Support » How-To and Troubleshooting » [Resolved] Upgrade to WordPress 3.0 Shows Broken Backend And No CSS Front Page For New Site

[Resolved] Upgrade to WordPress 3.0 Shows Broken Backend And No CSS Front Page For New Site

Viewing 11 replies - 1 through 11 (of 11 total)
  • Has anyone had a solution to this yet? Thanks…

    LOL, I figured this out! For some reason, the first time around that I saw what wp-admin/network.php showed as for input of .htaccess codes, the codes were wrong, all I have to do was to access the /wp-admin/network.php directly again to see the correct code second time around!

    It’s now working perfectly after I fixed .htaccess!

    Oh, by the way, turn on the debug as true in your wp-config.php can really help you in knowing which plugin is not working! By deactivating plugins you have running one by one, whenever your site refresh without a specific error, then you know the plugin that just got deactivate is the culprit. Or you can look at the error notice to see if it mentions the plugin’s files and directory, if it’s, then you know right away which plugin that you need to deactivate without trying the hit and miss tactic.

    thanks all!

    That got me into wp-admin and I can see pages like /about in the sub-site … but if I visit the front page it just hangs and loads forever.

    arghagain can you tell me how you fix this issue I don’t understand

    I am having the same issue after upgrading to 3.0 from wpmu. The network is up and appears to be working but I cannot access the backend or pages.
    Loading pages from subdirectory sites result in a 404 error. The only thing that does work is the edit button from Super Admin / Sites.
    Can anyone tell me the code needed for the .htaccess file to do the mod rewrite?

    Hello. I’m also having the same problem. The .htaccess WP generates for me makes no sense. And unlike arghagain I couldn’t get it change the .htaccess generation anyhow so I’m still stuck and in a need of the correct rules.

    I don’t understand this line: RewriteRule ^ – [L]

    It stops everything before the rules containing “wp-content”…

    It works already… It started working as mystically as with arghagain.

    I am having a problem with the added sites. They show up with no temp…they are just plain white background with black words and blue links. When I go into superadmin and try to go to backend it tells me that the link is broken. Can anyone help me with this?



    This should work if your htacces file looks like this:

    RewriteEngine On
    RewriteBase /
    #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]
    <IfModule mod_security.c>
    <Files async-upload.php>
    SecFilterEngine Off
    SecFilterScanPOST Off

    I had trouble with multisites that was similar to what is described here. I found two issues with my configuration:

    = If Apache httpd is using an Alias directive, then it should match the RewriteBase directive.

    = I found two fields in the Edit Site screen named Template and Stylesheet. I believe that they should match the folder name that the theme files are located in. For example, the folder name for Twenty Ten is twentyten. Note that on my computer the folder names are case-sensitive.

    I am still really confused.. HOW was this issue resolved? I have recently upgraded to multisite and am having the exact same problem as mentioned in the first post. My .htaccess file is exactly as posted by Jaap above. I can navigate the main blog fine, but attempting to access the backend or view a newly created site yields a 404 and Apache directory listing, respectively. I can’t help but think this is some simple permalink fix, but I’ve fooled around for hours and still no go. What information can I provide to have someone walk me though what to try? Using WP 3.0.1. Webpage: http://www.nauunderground.com

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘[Resolved] Upgrade to WordPress 3.0 Shows Broken Backend And No CSS Front Page For New Site’ is closed to new replies.