• Resolved totisara

    (@totisara)


    My client took the liberty of trying to upgrade her blog to WordPress 3.4 – however when she did this… she told me that she started getting a “Page not found” error whenever she tried to log into her account. She/I can no longer see her dashboard – whenever I log in to her WordPress it automatically redirects me to:

    https://melissassimplysweet.com/wp-admin/upgrade.php?_wp_http_referer=%2Fwp-admin%2F

    … rather than taking me to her dashboard. I’ve read that it could be a plugin conflict issue and that I should try to disable all WP plugins. Since I can’t get to the WP dashboard anymore, I tried to disable them through her MySQL database, however I do not know what I’m doing with MySQL and whenever I tried running the script:

    UPDATE wp_options SET option_value = ” WHERE option_name = ‘active_plugins’;

    … to disable all plugins, it notifies me “#1146 – Table ‘melissassimply.wp_options’ doesn’t exist”

    Not sure what is causing this issue but I’m really at a loss here as to what to do. I’d like to just get everything back to the way it was and downgrade to the previous version of WordPress but I don’t want to lose her current WP pages and posts. Can anyone please help?

Viewing 14 replies - 16 through 29 (of 29 total)
  • What exactly did you do when you re-uploaded the Twenty Eleven theme?

    Thread Starter totisara

    (@totisara)

    I downloaded the file from the link you provided, took the twentyeleven folder, dragged it into the “themes” folder on her FTP, and when the notification came up to replace/override the current “twentyeleven” theme folder that had already existed there, I told it to override.

    Then, when I went to view the website again, it just had a white screen. :\

    Try deleting the whole themes/twentyeleven folder and then uploading a fresh copy. I’d also suggest contacting your hosts to see if you have access to your site’s error logs. They could be invaluable in determining where the problem actually is.

    Thread Starter totisara

    (@totisara)

    Thanks everyone for taking the time to help me. I tried deleting the twentyeleven theme folder and uploading a fresh one, but the website still remained white. I contacted GoDaddy and they figured out the solution for me, even though it was not an issue on the GoDaddy side. Just thought I’d share in case anyone in the future has this issue:

    Since I had been able to view the website just fine but could not log in to her WP dashboard, they figured it was an issue with the database when she tried to upgrade to the latest WP version (within WordPress, not from GoDaddy). Turns out her install of WP was not seamless, and somehow the database number differed from the actual database number it was upgraded to – inside of the wp-includes folder, version.php was still showing the old database number. Since the install was successful in updating the new database number, but the one that was inside of the version.php file (that had to be changed manually, in this instance) was the old number, it crashed whenever I tried to log in.

    Thank you for posting the solution. This may help someone else in the future. ??

    Russ

    (@gfxdesigner)

    Thanks for providing that info! That was my issue.

    How did you find the actual database number to change in version.php?

    I too am experiencing the exact same thing on 2 sites and actually created a previous thread to help trouble shoot the issue.

    I have about 4 other sites but am afraid to upgrade any of those to 3.4.2.

    2 quick questions…

    1) I’m pretty sure the database fix is what I need as everything you did I did with the exact same outcome. So, knowing this is the issue, how do you actually fix it? How do you change the database number?

    2) I upgraded both of my sites on an iPad instad of a computer. I’ve done this countless times without ever having any issues. Could this have been the cause somehow?

    Thanks.

    How did you find the actual database number to change in version.php?

    You should able find that wp_options table look for db_version

    Just had the same 404 error problem while upgrading to 3.4.2.
    I could see my website but couldn’t get to the dashboard.
    Any attempts resulted in 404 error with url:
    https://mysite.com/wp-admin/upgrade.php?_wp_http_referer=%2Fwp-admin%2F

    After reading many posts, I tried renaming the theme directory name – this resulted in white screen, so I changed it back.
    Looked at contents of the htaccess file – looked fine, except permission was 604 instead of 644. Changed it, but didn’t help.

    This is what worked:
    Downloaded 3.4.2. Deleted all files in wp-admin top level only – I didn’t delete any files in subfolders (such as the css folder).
    Copied (FTP’d) wp-admin files from 3.4.2 download to wp-admin folder on host.
    Tried to go to the Dashboard and I got the message that the database needed updating, so I clicked to proceed. Update went fine. Was then able to access dashboard and everything is fine now.
    Hope this helps someone.

    I’m having a similar problem. I tried updating my site, https://www.soma1894.com/wordpress (through the Dashboard link) to 3.4.2 and now can’t sign on to my login/admin page, I get this error message:
    No Results Found
    The page you requested could not be found. Try refining your search, or use the navigation above to locate the post.

    I see a lot of info in this thread. Can anyone suggest the best course of action? Thanks.

    @lylede
    Normally you should start a new post. Strap hanging to a post marked resolved won’t get you much help.

    Try to log in here,

    https://soma1894.com/wordpress/wp-login.php

    My apologies, I’m a little new to wordpress support and didn’t realize strap hanging to a post marked resolved was improper etiquette.

    And I tried the link you provided but got the same error message.

    Open a fresh copy of 3.4.2. Using ftp upload the wp-admin and wp-includes folders to the server.

Viewing 14 replies - 16 through 29 (of 29 total)
  • The topic ‘Page not found after upgrading to WordPress 3.4’ is closed to new replies.