Support » Networking WordPress » Fatal error and 404 after 3.6 upgrade WP Multisite

  • Resolved Frank Jones

    (@fjones18)


    I was on 3.5.2 and did upgrade to 3.6 when I got the following message:
    Fatal error: Call to a member function add_menu() on a non-object in /home/content/47/10522347/html/wp-content/plugins/wp-native-dashboard/langswitcher.php on line 28

    After removing the plugin, I was able to complete the update and access the dashboard.

    Now, the primary site for the multisite installation is working as it should. However, the secondary site has a 404 error when I try to access the homepage. Accessing any other page does not give this error and the page loads as it should. I can login to the dashboard for this secondary site as well. Basically, all the functionality of both site is working with the exception of the homepage for the secondary site. For example, all these pages would load correctly:
    http://www.mysite.com/
    http://www.mysite.com/contact/
    http://www.mysite.com/wp-admin/
    http://www.mysite.com/es/wp-admin/
    http://www.mysite.com/es/contact/
    http://www.mysite.com/wp-admin/network/
    The only page that would not load correctly is:
    http://www.mysite.com/es/

    Also, I typically have a static homepage and blog posts are published on a Blog page. When I chane this and try to access the static page directly it loads. For example:
    typically the secondary site would be http://www.mysite.com/es/
    this would typically load the Home page
    after changing the dashboard setting to use the lates blog posts as the home page, I can go to http://www.mysite.com/es/home and the page loads

    I checked .htaccess and it has not changed since I setup WP Multisite in May of last year.

    Any idea what could cause that?

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

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    Bringing this over to Multisite…

    What’s the 404 look like? Is it styled like the main site or the secondary?

    Have you double checked that you still have a front page defined for that site?

    Thread Starter Frank Jones

    (@fjones18)

    I have not styled my 404 pages, so it’s the GoDaddy default: http://i463.photobucket.com/albums/qq353/torontorealestate/404Error.jpg

    I have checked the setting in the dashboard (Settings>Reading>Front page displays) and there is a front page defined. I have also changed this setting to ‘Your latest posts’ to see if that would change anything. The home page still did not load. However, I was able to load the page that I had set to home:
    http://www.mysite.com/es/home

    When I changed the setting back for the defined front page, that page would not load. For example:
    if http://www.mysite.com/es/home is set to be the front page, it redirects to http://www.mysite.com/es/ and does not load
    if http://www.mysite.com/es/home is not set to be the front page, it does not redirect and the page loads
    in both cases, http://www.mysite.com/es/ has a 404 error

    I hope that helps. Let me know if I need to elaborate further on any part of this.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    I have not styled my 404 pages, so it’s the GoDaddy default:

    Bzzzz. That’s bad. WordPress should ALWAYS have a default 404 in a theme. it’s required. So that’s something wrong on your server, and I THINK is the main issue here.

    Are you on Apache/Unix or IIS/Windows?

    Thread Starter Frank Jones

    (@fjones18)

    I’m using Apache/Unix hosting with GoDaddy. Also, I checked my theme and you are correct. There is a default 404 included and it is not the one being displayed.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    So that’s where you need to start looking 🙂 Ask Godaddy why that’s not using WP’s 404.

    Thread Starter Frank Jones

    (@fjones18)

    I’ll try asking GoDaddy, but this was working properly before the WP update. After the WP update it does not work. It seems unlikely they changed anything on the server at the same time I did the WP update. Wouldn’t that make this a WP problem?

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    You’d think, but ‘unlikely’ is the keyword 🙂 I work for a host. We upgrade a LOT of stuff on the sly.

    You can try reverting to 3.5 (just overlay the files) to see if it goes away, or the usual ‘turn off all plugins and revert to default themes’ test, which you should always do anyway 🙂

    if WP isn’t pulling the 404 page, though, it’s generally an indication of server issues.

    Thread Starter Frank Jones

    (@fjones18)

    One of the first troubleshooting steps I tried was to turn off all the plugins and themes, that’s how I solved the wp-native-dashboard issue. However, this problem persists.

    I’ve setup a support ticket with GoDadddy and they will get back to me soon. I’ll let you know what they say.

    Thanks for your help.

    Thread Starter Frank Jones

    (@fjones18)

    This was GoDaddy’s reply:

    Thank you for contacting Online Support. As this is a WordPress multisite it would be very difficult for us to troubleshoot in the normal way as its sets up a lot of virtual pages using custom scripting both within the site itself and within the database. One glaring issue that I could normally say is the issue is that the /es directory does not have an index file in it. Again as this is a WordPress multisite it may not matter. As this is all 3rd party scripting I have 2 suggestions 1) enable error logs to catch the error when it goes to the WordPress it can try and catch the error. 2 ) consult with WordPress.org for why this issue occurs.

    Please let us know if we can be of further assistance.

    Thread Starter Frank Jones

    (@fjones18)

    I just enabled the error logs as recommended by GoDaddy and their site requires 24 hours before they will be available. Is it just me or does that sound like a stupid idea? I guess I’ll check back in 24 hours.

    In the meantime, any suggestions to solve this problem would be welcome.

    Thread Starter Frank Jones

    (@fjones18)

    Thread Starter Frank Jones

    (@fjones18)

    Something the GoDaddy agent said didn’t seem right. He mentioned “the /es directory does not have an index file in it”. There shouldn’t be an /es directory in this Multisite install. So, I changed the directory name to /es2 and now the page loads. The problem is solved. The only other thing I want to mention is that the /es directory has a time stamp from some months ago. This means the previous version of WP Multisite did not have a problem with this directory being on the server, the new version does. Presumabley, other Multisite installs could have a similar problem if a new site is created with the same name as a directory on the server. For now, my problem is resolved.

    Thanks for your help.

    Hi,
    I have a similar issue..
    I did update the network, and I’ve created a new site that I can login it’s dashboard but when I intend to visit the site, I get 404 hosting error..!

    i don’t know if the problem because of the last release of WordPress or the general Internet connection problem the happened during the last 12 hours for a number of web hosting providers..!

    I did deactivate all plugins, but nothing went better..!

    Any Idea please..?

    Thanks.

    Thread Starter Frank Jones

    (@fjones18)

    If you’re using one of these hosts, it may be part of their problems today:
    Bluehost, HostGator, HostMonster and JustHost
    Here’s the site where they’re posting updates:
    http://enduranceresponse.com/

    If it’s not one of those hosts, more information may help with figuring out the problem.

    Yes, justhost.com..
    I don’t know how to solve the problem..!
    I’ll contact justhost support soon.

Viewing 15 replies - 1 through 15 (of 27 total)
  • The topic ‘Fatal error and 404 after 3.6 upgrade WP Multisite’ is closed to new replies.