• Resolved spiros

    (@spiros)


    I tried with 2 sites from 4.6.1 and after the upgrade I get this URL and a blank page:
    upgrade.php?_wp_http_referer=%2Fwp-admin%2F

    The only way to fix it was change in version.php the $wp_db_version value (38590) to the one that I could see in the database (37965).

    Then I am able to log in but I am not sure if the sites have been properly upgraded or why this happens.

    • This topic was modified 8 years, 3 months ago by spiros.
Viewing 12 replies - 1 through 12 (of 12 total)
  • Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Thread Starter spiros

    (@spiros)

    Hi, thanks. Is my fix problematic? Because I can see the Dashboard mentioning I have 4.7 for these sites…

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    If it looks OK and works OK, let’s assume it’s OK. ??

    I had the same issue as the OP and resolved it by matching DB numbers I was recieving the same URL
    upgrade.php?_wp_http_referer=%2Fwp-admin%2F

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.remarpro.com Admin

    The version value is used to run the database update routines. If you manually change it, then you’re not running the database updates. This can cause unforeseen problems in the future, so I recommend NOT editing those version numbers manually, and instead figuring out what about your server is not allowing you to run the upgrade routine.

    Specifically, look in your PHP error logs.

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.remarpro.com Admin

    Note that in this particular case for 4.7, doing that should not break anything as there were no major database changes. However, you still need to find the root cause of the problem, because you may have future issues along these same lines.

    Thread Starter spiros

    (@spiros)

    Can the database update routines be run manually from phpmyadmin?

    Thread Starter spiros

    (@spiros)

    I turned on debugging and got:

    Warning: mysqli_real_connect(): Headers and client library minor version mismatch. Headers:50550 Library:100028 in public_html/wp-includes/wp-db.php on line 1538

    Notice: register_sidebar was called incorrectly. No id was set in the arguments array for the “Sidebar” sidebar. Defaulting to “sidebar-1”. Manually set the id to “sidebar-1” to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (This message was added in version 4.2.0.) in public_html/wp-includes/functions.php on line 4091

    Notice: The called constructor method for WP_Widget in mts_Widget_Tabs is deprecated since version 4.3.0! Use
    __construct()
    instead. in public_html/wp-includes/functions.php on line 3846

    Notice: The called constructor method for WP_Widget in mts_ad_widget is deprecated since version 4.3.0! Use
    __construct()
    instead. in public_html/wp-includes/functions.php on line 3846

    Notice: The called constructor method for WP_Widget in mts_ad_300_widget is deprecated since version 4.3.0! Use
    __construct()
    instead. in public_html/wp-includes/functions.php on line 3846

    Notice: The called constructor method for WP_Widget in mts_ad_728_widget is deprecated since version 4.3.0! Use
    __construct()
    instead. in public_html/wp-includes/functions.php on line 3846

    Notice: The called constructor method for WP_Widget in mts_pp_Widget is deprecated since version 4.3.0! Use
    __construct()
    instead. in public_html/wp-includes/functions.php on line 3846

    Notice: The called constructor method for WP_Widget in Facebook_Like_Widget is deprecated since version 4.3.0! Use
    __construct()
    instead. in public_html/wp-includes/functions.php on line 3846

    Notice: The called constructor method for WP_Widget in mts_subscribe_widget is deprecated since version 4.3.0! Use
    __construct()
    instead. in public_html/wp-includes/functions.php on line 3846

    Notice: The called constructor method for WP_Widget in Social_Profile_Icons_Widget is deprecated since version 4.3.0! Use
    __construct()
    instead. in public_html/wp-includes/functions.php on line 3846

    Notice: The called constructor method for WP_Widget in CategoryPosts is deprecated since version 4.3.0! Use
    __construct()
    instead. in public_html/wp-includes/functions.php on line 3846

    Warning: Cannot modify header information – headers already sent by (output started at public_html/wp-includes/wp-db.php:1538) in public_html/wp-includes/pluggable.php on line 1179

    I got this issue after the update function in the admin failed and I tried to manually update.

    I think it’s being caused by W3 Total Cache. The issue for me was that I needed to disable all plugins by renaming the plugin folder temporarily, but the admin refused to work without W3 Total Cache active.

    So I did the following:

    1. Download a copy of .htaccess (NOTE: this is the .htaccess file from your web ROOT) and name it .htaccess.bak. Save it somewhere safe.
    2. Edit the existing .htaccess on the server so that it ONLY contains what is between # BEGIN WordPress and # END WordPress.
    3. On your server, go to /wp-content. Rename the plugins folder to plugins.bak
    4. In your browser, go to https://YOURDOMAIN.com/wp-admin/upgrade.php. This should work fine now. Follow prompts, update database.
    5. After database update is successful, rename plugins.bak back to plugins.
    6. Replace the edited .htaccess on your server with the file you saved as .htaccess.bak (obviously, rename it back to .htaccess).
    Thread Starter spiros

    (@spiros)

    It was W3 Total Cache. I had it removed and upgrade worked perfectly.

    Thanks sgpark! Worked perfectly!

    Thank you sgpark That worked for me too!

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘After upgrade to 4.7 cannot log in to Admin’ is closed to new replies.