• I attempted to upgrade to WP 3.7.1 and it says it installed and upgraded yet when I go to upgrade plugins or install new plugins I get the following errors:

    You have the latest version of WordPress.
    Warning: require(/home/content/95/11989795/html/wp-admin/includes/class-wp-upgrader-skins.php) [function.require]: failed to open stream: No such file or directory in /home/content/95/11989795/html/wp-admin/includes/class-wp-upgrader.php on line 14

    Fatal error: require() [function.require]: Failed opening required ‘/home/content/95/11989795/html/wp-admin/includes/class-wp-upgrader-skins.php’ (include_path=’.:/usr/local/php5_3/lib/php’) in /home/content/95/11989795/html/wp-admin/includes/class-wp-upgrader.php on line 14

    What does this mean and how can I get this addressed?

Viewing 15 replies - 1 through 15 (of 18 total)
  • Moderator t-p

    (@t-p)

    Have you tried:
    – deactivating ALL plugins temporarily to see if this resolves the problem. If this works, re-activate them individually (one-by-one) to find the problematic plugin(s). If you can’t get into your admin dashboard, try deactivating via FTP or SFTP or whatever file management application your host provides. If applicable, also remember to deactivate any plugins in the mu-plugins folder. The easiest way is to rename that folder to mu-plugins-old.
    – To rule out any theme-specific issue, try switching to the unedited default, core-bundled Theme (such as Twenty Twelve or Twenty Thirteen) for a moment using the WP dashboard. If you don’t have access to your admin area, you can switch to the default theme by renaming your current theme’s folder in wp-content/themes and adding “-old” to the end of the folder name using via FTP or SFTP or whatever file management application your host provides. Alternately, you can remove other themes except the default theme. That will force your site to use it.
    resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems (because the hooks remain unless plugins completely removed or some plugins stick around in cached files. So by renaming the folder, you break them and force them inactive).
    – If the above troubleshooting steps fail to resolve the issue, try manually re-uploading all files and folders EXCEPT the wp-config.php file and the /wp-content/ directory from a fresh download of WordPress. Make sure that you delete the old copies of files & folder before uploading the new ones. Read the Manual Update directions first!

    Thread Starter dstprl

    (@dstprl)

    None of that helped. I called Go Daddy and they told me when I upgraded the upgrade file is missing. What do I do from here because I see there is a 3.8 version coming soon and I doubt I will be able to upgrade to that with this outstanding issue. Please advise. FYI, I am not a developer.

    See the last step in Tara’s post above.

    Moderator t-p

    (@t-p)

    I called Go Daddy and they told me when I upgraded the upgrade file is missing. What do I do from here because I see there is a 3.8 version coming soon and I doubt I will be able to upgrade to that with this outstanding issue.

    Fix this current issue that way you will be ready to recieve 3.8!

    As @wpyogi poited out, see the last step of my last reply.

    Thread Starter dstprl

    (@dstprl)

    Thanks Tara and WPyogi. I tried the previous steps and am resolved to manually reuploading all files and folders. I still have a question. Where is the wp-config.php file found? I do not see it right out. Are you saying NOT to overwrite the wp-content folder (leave that alone)?

    Thread Starter dstprl

    (@dstprl)

    Hi- I followed the steps of the manual installation and it brought down my site and I have to pay to get it restored through disaster recovery. I downloaded the manual upgrade and here is what I get when I try to access my domain now:

    Warning: require(/home/content/95/11989795/html/wp-includes/pomo/mo.php) [function.require]: failed to open stream: No such file or directory in /home/content/95/11989795/html/wp-settings.php on line 69

    Fatal error: require() [function.require]: Failed opening required ‘/home/content/95/11989795/html/wp-includes/pomo/mo.php’ (include_path=’.:/usr/local/php5_3/lib/php’) in /home/content/95/11989795/html/wp-settings.php on line 69

    I can’t even get it in.

    Moderator t-p

    (@t-p)

    You could try downloading a fresh copy of WordPress and uploading again via FTP.

    See instruction in my previous reply above.

    Thread Starter dstprl

    (@dstprl)

    Thanks Tara – I did switch to the more generic theme and did all the steps listed above. When I did a manual upgrade I was no longer able to access my blog and had to pay to get it restored via disaster recovery. Not sure – the issue still remains after it is recovered. Thanks.

    Thread Starter dstprl

    (@dstprl)

    What I will try is when 3.8 comes out deactivate plugins and switch to a generic theme and see if that works.

    Thread Starter dstprl

    (@dstprl)

    Tara – should I upload everything above but where do I find the wp-config file to not update it? The manual update directions states we overwrite the wp-content directory and contents vs. deleting and copying. Is that right or should I leave it alone?

    Thread Starter dstprl

    (@dstprl)

    Hi again – I downloaded the latest version of WP 3.7.1 last night right before I copied the files over and received the fatal error which required me to pay to recover my site.

    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 and the wp-config.php & root .htaccess files – 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

    Thread Starter dstprl

    (@dstprl)

    Thanks ESMI – I will try all of these steps. On the last bullet – to run the upgrade manually via wp-admin/upgrade.php – do you mean click on that file in the root folder via FTP after the previous changes are made?

    Thanks.

    Moderator t-p

    (@t-p)

    Thread Starter dstprl

    (@dstprl)

    Thanks Tara – I will try this again at a later date. My site crashed last night following those instructions verbatim and I can’t afford to keep paying them to recover it.

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘Received fatal errors’ is closed to new replies.