Thread Starter
inge12
(@inge12)
Duh! Thanks! 🙂
Okay, so now I have a new issue showing up under Tools-Network:
I moved the blog successfully from a sub-domain to the root, but the code under Network suggests to add this to wp-config.php:
define( 'MULTISITE', true );
define( 'SUBDOMAIN_INSTALL', false );
$base = '/';
define( 'DOMAIN_CURRENT_SITE', 'blog.domain.net' );
define( 'PATH_CURRENT_SITE', '/' );
define( 'SITE_ID_CURRENT_SITE', 1 );
define( 'BLOG_ID_CURRENT_SITE', 1 );
But I moved the blog to the root (/public_html). It is no longer in blog.domain.net
Oh, yeah .. I got the idea from the codex that I can’t use subdomains, but must use subdirectories. Maybe the code in the actual install knows better, and it suggests that my current blog should go into the subdomain?
Suggestions?
Thread Starter
inge12
(@inge12)
Okay, so I changed my wp-config file as suggested, and I changed my .htaccess file as suggested:
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]
# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]
RewriteRule ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
Result is that my WordPress install is totally broken.
(Lucky it’s only on a test setup, but I do need to know how to do it on the real setup!)
If this is test set up I suggest you start form scratch from fresh install in root and then try and set up as network.If it all depends on if you host lets you use subdomain names if not then you will need choose subdirectory
Thread Starter
inge12
(@inge12)
Thanks for the reply.
A lot of work has been put into the test setup — modification of theme, as well as actual posts that are supposed to be ported over to the real site.
With all the glitches I’ve run into, I think I’ll have to do another test setup, and move the theme, posts, etc. into it before moving it to an active, live site that must not have significant downtime.
Thread Starter
inge12
(@inge12)
I changed the .htaccess file:
from
define( 'DOMAIN_CURRENT_SITE', 'blog.domain.net' );
to
define( 'DOMAIN_CURRENT_SITE', 'domain.net' );
but things still weren’t working.
Then I looked at the database through PHPAdmin and found that the domain for the blog was still specified as ‘blog.domain.net’
I edited the database directly to specify the domain as ‘domain.net’
Then things started working — i.e. the blog recognized the database.
Thread Starter
inge12
(@inge12)
OOPS! The editing was NOT in the .htaccess file but in the wp-config.php file!
That editing was necessary, as well as editing the database. There are probably other ways to do it, but this worked for me.
