Sub-sites admin not accessible and CSS not visible after MU upgrade to 3.0

Might need to call the upgrade file directly, like

/wp-admin/upgrade.php

it returned answer to direct upgrade call; “Your WordPress database is already up-to-date!”

I am running on dreamhost Shared server and have read about the domain mapping problems that may occur, but i am not using domain mapping.

Also, i initially had problems with the .htaccess file (images not showing post upgrade) but got that sorted.

I tried creating a new sub-site to access the admin panel and see if it was an upgrade issue, but even a new site (although visible in plain HTML) has no access to the admin panel. https://bagging-scotland.com/mybag/testsite/

thanks for your help @andrea_r

Any chance we you upgraded, you mucked up the htaccess file? Because that’s what’s causing it.

quite possibly! ??
it got quite confusing for me because all the examples and default .htaccess file refers to the root of the domain, whereas my installation is in a sub-directory and has a redirect from root of the domain… i’d prefer it in the root directory but moving it is an even more scary prospect.

i know its just a case of adding in the directory but it leaves me unsure when doing it with all those eerie characters %$&'(.*%$& etc

someone gave me this snippet to create the re-direct with:

RewriteEngine On
RewriteRule ^/?$ /mybag/ [L,QSA,R=301]

but perhaps there would be a better way to do it now that there are additional rules for WP3, i tried putting it in the ‘RewriteBase’ bit as a guess bit didnt quite work with the original rewrite:

RewriteEngine On
RewriteRule ^/?$ /mybag/ [L,QSA,R=301]
RewriteBase /mybag
#uploaded files
RewriteRule ^(.*/)?files/$ index.php [L]
RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*
RewriteRule ^(.*/)?files/(.*) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteCond %{REQUEST_URI} ^.*/wp-admin$
RewriteRule ^(.+)$ $1/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule . – [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]

sorry for my complete incompetence, i’m trying to learn but cant make head or tail of it!

And that rewrite was working before the upgrade?

(it’s not incompetence, this bit can be tricky)

yes, the rewrite worked fine pre-upgrade. the rewrite still works, but now it requires the other new WP3 lines, the re-direct only sends to the home page with the images missing, the other pages in the main site and sub-sites dont work either.

Tricky indeed! Thanks

Could it be something to do with the sub-sites not having their new twentyten theme installed correctly?

I have noticed that the HTML output has the same characteristics/layout when accessing the sub-sites (which don’t show any CSS and cant access admin area).

example: https://bagging-scotland.com/mybag/testsite/

The theme is installed correctly; the no styling is a symptom.

Look at the source of the page – it’s called in the right stylesheet as it shoudl, yet if you access that URL directly, it can’t be found. Yet, it is on the server.

We saw this exact same issue *a lot* in mu installs.

someone gave me this snippet to create the re-direct with:

RewriteEngine On
RewriteRule ^/?$ /mybag/ [L,QSA,R=301]

What happens if you take this out?

I currently have that line commented out (and so inactive) with a # at the beginning of the line – the redirect no longer works, but the site still has the same issues…

Saw your post in the other thread – are you on a Windows or IIS server? (that web.config is specific to windows servers)

I’m pretty sure its not windows server, im hosting it on Dreamhost shared server and i think they use Linux servers(?). That’s that idea out the window then!

I was wondering:

Should i have a .htaccess file in my server root folder to provide the re-direct, and ALSO have a separate .htaccess file in the root of the WP installation? Can you have two?

That way the file in the root of the installation should work the same as any other installation (rather than a sub-directory install of WP).

Resorting to crazy tactics here!

These lines in my .htaccess (in the server root directory) are causing a 500 server error, so i currently have them commented out:

# add a trailing slash to /wp-admin
RewriteCond %{REQUEST_URI} ^.* /wp-admin$
RewriteRule ^(.+)$ $1/ [R=301,L]