Recently a site that I do some side work for had a hard drive failure on their server and had to transfer the site to a new server. They recently came to me telling me their MU install was fine minus that the sub-blogs no longer had a skin nor did they have access to the backend of the sub-blogs.
Everything looks fine on the main blog and I ran a repair on the database to see if that would fix and no luck. Any suggestions?
http://www.geeksradio.fm
sub-blog:
http://www.geeksradio.fm/lumpcast/
Looks like css files are missing. Anyone checked the apache error logs for 404s?
Considering they can;t get into the backend of the sub-blogs, I;d say the rewrite rules are messed up. Check the permalinks on the main blog. Do they work fine?
Check htaccess, does it look like the default?
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
thats the .htaccess ... I believe that is default. permalinks seems to be working fine on main blog as well... the sub-blogs should be using the same style as the main blog as that is the only active style.
It's not. you're missing a lot. specifically, the stuff that controls the items currently broken.
RewriteEngine On
2 RewriteBase /
3
4 #uploaded files
5 RewriteRule ^(.*/)?files/$ index.php [L]
6 RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*
7 RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L]
8
9 # add a trailing slash to /wp-admin
10 RewriteCond %{REQUEST_URI} ^.*/wp-admin$
11 RewriteRule ^(.+)$ $1/ [R=301,L]
12
13 RewriteCond %{REQUEST_FILENAME} -f [OR]
14 RewriteCond %{REQUEST_FILENAME} -d
15 RewriteRule . - [L]
16 RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]
17 RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
18 RewriteRule . index.php [L]
19
20 <IfModule mod_security.c>
21 <Files async-upload.php>
22 SecFilterEngine Off
23 SecFilterScanPOST Off
24 </Files>
25 </IfModule>
See: http://trac.mu.wordpress.org/browser/trunk/htaccess.dist
It seems that a good amount of people are having these 404 issues in the last week ( I had a friend who had the issue too, but they reinstalled the MU ).
Could it be possible that there may be a security hole involved? My site just had a 404 mess up today, but its been working all year, and I haven't done anything to it in 3 weeks.
It could also be possible that your host reset a bunch of htacces files too.
Anyone tinkering with your install will either be obvious, or they will have put those spam links in it.
That is true. My problem was the htacces change. I was just making sure there wasn't a trend.
I probably will write an article on the 404/500 issues, since a lot of these answers are easy, overlooked, and just get lost in the forums.
Other people have written certain issues; would be good to combine all of these to reference future forum posts.