I have often wondered whether I could write such a thing. Problem is that a plugin can (and sometimes needs to) make changes – database and sometimes files too. There is NO way for an external party to know what changes were made. A plugin that could manage the process would have to (as noted … Read more
Have a look at this older question: How to: Easily Move a WordPress Install from Development to Production?. It covers migration and deployment of WP installations. For your more immediate issue, do backups of your database. Use a backup plugin (WP-DB-Backup is what I use, find it on the WP plugins repository) to handle this … Read more
Dunc, glad you asked about this before it was too late for you. You have heard the right words. You are right, unfortunately the articles tutorials are not very much newbie friendly. Frist let me try to clear some terminology for you. The thing you need to manage your code and keep track of all … Read more
There’s the site_status_tests filter, to e.g. remove the asynchronous background updates tests: add_filter( ‘site_status_tests’, function ( $tests ) { unset( $tests[‘async’][‘background_updates’] ); return $tests; } ); But one could argue that this is just hiding information from the user. Ticket #46733 suggests instead e.g. “…ignored tests section, hidden away like the Passed tests“, so the … Read more
This is not yet a complete answer, for lack of time, though I’ll try to return later with a more complete example but I just wanted to add a couple of notes. Possibly someone else will jump in soon. To get the ball rolling… Firstly, Yes this is entirely possible, you can create this functionality … Read more
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/
There’s no set best practice, as each model fits different work processes. One Repository If you’re only managing a single site with a single set of plugins/themes then a single repository makes sense. Or if you’re managing multiple sites that use the same set of plugins/themes. Multiple Repositories This is my personal preference. Keep WordPress … Read more
Templates are only stored as files in the file system. They are not stored in the database so there is no core functionality for versioning template files. When you make changes, the file is overwritten with the changes. The easiest route would be to use an existing version control solution (SVN,CVS,Git,Hg, etc.) and maintain the … Read more
First of all, you need to recognize that there are two workflows here: yours and your client. Your Workflow Receive PSD Code HTML/CSS Code WordPress template Deploy theme to live WordPress site Their Workflow Devise required changes and email you Write posts Upload photos The Issue Implementing version control here has absolutely nothing to do … Read more
Here are two possible solutions, both of these are actually generic MySQL version control tools but can be adapted to your workflow: dbv.php This tool creates “migrations”, which are basically SQL scripts, from the changes detected on the database. These scripts are stored in a local directory and thus can be commited to your current … Read more