Making the move from WordPressMU 2.x to 3.x isn’t all seamless. If after you upgrade all your uploaded images are broken download a broken image (because the webserver is actually serving an image, just your browser can’t read it). Open this image in notepad and you should see something like:
|
1 2 3 4 5 6 7 8 9 10 |
brokenimage.jpg <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body> <h1>Not Found</h1> <p>The requested URL /wp-content/blogs.php was not found on this server.</p> <hr> <address>Apache/2.2.3 (CentOS) Server at weblogs.pbspaces.com Port 80</address> </body></html> |
If you followed the upgrade instructions exactly you deleted the file /wp-content/blogs.php. Well thats a problem, in WordPress 3.0 they decided to move the function of /wp-content/blogs.php to /wp-includes/ms-files.php. Now if you have broken images and you still have blogs.php–it’s still a problem with your rewrite rules anyway because the old 2.x version of blogs.php isn’t going to work now that you have upgraded everything else to 3.x.
To fix this we need to update your rewrite rules in the .htaccess file
Find the line:
|
1 |
RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L] |
And replace it with:
|
1 |
RewriteRule ^(.*/)?files/(.*) wp-includes/ms-files.php?file=$2 [L] |
It’s that simple, now to see it take effect you will need to clear your browser cache, use another browser, or force reload (Ctrl+F5 typically)
June 25th, 2011 at 9:45 pm
Wow, I just spent 5 hours trying to figure this out, thank you so much, what a simple solution!
March 19th, 2012 at 11:53 pm
Man, your site popped up first and the solution was perfect. Too bad I didn’t Google it before I deleted those broken images, now I have to re-attach everything.
March 20th, 2012 at 7:39 pm
Glad to help!