4 ms·

Wordpress is less than ideal for managing via git, primarily due to their plugin architecture. The best way I have managed to use git is to put the repo at the

Wordpress is less than ideal for managing via git, primarily due to their plugin architecture. The best way I have managed to use git is to put the repo at the wp-content level and only watch the theme and plugin directories. Then anytime I make updates to a plugin or group of plugins, I make sure to commit those changes as a seperate commit to what I am normally working on. It is tedious and hacky, but it at least gets me basic version control functionality with the ability to roll back on any code that can effect theme functionality.

rwhitman 12y ago
This is my workflow as well. Not ideal, but better than nothing. Though I will say the biggest pain point with Wordpress is syncing and merging DB changes amongst team members, since so much of WP configuration is stored in the DB this becomes a real point of frustration especially on very large sites. I'd peg that problem as a much higher priority in terms of WP workflow than how to manage git inside WP admin.
- nader 12y ago
  this is a massive problem with all kinds of CMS including Drupal which we are using often. Drupal 8 is introducing configuration management, i.e. saving database configuration in yaml files which makes them "gittable". I hope wordpress and other CMS will also adopt this or a similar way.
  - LordIllidan 12y ago
    The Features module in Drupal 7 is a semi-workaround https://www.drupal.org/project/features https://www.drupal.org/project/features but I've hated Drupal a lot because of this. Too much stuff is stored in the DB.
    - snowwrestler 12y ago
      Forum One just released a sort of "Features for Wordpress" plugin: http://forumone.com/insights/configuration-management-finally-comes-to-wordpress/ http://forumone.com/insights/configuration-management-finall... https://github.com/forumone/wp-cfm https://github.com/forumone/wp-cfm

rwhitman 12y ago

This is my workflow as well. Not ideal, but better than nothing. Though I will say the biggest pain point with Wordpress is syncing and merging DB changes amongst team members, since so much of WP configuration is stored in the DB this becomes a real point of frustration especially on very large sites. I'd peg that problem as a much higher priority in terms of WP workflow than how to manage git inside WP admin.

nader 12y ago
this is a massive problem with all kinds of CMS including Drupal which we are using often. Drupal 8 is introducing configuration management, i.e. saving database configuration in yaml files which makes them "gittable". I hope wordpress and other CMS will also adopt this or a similar way.
- LordIllidan 12y ago
  The Features module in Drupal 7 is a semi-workaround https://www.drupal.org/project/features https://www.drupal.org/project/features but I've hated Drupal a lot because of this. Too much stuff is stored in the DB.
  - snowwrestler 12y ago
    Forum One just released a sort of "Features for Wordpress" plugin: http://forumone.com/insights/configuration-management-finally-comes-to-wordpress/ http://forumone.com/insights/configuration-management-finall... https://github.com/forumone/wp-cfm https://github.com/forumone/wp-cfm