I use Git for all my projects since it lets me work offline and that happens fairly often for me. Git can interface with SVN if you’d still like to use Git then push your plugins to WordPress.org. http://www.nkuttler.de/post/using-git-for-wordpress-development/ http://hakre.wordpress.com/2010/09/28/git-rocks/
(I realize this question is five years old, and that the OP probably found a solution already.) I work on a team that manages a large WordPress website. We have tens of thousands of custom posts, with data being entered/edited dozens if not hundreds of times a day. We actually break things down a little … Read more
While I know version control approach to be used in practice, I don’t think it’s too common. WP has weak version control practices in general, so development of extensions doesn’t quite plan for such. Example of specific scenario which will cause issues might be changes in template hierarchy. Let’s say you customized single.php in version … Read more
Set the constant DISALLOW_FILE_MODS to TRUE in your wp-config.php: const DISALLOW_FILE_MODS = TRUE; See the Codex for background information: Setting this constant also disables the Plugin and Theme editor (i.e. you don’t need to set DISALLOW_FILE_MODS and DISALLOW_FILE_EDIT, as on its own DISALLOW_FILE_MODS will have the same effect). It will also prevent installing or uninstalling … Read more
I use a script called git-ftp, which simply uses FTP to push changes from a git repo onto a server.
The reliable two–way sync is simply not something that have happened in WordPress. The typical way is in line with what you are doing — pulling a copy of production database into development environment. Note that this is commonly the one direction it goes. It’s much more problematic to try sync development back to production. … Read more
Download your languages files from the SVN repo… I would strongly advise against this. The repo, as storage of language files, is being discontinued, in favor of Translate WordPress. Right now, you have no guarantees that the repo has a current version of the file. The current method of getting language files is either to … Read more
Good news and more good news! First – all of the code related to WordPress itself and its repositories resides in version control system (Subversion). Among other things that makes publicly available sites with all code in plain sight: http://core.svn.wordpress.org/ http://themes.svn.wordpress.org/ http://plugins.svn.wordpress.org/ One not so obvious result of that – if you can see it, … Read more
Basically ignore everything except your theme folder and custom plugins. sample .gitignore: wp-admin/ wp-includes/ .htaccess index.php license.txt liesmich.html readme.html wp-activate.php wp-blog-header.php wp-comments-post.php wp-config.php wp-config-sample.php wp-config-stage.php wp-config-live.php wp-config-dev.php wp-config-production.php wp-cron.php wp-links-opml.php wp-load.php wp-login.php wp-mail.php wp-settings.php wp-signup.php wp-trackback.php xmlrpc.php config/ wp-content/plugins/ wp-content/mu-plugins/ wp-content/languages/ wp-content/uploads/ wp-content/upgrade/ wp-content/themes/* # don’t ignore the theme you’re using !wp-content/themes/yourthemename This makes the … Read more
Yep, you can pass the initial revision from which to start scanning: git svn clone -s -r387893 http://plugins.svn.wordpress.org/your-plugin/ You can hunt down that revision by using this command: svn log http://plugins.svn.wordpress.org/your-plugin/ The last line shows the earliest revision. Source: http://teleogistic.net/2011/05/revisiting-git-github-and-the-wordpress-org-plugin-repository/