Title: Fatal error Last modified: August 20, 2016 --- # Fatal error * [wowfirst](https://wordpress.org/support/users/wowfirst/) * (@wowfirst) * [14 years, 8 months ago](https://wordpress.org/support/topic/fatal-error-386/) * While updating plugins at [http://easypermissions.com](http://easypermissions.com) the page all of a sudden went blank except for this message: * “Fatal error: Call to undefined method stdClass::set_prefix() in /home/chris392/ public_html/easypermissions.com/wp-includes/load.php on line 337” * When I try and visit the site the same message appears. * My hosting provider tells me it is a WordPress issue, not a server issue. * As a precaution, I have backed-up my files and databases. * Can anyone tell what specific steps I need to take to correct this issue? * Thanks. Viewing 15 replies - 1 through 15 (of 15 total) * [esmi](https://wordpress.org/support/users/esmi/) * (@esmi) * [14 years, 8 months ago](https://wordpress.org/support/topic/fatal-error-386/#post-2319343) * Try: – switching to the Twenty Eleven theme by renaming your current theme’s folder in wp-content/themes and adding “-old” to the end of the folder name using [FTP](http://codex.wordpress.org/FTP_Clients) or whatever file management application your host provides. * – [resetting the plugins folder](http://codex.wordpress.org/FAQ_Troubleshooting#How_to_deactivate_all_plugins_when_not_able_to_access_the_administrative_menus.3F) by FTP or phpMyAdmin. * Thread Starter [wowfirst](https://wordpress.org/support/users/wowfirst/) * (@wowfirst) * [14 years, 8 months ago](https://wordpress.org/support/topic/fatal-error-386/#post-2319616) * Hello Esmi: * Thanks for your response. * I am new to programing, so I would appreciate it if you could tell me if I have the following steps correct: * 1) In c-panel click on File Manager * 2) Under File Manager Directory Selection (1) click on easypermissions.com under“ document Root for,” (2) Select “Web Root (public_html/www) * 3) Click on “go” * 4) Under Name, double click on easypermissions.com folder * 5) Double click on wp-content folder * 6) Click to highlight wp-themes folder * 7) Click on Rename in Toolbar * 8) In “rename” window change “themes” to “Twenty Eleven-old” * Have I got it right? * Thanks in advance for your help! * Thread Starter [wowfirst](https://wordpress.org/support/users/wowfirst/) * (@wowfirst) * [14 years, 8 months ago](https://wordpress.org/support/topic/fatal-error-386/#post-2319764) * Hello Esmi: * As you suggested, I want to switch the Twenty Eleven theme. Do I have the above steps correct? * Thanks. * [Ryan Yu](https://wordpress.org/support/users/geeksfolder/) * (@geeksfolder) * [14 years, 8 months ago](https://wordpress.org/support/topic/fatal-error-386/#post-2319765) * In the “wp-content” folder, you should have “themes” folder, NOT wp-themes. * In the “themes” folder, you should see the “twentyeleven” folder. As esmi suggested, rename it to “twentyeleven-old”. * If it doesn’t solve the issue, you may want to try the second suggestion esmi gave, [resetting the plugins folder](http://codex.wordpress.org/FAQ_Troubleshooting#How_to_deactivate_all_plugins_when_not_able_to_access_the_administrative_menus.3F). * Please let us know if those steps solved your issue 🙂 * Thread Starter [wowfirst](https://wordpress.org/support/users/wowfirst/) * (@wowfirst) * [14 years, 8 months ago](https://wordpress.org/support/topic/fatal-error-386/#post-2319793) * Hello Geeksfolder: * Thank you for your response. * There is no “twentyeleven” folder. * There is a “twentyten” folder. I renamed it to “twentyten-old” and “twentyeleven- old.” No change in either case. * I reset the plugins using phpMyAdmin. There is no change. * I would appreciate other suggestions. * Thanks. * [Ryan Yu](https://wordpress.org/support/users/geeksfolder/) * (@geeksfolder) * [14 years, 8 months ago](https://wordpress.org/support/topic/fatal-error-386/#post-2319794) * Hi wowfirst, * As you had this issue while updating the plugin, the plugin might be causing the issue. The plugin may be trying to extract values from array but somehow it crashed. * Do you remember which plugin you were updating? * Thread Starter [wowfirst](https://wordpress.org/support/users/wowfirst/) * (@wowfirst) * [14 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-386/#post-2319800) * Hi weeksfolder: * Unfortunately, I don’t remember the plugin I was updating when the error occurred. * I do know that it was probably one of the following plugins: * Add to Footer, Akismet, All in One SEO Pack, AmazonPress, AutoChimp * AWeber Integration, BNS Corner Logo, Contact Form 7 * DBC Backup, Exclude Pages from Navigation, Feed Styler, * Header and Footer, Hello Dolly, s2Member, Secure WordPress * Simple Image Link * Does this help? * Thanks * [Ryan Yu](https://wordpress.org/support/users/geeksfolder/) * (@geeksfolder) * [14 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-386/#post-2319801) * What you can do is to deactivate the plugin one by one and see if one of the plugins is causing the issue. * As it would be something to do with cache or database, try by this order. – DBC Backup – Secure WordPress – s2Member – Feed Styler – AmazonPress – AutoChimp and rest of the plugins * Thread Starter [wowfirst](https://wordpress.org/support/users/wowfirst/) * (@wowfirst) * [14 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-386/#post-2319807) * Unfortunately, when I try to log-in via [http://easypermissions.com/wp-login.php](http://easypermissions.com/wp-login.php) the same Fatal Error message (see above) comes up. * Is there another way to log-in? * Thanks. * [esmi](https://wordpress.org/support/users/esmi/) * (@esmi) * [14 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-386/#post-2319808) * Please see the 2nd link I gave right at the start of this topic. * Thread Starter [wowfirst](https://wordpress.org/support/users/wowfirst/) * (@wowfirst) * [14 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-386/#post-2319810) * I tried to reset plugins using phpMyAdmin (see 4th entry above). There was no change. * Would it make a difference if I reset plugins via FTP? * Thanks. * [Ryan Yu](https://wordpress.org/support/users/geeksfolder/) * (@geeksfolder) * [14 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-386/#post-2319812) * It seems like there’s something else going on. Can you access your FTP and rename. htaccess? * Also check if your hosting server has enough space. * Thread Starter [wowfirst](https://wordpress.org/support/users/wowfirst/) * (@wowfirst) * [14 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-386/#post-2319821) * My hosting company says there is enough space. * To rename .htaccess, are the following steps correct? * 1) Open File Manager in cpanel 2) Select Public FTP Root (public_ftp), click GO 3) Double cliek on /home 4) Click on .htaccess 5) Click on Rename * If so, what should I rename it? * Thanks. * [Ryan Yu](https://wordpress.org/support/users/geeksfolder/) * (@geeksfolder) * [14 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-386/#post-2319822) * To .htaccess_old We are trying to see if .htaccess has an issue. * Also can you paste the code from .htaccess ? * Thread Starter [wowfirst](https://wordpress.org/support/users/wowfirst/) * (@wowfirst) * [14 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-386/#post-2319828) * I renamed .htaccess to .htaccess_old. This had no effect. * Where do I find the “code from .htaccess”? * Where do I paste it? * Thanks. Viewing 15 replies - 1 through 15 (of 15 total) The topic ‘Fatal error’ is closed to new replies. ## Tags * [fatal error](https://wordpress.org/support/topic-tag/fatal-error/) * [plugins update](https://wordpress.org/support/topic-tag/plugins-update/) * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) * 15 replies * 3 participants * Last reply from: [wowfirst](https://wordpress.org/support/users/wowfirst/) * Last activity: [14 years, 7 months ago](https://wordpress.org/support/topic/fatal-error-386/#post-2319828) * Status: not resolved ## Topics ### Topics with no replies ### Non-support topics ### Resolved topics ### Unresolved topics ### All topics