WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] [closed] Automatic update to 3.5 failed (22 posts)

  1. juvenile38
    Member
    Posted 1 year ago #

    I tried to automatically update to 3.5 and it failed.

    By deleting the .maintenance file and the upgrade folder I was able to restore my site.

    However I can't seem to access the admin section and I'm seeing the following error...

    Fatal error: Call to undefined function get_taxonomies_for_attachments() in /home/content/34/7971934/html/main/wp-admin/menu.php on line 67

    Does anyone know what to do to fix this problem? Any help would be greatly appreciated!

  2. killem
    Member
    Posted 1 year ago #

    same here, we shouldn't update wordpress so early... It's seems to beta version still

  3. juvenile38
    Member
    Posted 1 year ago #

    I only did it because it told me too. I don't think they would push a beta like that would they?

    Very frustrating.

  4. twinklewitch
    Member
    Posted 1 year ago #

    Same here. Updated 2 sites just fine, third one doesn't want to at all, always giving me the same error.

  5. killem
    Member
    Posted 1 year ago #

    Found it ! click

  6. juvenile38
    Member
    Posted 1 year ago #

    The doesn't link to anything?

  7. pie154
    Member
    Posted 1 year ago #

    I am having the same problem on one of the websites I run (after update to 3.5), any help getting pointed in the right direction would be much appreciated. Thanks

  8. wphelpplease
    Member
    Posted 1 year ago #

    Can someone please tell me how to embed video with 3.5 please my jw player wont work

  9. JasmineZhu
    Member
    Posted 1 year ago #

    Hey guys having the same problem since updating to the new 3.5 version...
    Fatal error: Call to undefined function get_taxonomies_for_attachments() in /home/public_html/wp-admin/menu.php on line 67

    Please help anyone! I've tried renaming the plugins folder but that doesn't work.

  10. Dion Hulse
    WordPress Dev
    Posted 1 year ago #

    Fatal error: Call to undefined function get_taxonomies_for_attachments() in /home/public_html/wp-admin/menu.php on line 67

    This error unfortunately means your upgrade didn't complete successfully, there's no easy way around this - you'll need to re-upload your WordPress files.

    In order to do this, you'll need to download the WordPress .zip file, and FTP all the files from the zip (other than wp-content) to your host, using the instructions here:
    http://codex.wordpress.org/Updating_WordPress#Manual_Update

  11. juvenile38
    Member
    Posted 1 year ago #

    In the steps it says to do the wp-content...should this just be skipped? Also when deactivating the plugins manually does this mean they're deleted? Or just temporarily unusable? One of the plugins I use is for a forum and can not afford to lose it...

    Thanks again for the help!

  12. Roy
    Member
    Posted 1 year ago #

    Just hopping in halfway the discussion, but if you have problems with a running website, you can deactivate all plugins by renaming the /wp-content/plugins folder (just rename, do not delete).
    You probably don't have to edit wp-config.php, but don't overwrite it. On the other hand, making a new one never hurts, since even wp-config.php has been changed over the years.
    If all fails, just remove all wp files except wp-config.php (but note my earlier remark) and wp-content/themes and upload the files using FTP and using an unzipped file from the download link on top of this page.

  13. juvenile38
    Member
    Posted 1 year ago #

    Ok just finished my manual install and everything is back to normal!

  14. splurj
    Member
    Posted 1 year ago #

    I managed to access the dashboard by replacing the menu.php file from the 3.5 update with the 3.4 menu.php.

    And now I'm trying the 3.5 update again, fingers crossed.

  15. esmi
    Forum Moderator
    Posted 1 year ago #

    No! You cannot mix files like that! Try re-uploading all files & folders - except the wp-content folder - from a fresh download of WordPress. Make sure that you delete the old copies of files & folder before uploading the new ones.

    If you continue to have problems, please post your own topic.

  16. splurj
    Member
    Posted 1 year ago #

    The update does take a while, I think the first time I tried to press the update button twice, maybe that's what caused the problem?

    Still updating...

  17. splurj
    Member
    Posted 1 year ago #

    I wasn't planning to keep the old file, I just needed to be able to access the dashboard to try the update again.

  18. splurj
    Member
    Posted 1 year ago #

    Bingo! It worked :)

  19. esmi
    Forum Moderator
    Posted 1 year ago #

    Excellent! :-)

  20. splurj
    Member
    Posted 1 year ago #

    Conclusion:
    If you get the error replace the menu.php file with the 3.4 version, then you can get into your dashboard.

    Run the update again in one browser tab, open the website in another, once the update is finished the website will load up but the update page doesn't seem to change or say 'finished', open a new tab and access your /wp-admin dashboard/ it should ask you to update your database, click OK, and you're in!

  21. esmi
    Forum Moderator
    Posted 1 year ago #

    That fix will not work for everyone by a long chalk. The best aporiach is to try:
    - switching to the default theme by renaming your current theme's folder inside wp-content/themes and adding "-old" to the end of the folder name using FTP or whatever file management application your host provides.

    - resetting the plugins folder by FTP or phpMyAdmin.

    - re-uploading all files & folders - except the wp-content folder - from a fresh download of WordPress. Make sure that you delete the old copies of files & folder before uploading the new ones.

    - running the upgrade manually via wp-admin/upgrade.php

  22. splurj
    Member
    Posted 1 year ago #

    Fair enough, I'm no expert by a long shot but it worked for me anyway.

Topic Closed

This topic has been closed to new replies.

About this Topic