OK, I’ve been through everything I can find over the past three days and not finding any definitive answers. Lots of speculation, outdated instructions and some amount of ambiguity, so coming to the Brain Trust before I Bork the whole darn thing.
With the new direction that WP is taking, it seems a good idea to get everything into order, so that future updates/upgrades are compatible and work as well as possible. It is a sub-domain install, currently at 3.6.1, having upgraded from WPMU 2.x all through all versions since. The conversion to WP 3.0 went as expected, as did all others subsequent… I thought.
What I didn’t do (because I just came across it TODAY (why?)) is to follow the upgrade instructions listed on this page:
The current 3.5+ .htaccess is running, with the exception of having the ms-files.php line added in to rewrite the attachments location; which is what I want to get rid of.
It started when I began to migrate the old /blogs.dir/ID/files/yyyy/mm/ to /uploads/sites/ID/yyyy/mm/
I read Mika’s treatise on doing this, along with a few other accounts on the topic, and then came across a plugin to do it. Attempting to run the plug, it died, saying that my install isn’t Multisite. Uhhh… yes it is. Checking the plug code it barfed on the absence of:
OK, added that in, attempt to login and get the ol’
Error connecting to database
If I’m logged in, and refresh the page, I get:
One or more database tables are unavailable. The database may need to be repaired.
Have yet to hit that repair link.
Found a listing of tables that are in 3.4 and those all are there but can’t locate a listing of 3.5+, which would probably let me see what’s missing. I have a separate dev install where I test my plugin when new WP versions reach RC and it runs fine with define(‘MULTISITE’, true) in wp-config. It, however, only has one site, no secondaries.
What do I need to do, short of doing a whole new install and exporting/importing, to clear this hurdle? I’d rather do this surgically, as opposed to nuking it from orbit.
Thanks for any directions.
- The topic ‘Migrate 3.6 to actual 3.6’ is closed to new replies.