Support » Fixing WordPress » No access to admin dashboard after 4.2 upgrade

  • Resolved myboler

    (@myboler)


    I upgraded 3 of my sites to WP4.2 two sites upgraded fine but the 3rd site I cannot access the admin dashboard, all that I get is a screen saying:
    “No Update Required
    Your WordPress database is already up-to-date!”
    with a continue button which loads the index page.

    Tried rebooting and clearing cache, same results

Viewing 5 replies - 1 through 5 (of 5 total)
  • I too am unable to access the dashboard and am receiving the same message after upgrading to 4.2.
    No matter what I try it keeps looping me back to my site’s homepage.

    Please help.
    Thanks!

    This is most likely being caused by the get_avatar_url.

    Please take a look at your hosting error logs.

    If you look at the error log it will tell you which line contains the error and which file. An easy way to fix this would be to edit that file. Comment out the section that is causing the error. The file should be in your theme directory

    On the noted line (found in the error log) you should see a statement that is used for avatars. Comment out the entire thing by placing /* in front of the statement and */ immediately following it. This will exclude it from being processed. Your website should load just fine after making this change and the code will still be there, just excluded from processing.

    This function was built into WordPress in 4.2, but was previously something that the theme author had to bake in. In 4.2 the exact same statement that you commented out is included in wp-includes/link-template.php.

    Therefore, it is completely safe to remove it because it’s a duplicate code conflict. Commenting it out is just a safer way to explain to people. I hate telling people to remove code because they may remove the wrong thing.

    This is causing 4.2 to not load for many people.

    Thread Starter myboler

    (@myboler)

    My service provider (Dreamhost) fixed this issue by simply clearing the cache from their end.

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    My service provider (Dreamhost) fixed this issue by simply clearing the cache from their end.

    @myboler I’m really glad that this was resolved for you. 😉

    As this has devolved and been hijacked into another inappropriate subject I’m going to close this topic. If you have any further problems please feel free to start a new thread.

    https://wordpress.org/support/forum/how-to-and-troubleshooting#postform

    Thanks!

    Edit: The 4.2 Master Troubleshooting post discusses this part, if it was that get_avatar_url() issue.

    Fatal Error with Cannot redeclare get_avatar url()
    This is generally caused by a theme that has not yet been updated to be compatible with WP4.2. You can either manually deactivate the theme by renaming it on the server (use FTP or another file manager to access your site files on the sever) to mytheme.HOLD – which should let you login again. Then check whether the theme has a recent update – if so, update the theme and that should fix the problem.

    Alternatively, you can temporarily fix the error without removing the theme by editing that file. If you look at the error log it will tell you which line contains the error and which file. First make a backup copy of the file in a safe place just in case editing the file goes wrong! Then on the real file, comment out the entire section (function) that is causing the error by placing /* in front of the statement and */ immediately following it. This will exclude it from being processed.

    Why this broke: This function was built into WordPress in 4.2, but was previously something that the theme author had to include. In 4.2 the exact same statement that you commented out is included in wp-includes/link-template.php.

    So far the only themes that have been impacted by this are commercial ones.

    https://wordpress.org/support/topic/read-this-first-%e2%80%93-wordpress-42-master-list?replies=5&view=all#post-6860958

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘No access to admin dashboard after 4.2 upgrade’ is closed to new replies.