Go to http://yourdomain.com/secondsite/wp-admin or http://secondsite.yourdomain.com/wp-admin (which ever you’re using) and it’ll all be there.
The themes will all be in the one folder, but the posts are in your DATABASE, remember 🙂 The DB splits it like wp_#_foo (where # is the blog number…).
You will not see blog-specific files on the server – they are *virtual*. You sue the blogs the same way you woudl as if you have multiple blogs at wordpress.com. 😉
wpmututorials.com if you want to do some background reading.
Thanks in advance!
Ok, I think I have missed something here, because there is no such a folder ‘/secondsite’ or files under /second/wp-admin. I checked the path form the super admin section from the sites tab.
If I have understood correctly multisite means that same files are used for functionality, with only different parameters set up in configuration. So only these files should exist under the secondsite folders? But should they have been created there automatically when I activated the multisite, or should I copy/clone some files from the first installation?
What I ment with folders is that I thought that the admin panel would be the same for the all sites, but according the first post, all the administration for the sites is done separately.
thanks!
No. Like I said in my other post, the blogs/sites are *virtual* meaning they do not exist on the server. Your htaccess file uses commands in there to serve up the right address. WordPress serves up the information from the database.
Do not copy files or folders over.
The amdin panel *looks* the same for all sites, but is accessed separately. Have you ever had more than one blog at wordpress.com? Cuz that’s what you’re setting up.
Ok, seems that I have been missing the htaccess file completely.
I just added it but it breaks down the hole site, giving: “Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.”
I tried to look for the solution, but with no help.
My site is not on the domain root, it is in subfolder like this: http://www.page.com/test/test/wordpress-2.9.2/wordpress/
Could the permalinks mess things up (which of permalink forms should be selected?)?
Is mine rewritebase correct?
(samlpe of .htaccess)
RewriteEngine On
RewriteBase /test/test/wordpress-2.9.2/wordpress/
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).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]
Just noticed that ‘RewriteEngine On’ -line itself only also breaks site, is this healthy. Im not very familiar with the htaccess configuration, but it feels that that line doesn’t even do anything..
ipstenu:
Thanks, looks simple. I tried those paths before, as you said, but I believe that then the problem was the missing htaccess. But now I cannot get it working, so no redirecting..
Actually I’m usign this as a test site, so the location/act in the subfolder is correct. And the domain root still needs to be available for the origin (not wordpress)
But for the future I would be happy to know the actions between these.
If THIS RewriteEngine On breaks your site, then tell your host ‘Hi, I need mod_rewrite enabled!’ Because without that? Your installs will never work. 🙂 That bit of code calls the tools on your server that allow WordPress to use pretty permalinks. Without that, you cannot use MultiSite.
Yep, got it by enabling the mod_rewrite.
Sunshines and rainbows to you all!
