tcwaters

Multisite is somewhat more complicated to move, as the database itself has multiple references to the server name as well as the folder locations. If you’re simply moving to a new server with the same domain name, you can copy the files and database over, exactly as you would a traditional install.

If, instead, you are changing domains, then the best way to move Multisite is to move the files, edit the .htaccess and wp-config.php (if the folder name containing Multisite changed), and then manually edit the database. Search for all instances of your domain name, and change them as needed. This step cannot yet be easily automated. It’s safe to search/replace any of the wp_x_posts tables, however do not attempt blanket search/replace without the Search and Replace for WordPress Databases script.

This doesn’t sound like it is exactly the same. Although I get one place I did it wrong. I installed a back up plugin, like I would for a single site, INSTEAD of installing for the entire “/” site.

If you’re moving Multisite from one folder to another, you will need to make sure you edit the wp_blogs entries to change the folder name correctly. You should manually review both wp_site and wp_blogs regardless, to ensure all sites were changed correctly.

Also manually review all the wp_x_options tables and look for ‘three fields and edit as needed:

home
siteurl
fileupload_url
If you are moving from subdomains to subfolders, or vice-versa, remember to adjust the .htaccess file and the value for SUBDOMAIN_INSTALL in your wp-config.php file accordingly.

Yes,

I can crerate a network just fine. Where we are failing is moving sites from an existing multisite network to a new network on a different server.

I wanted to mark this thread as resolved. so here is a follow-up.

We could not determine what caused the problem, however, we deleted the site, emptied the database and rebuilt it. There wasn’t too much in it, so it wasn’t that big of a task. After the rebuild, WP 6.6 ran wonderfully with no speed issues at all. The update to 3.6.1 went just fine too.

I have a feeling I hadn’t adequately deactivated all plugins before the udate that caused the slowness and somehow corrupted the database?

This is ONLY a problem on multisite installations running on Windows in my experience. WP 3.6 on Windows as a single site shows no speed issue. And Multisite running on a Mac server shows no issue.

I have de-activated all plugins and the issue remains.

All plugins de-activated and same behavior.

Duh. Figured this out on my own. Under screen options.

THX. Yes, I deactivated the broken them, activated another them, amd then tried to delete the broken theme.

I also tried simply adding the stylesheet since that was the file it said was missing. I think I tried everything.

What I’m unclear about is how does the template.php page determine what templates to display there. Why does that page believe that a template is installed when I have removed the template’s folder completely from the /templates directory

THX,

I have put the info into both, however, the server admin told me today, that the server uses web.config.

Is there a standard web.config for running on a Windows IIS server?

This got me going. Deleted the themes, put via SFTP the theme twentyeleven, and I was able to access the site again.

sorry that was a typo.

https://www.pages.pharmacy.pitt.edu

https://www.phages.pharmacy.pitt.edu however, this is on a pre-production server and is only available within the pitt.edu domain.

I did deactivate the plugins as per the codex but that hasn’t solved the problem.

This problem is resolved. In the apache rewrite page, the Apple server was adding code after my server admin had commented it out. By uncommenting it, and changing the order of some of the lines, the problem was resolved.

Gave up and used another plugin.

I resolved this on my own.

Took a screen shot of the tags cloud. Opened the screen shot in Acrobat and used it to OCR the text.

Worked great!

No. Thx. Totally missed seeing that it was needed. Got it! THX!