• Hello,

    Before upgrading we have 2 tables: wp_1_options and wp_2_options but after automatic upgrading, we received this from the log file:

    WordPress database error Table ‘coffeemu_ld.wp_0_options’ doesn’t exist for query SELECT option_value FROM wp_0_options WHERE option_name = ‘wp_0_user_roles’ LIMIT 1 made by require_once(‘C:\\wamp\\www\\linedata\\wp-admin\\admin-header.php’), do_action(‘in_admin_header’), call_user_func_array, wp_admin_bar_render, do_action_ref_array, call_user_func_array, wpseo_admin_bar_menu, get_admin_url, get_site_url, switch_to_blog, WP_Roles->reinit, get_option, referer: https://www.linedata.com/wp-admin/

    The thing is, this table wp_0_options does not exist at all. Do you know how to fix this bug?

    Thanks for your help. I appreaciate it.
    Hieu

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter hieu.nguyen

    (@ndh611)

    There are also similar log errors for other files, besides admin-header.php, such as: update-core.php, settings.php

    Thanks,
    Hieu

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    There shouldn’t be a _0_ call at all…

    Go into your DB via phpMyAdmin and try running a repair there.

    Laurence Tuck

    (@laurenceshowmecoza)

    Any luck with this error Hieu?

    Thread Starter hieu.nguyen

    (@ndh611)

    No luck. Did my best but no luck.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    What happened with the DB repair? You never came back…

    Also what do you have for the Multisite section of your wp-config.php?

    Laurence Tuck

    (@laurenceshowmecoza)

    @ipstenu: repairing the db is not going to fix this issue. WordPress is referencing a blog that doesn’t exist and quite possibly using its ID, which in this case is 0 (or not set for some reason). The function calling wp_0_options… (or whichever table) is receiving an empty ID. My suspicion is that this is plugin related.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Laurence: You’d think, but sometimes when a DB barfs, it gets really stupid with the error messages. I have, personally, solved that problem with a DB repair, so it doesn’t hurt to try, does it? ??

    It would also be an exceptionally daft plugin (though this is possible) to be defining wp_0 anywhere. Plugins should be using WP functions which can auto-detect.

    But of course there’s an EASY test for this. Rename plugins to plugins-old. See if the problem goes away.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘WP Multisite broken after upgrade from 3.4 to 3.5.1’ is closed to new replies.