Title: Auto updates causing fatal errors Last modified: August 30, 2016 --- # Auto updates causing fatal errors * [ScottishCartoons](https://wordpress.org/support/users/scottishcartoons/) * (@scottishcartoons) * [10 years, 7 months ago](https://wordpress.org/support/topic/auto-updates-causing-fatal-errors/) * Over the past week our site has been knocked offline three times by auto updates which have caused fatal and syntax errors (see below). Since there is no way to log in to our control panel who the site is down we have had to contact our host server and have them restore the site each time using a prior back up. Is there a way to disable these updates? Or to ensure that future additions do not result in the site going down? We are running WP version 4.3.1 and the Craft theme. * ERROR MESSAGES * Parse error: syntax error, unexpected ‘%’ in /home/xxxxxxxx/public_html/wp-includes/ functions.php on line 2902 * Fatal error: Call to undefined function wp_suspend_cache_addition() in /home/ xxxxxxxx/public_html/wp-includes/cache.php on line 391 * Warning: call_user_func_array() expects parameter 1 to be a valid callback, function‘ wp_ob_end_flush_all’ not found or invalid function name in /home/xxxxxxxx/public_html/ wp-includes/plugin.php on line 503 * Warning: require_once(/home/xxxxxxxx/public_html/wp-includes/cache.php): failed to open stream: No such file or directory in /home/xxxxxxxx/public_html/wp-includes/ load.php on line 439 * Fatal error: require_once(): Failed opening required ‘/home/xxxxxxxx/public_html/ wp-includes/cache.php’ (include_path=’.:/usr/local/lib/php’) in /home/xxxxxxxx/ public_html/wp-includes/load.php on line 439 * Parse error: syntax error, unexpected end of file in /home/xxxxxxxx/public_html/ wp-includes/functions.php on line 2877 Viewing 8 replies - 1 through 8 (of 8 total) * Moderator [t-p](https://wordpress.org/support/users/t-p/) * (@t-p) * [10 years, 7 months ago](https://wordpress.org/support/topic/auto-updates-causing-fatal-errors/#post-6701185) * Have you tried: – Flushing any caching plugins you might be running, as well as server and/or browser caches. Also, any op cache or content network cache, as well as Cloudflare, clear those caches. – deactivating ALL (yes all) plugins temporarily to see if this resolves the problem (plugin functions can interfere). 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 [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](http://codex.wordpress.org/FTP_Clients). Sometimes, an apparently inactive plugin can still cause problems. Also remember to deactivate any plugins in the mu-plugins folder (if you have created such folder). The easiest way is to rename that folder to mu-plugins-old. – switching to the unedited default Twenty Fifteen theme for a moment using the WP dashboard to rule out any theme-specific issue( theme functions can interfere like plugins). If you don’t have access to your admin area, use [FTP ](http://codex.wordpress.org/FTP_Clients), or your web-host’s cPanel or whatever file management application your host provides. Navigate to/ wp-content/themes/ and switch to the default theme by renaming your current theme’s folder by adding “-old” to the end of the folder name. Alternately, you can remove other themes except the default theme. That will force your site to use it. – If all the above steps do not resolve the issue, then try **MANUALLY** updating. Download a fresh copy of the WordPress .zip file to your computer, unzip it, and use that to copy up all files and folders **EXCEPT the wp-config.php file and the /wp-content/ directory.** You may need to delete the old wp-admin and wp-includes folders and files on your server before uploading the new ones. Read the [Manual Update ](http://codex.wordpress.org/Updating_WordPress#Manual_Update) directions first. –**Backup: If you haven’t already done, always backup everything( including your database) before doing any actions, just in case something really goes wrong.** * [kmessinger](https://wordpress.org/support/users/kmessinger/) * (@kmessinger) * [10 years, 7 months ago](https://wordpress.org/support/topic/auto-updates-causing-fatal-errors/#post-6701187) * See [https://codex.wordpress.org/Configuring_Automatic_Background_Updates](https://codex.wordpress.org/Configuring_Automatic_Background_Updates) * Thread Starter [ScottishCartoons](https://wordpress.org/support/users/scottishcartoons/) * (@scottishcartoons) * [10 years, 7 months ago](https://wordpress.org/support/topic/auto-updates-causing-fatal-errors/#post-6701282) * I’ve only a superficial understanding of WordPress and so nervous about trying any of the above. However this process has highlighted that the site has no wp- config.php file, instead there is a piece of code that seems to have been written to compensate for the original web designer’s inability to create the file when establishing the site. Is this something that needs to be addressed before trying anything else? * [esmi](https://wordpress.org/support/users/esmi/) * (@esmi) * [10 years, 7 months ago](https://wordpress.org/support/topic/auto-updates-causing-fatal-errors/#post-6701283) * I would say so, yes. What is in this piece of code? * Thread Starter [ScottishCartoons](https://wordpress.org/support/users/scottishcartoons/) * (@scottishcartoons) * [10 years, 7 months ago](https://wordpress.org/support/topic/auto-updates-causing-fatal-errors/#post-6701286) * As below, named setup-config.php * _[ Lengthy unreadable code deleted ]_ * Thread Starter [ScottishCartoons](https://wordpress.org/support/users/scottishcartoons/) * (@scottishcartoons) * [10 years, 7 months ago](https://wordpress.org/support/topic/auto-updates-causing-fatal-errors/#post-6701287) * I don’t think I can post it here but having looked through it it’s definitely a measure to get past a problem with wp-config.php at the outset (several years ago). * Moderator [Jan Dembowski](https://wordpress.org/support/users/jdembowski/) * (@jdembowski) * Forum Moderator and Brute Squad * [10 years, 7 months ago](https://wordpress.org/support/topic/auto-updates-causing-fatal-errors/#post-6701288) * Hi [@scottishcartoons](https://wordpress.org/support/users/scottishcartoons/) Please don’t post that many lines of code in these forums. It doesn’t work. * What is the filename and directory for that code you posted? * Thread Starter [ScottishCartoons](https://wordpress.org/support/users/scottishcartoons/) * (@scottishcartoons) * [10 years, 7 months ago](https://wordpress.org/support/topic/auto-updates-causing-fatal-errors/#post-6701289) * Apologies, Jan. First time poster. I don’t think it matters. Clearly there’s a fundamental problem with the site, something I wouldn’t wish to waste your volunteers’ time with. Viewing 8 replies - 1 through 8 (of 8 total) The topic ‘Auto updates causing fatal errors’ is closed to new replies. ## Tags * [fatal](https://wordpress.org/support/topic-tag/fatal/) * [update](https://wordpress.org/support/topic-tag/update/) * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) * 8 replies * 5 participants * Last reply from: [ScottishCartoons](https://wordpress.org/support/users/scottishcartoons/) * Last activity: [10 years, 7 months ago](https://wordpress.org/support/topic/auto-updates-causing-fatal-errors/#post-6701289) * Status: not resolved ## Topics ### Topics with no replies ### Non-support topics ### Resolved topics ### Unresolved topics ### All topics