homeruntaz

Found the solution!!!! I changed the url in the blogs table(wp_blogs if you didn’t modify it) -it’s the only row in the table and once I added the www to it- the site, admin and network admin works!

I’m having the same problem as robpannell – but only after I changed the site from non-www to www. The site is up, the admin works but the network admin goes into the infinite loop. If I remove the DOMAIN_CURRENT_SITE, then the network admin works but then none of the site links work(but the site is visible). I have two databases I’m flipping between to figure this out -one with all the links set to non-www and one with all www. I’m guessing there’s a mismatch somewhere between non-www and www but don’t get where when it only affects network admin?

Ok – I’ve been playing with this and there must be more to “upgrading” from a standard install to network. We have an existing WP3 site and would like to make it multiuser instead of the multiple installs we have now. I add the “WP_ALLOW_MULTISITE” CODE and relaunch – start the Network and then add the multisite code to wp-config and the .htaccess file. As soon as I do that and log out – it no longer finds a database connection. I noticed on previous attempts that a network database has wp_blogs table, and several other tables, where a standard install doesn’t have that- I’ve checked all our other sites/databases. Is there more to do? We have a huge site and need to add additional sites to it so they can have their own permalink structure within the larger site.