Why would you need to log them? They’re defined in the code itself. Look at wp-admin/includes/upgrade.php. Every version that changes the DB has a function defined that does the job. The changes made for version 3.4 are defined in the upgrade_340() function. The changes made for 3.3 are defined in the upgrade_330() function. And so … Read more
Ok, to resolve these issues, let’s implement the cascading upgrade process which will handle both use cases. First of all lets implement our plugin activation hook, which will be our entry point: // define current plugin version define( ‘WPSE8170_PLUGIN_VERSION’, ‘2.0.0’ ); // define our database table name define( ‘WPSE8170_DB_TABLE’, $GLOBALS[‘wpdb’]->prefix . ‘wpse8170_test_table’ ); add_action( ‘init’, … Read more
Impossible. The path is hard coded in many places (wp-admin/includes/update-core.php for example). I think this is worth a Trac ticket, if there isn’t one already. We can move the directories for plugins, themes and mu-plugins. This is the last thing why we need a wp-content directory at all. Update There was a short discussion in … Read more
I don’t know of a great before and after comparitor that would get you the results you need. In fact I would be worried that any tool like that won’t catch any failures in functionality. Honestly I would suggest incrementally building up a testing suite that goes through some of your standard processes and verifies … Read more
You should probably upgrade one step at a time from one version to the next. All the code of all the versions are listed at the http://wordpress.org site. It will be a long process but the best to ensure proper upgrades. You can try to make it faster by skipping several versions at each step, … Read more
Most of the time any changes that need to be done on upgrade are database related. Core files can be freely swapped pretty much. WP keeps track of this by comparing db_version option (stored in database) against the current value (from core files) on admin load. If there is mismatch it runs the upgrade routine … Read more
Well after a lot of digging, I think I uncovered what happened. The clue came from the fact that I noticed it was wp_options and all alphabetically subsequent tables that lost their primary keys. On import, first the tables are created. Next it goes through all those tables in alphabetical order and applies the primary … Read more
Delete everything but wp-content and wp-config.php, copy the fresh installation into the directory. On upgrading WordPress will use the database to see what should be done, not the files. Not all files are deleted automatically, because some of them might still be used by outdated plugins or external scripts (the old feed files are good … Read more
I had the same problem, this link explains how to change your filesize upload limit https://www.digitalocean.com/community/tutorials/how-to-change-your-php-settings-on-ubuntu-14-04 Basically find your php.ini file, and change these two below to 30M post_max_size = 8M upload_max_filesize = 2M
I also used SVN before to update my wordpress installation. Up the working copied will get messed up very quickly with all the manual updates or files created by plugins. I would always recommend to use the update functionality of wordpress if you only want to step from one tagged version to another one. Although, … Read more