following both of the relevant codex articles
Which ones? I gotta ask 🙂
Between those two major changes, I did have to change the content links, for which I used Velvet Blues Update URLS.
THAT tells me you did it wrong, since the article you should have used – https://codex.wordpress.org/Moving_WordPress#Moving_WordPress_Multisite – says to use the interconnect script for a reason 🙂
Thanks, Ipstenu.
Hah! That would have been smart. I followed the Create a Network directions, which linked to Before You Create a Network and then Giving WordPress Its Own Directory. I saw the article you mentioned, but didn’t worry too much about the difference between Velvet Blues and Search-Replace-DB since I was switched directories before adding Multisite.
I’m totally up for using the interconnectit script. In fact, I tried it just a few minutes ago but dry run didn’t find anything to change. Maybe I didn’t get the options right, though: I tried replace l156.org/wp-admin/network with l156.org/new/wp-admin/network and then replace /wp-admin/network with /new/wp-admin/network.
I tried replace l156.org/wp-admin/network with l156.org/new/wp-admin/network and then replace /wp-admin/network with /new/wp-admin/network.
That would be wrong 🙂 But that’s because you did a double move (domain AND folder) so it’s weird and totally not your fault.
So I’m assuming you’re moving from l156.org/ to l156.org/new/ (if this is wrong, change the domains/paths to match what’s right)
1) Using the interconnectit script: Replace l156.org/ with l156.org/new/
2) Using the interconnectit script: Replace l156.org/new/new/ with l156.org/new/ (because you may have some weird things)
3) In the DB manually: check the wp_site table and make sure you have a PATH in there of /new/
4) In the DB manually: check wp_blogs table and make sure those paths are correct
That SHOULD be it…
The directions broke it even more, probably because I convoluted things.
After the first two steps, I lost the theme. After the last, I had only Error making database connection. I then restored from backups.
I’ll go back to the beginning:
- DNS has not been updated. The work-in-progress is at a different ip.
- I moved the directory from
/home/lorg/publichtml/ to /home/lorg/publichtml/main/. (I was using new as shorthand.)
- I kept the domain at
http://l156.org/ and did not move it to http://l156.org/main/.
- After those two major changes from my first post, everything works–all pages, links, content, and dashboard–except the links under the My Sites heading of the dashboard. I have to slip
main/ in there to make them work.
- After I insert
main/ the links from the network admin pages work and include main/, while the links under the My Sites section of the admin bar still do not.
- The My Sites link itself does work and does show
main/.
- All of those other parts that work do not display the
main/ part of the URL, just http://l156.org/wp-*
I have to wonder: Is there a part of the DB where I need to manually change over those network admin links on the admin panel?
I was wrong about that last bullet point:
- For all of the those other parts that work
- outside the dashboard do not have
main/ and
- inside the dashboard do have
main/, both the pages themselves and the links on the panels.
Sorry, that was supposed to be a nested list.
Also, the wp-content links also need and have main/.
I got it! It was (of course) something really simple:
I had not removed the old .htaccess rules.
That’s all. I inserted a handful of comment tags, F5, and Bob’s your uncle.
