Problem with upgrading 3.0 to 3.3

  • Resolved turkel

    (@turkel)


    14 years, 3 months ago

    Hi,

    I am trying to upgrade wordpress 3.0.3 to wordrpess 3.3.1 but i am getting following error after upgrade:

    Warning: Invalid argument supplied for foreach() in /home/xxx/public_html/wp-includes/functions.php on line 480

Warning: Cannot modify header information - headers already sent by (output started at /home/xxx/public_html/wp-includes/functions.php:480) in /home/xxx/public_html/wp-includes/ms-settings.php on line 90

    There are no any little errors in my site (WP v3.0.3) even on debug mode, installation is standard and no any modification. I only use multi db and some other plugins.
    I have tried to upgrade script to WP 3.1, but it gave me same error after upgrade too.

    Let me know please, what may be the problem in my site.

    Thanks,
    Turkel.

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

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    14 years, 3 months ago

    Get a fresh copy of the 3.3 files and manually upload them.

    Thread Starter turkel

    (@turkel)

    14 years, 3 months ago

    Yes I did it also, uploaded only wp-admin and wp-includes with index files and got same error 🙁

    Thread Starter turkel

    (@turkel)

    14 years, 3 months ago

    I have tried to repair database through:
    wp-admin/maint/repair.php

    ad i got following errors on my global database:

    vzd_1_posts: Table 'xxx_global.vzd_1_posts' doesn't exist
vzd_1_comments: Table 'xxx_global.vzd_1_comments' doesn't exist
vzd_1_links: Table 'xxx_global.vzd_1_links' doesn't exist
vzd_1_options: Table 'xxx_global.vzd_1_options' doesn't exist
vzd_1_postmeta: Table 'xxx_global.vzd_1_postmeta' doesn't exist
vzd_1_terms: Table 'xxx_global.vzd_1_terms' doesn't exist
vzd_1_term_taxonomy: Table 'xxx_global.vzd_1_term_taxonomy' doesn't exist
vzd_1_term_relationships: Table 'xxx_global.vzd_1_term_relationships' doesn't exist
vzd_1_commentmeta: Table 'xxx_global.vzd_1_commentmeta' doesn't exist

    So first I want to know why it looks for main site at globals database instead of own database which is xxx_c ?
    What do this means and how to repair it ?
    This wordpress site root is came from version 2.7 by upgrading.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    14 years, 3 months ago

    Don’t do a repair that way. WP has a weird hissy fit about the DB tables.

    Can you use PHPMyAdmin to repair the DB?

    Thread Starter turkel

    (@turkel)

    14 years, 3 months ago

    yes sure going to do this now, but I think it will only optimize tables which is not related to my problem, but wordpress repair tool checks for not existing databases.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    14 years, 3 months ago

    It doesn’t. I mean, it does, but it’s not. It’s looking for tables that don’t exist because they don’t HAVE to. Like I said, it gets hissy.

    Go in and REPAIR the DB via phpmyadmin.

    Thread Starter turkel

    (@turkel)

    14 years, 3 months ago

    OK I have repaired then optimized globals and xxx_c database which home site is located then upgraded, same result 🙁

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    14 years, 3 months ago

    Did you try renaming your plugins folder to plugins-old?

    And do you have a good backup?

    Thread Starter turkel

    (@turkel)

    14 years, 3 months ago

    Yes I did these and I have backup except wp-content folder

    Thread Starter turkel

    (@turkel)

    14 years, 3 months ago

    My wordpress MS is this:
    http://vsayt.com

    Thank you very much for all your help, can you try again, I can give you login details.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    14 years, 3 months ago

    I don’t log in to other people’s sites unless you’re hiring me.

    Copy the files from WP 3.0 (get it here http://wordpress.org/download/release-archive/ ) and see if your site comes back.

    IF SO. Then manually upgrade to 3.1

    Thread Starter turkel

    (@turkel)

    14 years, 3 months ago

    sorry

    I did it before, so I have upgraded 3.0.3 to 3.0.6 and it worked OK but then upgrade to 3.1 not worked, got same error 🙁

    Thread Starter turkel

    (@turkel)

    14 years, 3 months ago

    Problem still not solved 🙁
    Please, recommend me other things to do, I am already programmer, but not familiar with wordpress structure, so give me all possible outcomes to check please.

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    14 years, 3 months ago

    Go back to basic debugging.

    Rename the plugins and mu-plugins folders to something else and see if that lets you in.

    Thread Starter turkel

    (@turkel)

    14 years, 3 months ago

    nope, I have did it also, not helps.
    I have copied site to my wamp server now working there.
    While i use wp-admin database i am getting this message:

    Could not find site vsayt.com. Searched for table wp_blogs in database xxx_default. Is that right?

    xxx_default is default main site database without multi site installation but I have enabled multisite.
    As I know it have to look for domain on globals database but it doesn`t after upgrade. It have to read db.php file which makes site multi database but seems not works with multi DB.

    Problem is on connection to database, is there are any solution for this?

Viewing 15 replies - 1 through 15 (of 15 total)

The topic ‘Problem with upgrading 3.0 to 3.3’ is closed to new replies.