Looking at your proposed structure, I am assuming that the only thing that would be changed is: The WordPress files are all kept in a folder you’ve called web. For this just create a .htaccess file in root folder, and put this content inside (just change example.com): <IfModule mod_rewrite.c> RewriteEngine on RewriteCond %{HTTP_HOST} ^(www.)?example.com$ RewriteCond … Read more
I would argue that this is simply not possible (or extremely difficult) to do in an automated fashion, as there are so many different files which could be included or used in so many different places. I’ll take javascript files as an example. They could be included: via <script> tags in any of the template … Read more
NOTE: XML Importer will not work for this task as the amount of data is too large. This tool is by far the simplest solution if there’s any way you can get it to work. Is it absolutely “too large” for the importer, or just limited by file upload / PHP execution time limits? If … Read more
Can i, with Git, checkout the most current repo from my live server to my local machine? No, unless you also add the wp-content folder under version control. You can instead look at other tools, such as rsync. As for the database, you could make the live server accept remote MySQL connections, so that you … Read more
http://codex.wordpress.org/Hardening_WordPress#File_Permissions / – The root WordPress directory: all files should be writable only by your user account, except .htaccess if you want WordPress to automatically generate rewrite rules for you. /wp-admin/ – The WordPress administration area: all files should be writable only by your user account. /wp-includes/ – The bulk of WordPress application logic: all … Read more
As mentioned in my comment, ensure you test the following in a “clean” browser: Set siteurl & home to http://www.example.com/wordpress-subdirectory Set permalink_structure to nothing Set active_plugins to nothing Ensure there are no WP_SITEURL or WP_HOME constants defined in your wp-config.php Remove all rewrite rules to do with WordPress from your .htaccess Not of all these … Read more
As @andreascreten, wp-cli will do the job for you. wp-cli includes commands for W3TC (located in the src/php/wp-cli/commands/community/total-cache.php file), so you can flush the cache by running: $ wp total-cache flush <type> Where <type> is one of ‘db’, ‘minify’, ‘object’, ‘page’ or ‘post’. (Note: If you use ‘post’, you’ll need to pass in –post_id= or … Read more
When exporting from original database you should choose to create the tables if they dosn’t exist (First error). If you didn’t choose that option (in phpMyAdmin that option exists, not sure in other database tools), the import file can not create the tables for your and you need to create then prior to start importing … Read more
I commit all WordPress because I consider it one big ball of code that pertains to one site, this means updates to core WordPress files, plugins and themes are all part of the commit history. I don’t use sub-modules or any other weird nested revision setups. If you have a complicated structure of including multiple … Read more
WP CLI The easy way; use the WP CLI (also available as wp-cli.phar) to get a solid, maintainable solution for this requirement. More for this topic you will find at the command wp plugin <command> WP API If you will need a custom script is is necessary to load the WP API, via wp-load.php and … Read more