500 error after upgrade WordPress multisite

  • Resolved handig

    (@handig)


    13 years, 10 months ago

    I upgraded from 3.0.4 to 3.1.2 and I had some redirect 310 error problems. This was solved by modifying the network admin.php

    Then I noticed something very strange. All my websites are there except one. I get a 500 error.

    What I understand is that WordPress multisite works as follow. The website on the network should be pointed to the ip of the Multisite WordPress installation.

    When I type in the URL of the the website in the browser, the computer looks it up in the DNS servers. The registrar dns tells it, that it lives on the IP of the WordPress multisite installation. My computer gets send to that IP adress, my webserver directs me to my WordPress multisite installation and the WordPress multisite looks into database which blog to serve.

    But somewhere I now get a 500 error for one of the websites on the multisite Wordpess.

    Where should I look at?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    The problem in that thread wasn’t the admin.php, but that the user had moved from foo.com/example to example.com and didn’t update the wp_blogs table to change from /example to /

    What I understand is that WordPress multisite works as follow. The website on the network should be pointed to the ip of the Multisite WordPress installation.

    IP doesn’t matter (unless we’re mapping domains). What you described is sorta how ALL websites work ?? Domain -> DNS -> IP -> webpage!

    So are we talking mapped domains on a MultiSite install or subdomains or subfolders or what?

    Thread Starter handig

    (@handig)

    I have a multisite subdomain installation.

    To clarify it a bit. So I have WordPress multisite on https://www.mywpmultisite.com with subdomains websiteA.mywpmultisite.com (for website https://www.websiteA.com) and websiteB.mywpmultisite.com (for https://www.websiteB.com).

    After the upgrade I can still go to https://www.websiteA.com but https://www.websiteB.com gives the 500 error.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    So we’re talking mapped domains on a subdomain multisite ??

    If you turn mapping off for WebsiteB can you get to websiteb.mywpmultisite.com?

    Thread Starter handig

    (@handig)

    I turned the mapping off (by deleting it) but can’t go to websiteb.mywpmultisite.com.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Normally that’s an .htaccess error (which would affect ALL sites, so not so much for you!) or a theme/plugin error. Can you turn off all plugins for WebsiteB?

    Thread Starter handig

    (@handig)

    Thank you very much for your help. I had 14 active plugins and it was (ofcourse) the last one which caused the error: Advanced XML Reader

    Thanks again.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Well if it was the first one, that’d’ve been the last one ?? No prob!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘500 error after upgrade WordPress multisite’ is closed to new replies.