How to fix the failure of the WordPress update and the failure of the release

 WP rewrite structure \u0026#39;/%Postname%\u0026#39; 

In this case, before you continue to include your IP address on the whitelist as a fast repair, determine the reason for your IP to be prevented by your own WAF, please check you for you The analysis of the web application firewall to view which firewall rules have triggered.

Step 4 -View PHP error log and enable debugging mode in WordPress

Before using WP Debug and using WordPress’s own debugging system, those who use Servebolt will easily access your PHP error log.

By default, all sites running on the Servebolt Cloud will generate two logs

– -ERRORLOG

and Accesslog . These can be in the /LOGS folder in the root directory of your site (that is, as /Public directory at the same level). ERRORLOG files will include information that runs any code that runs on your site (this includes errors that do not destroy your site and will continue to fail in the background but sometimes occur) Essence

Moreover, if this does not provide any further information about the error source, you can enable the debug mode in WordPress. When you enter the debug mode, WordPress will automatically record any PHP response received in the new file named

defug.log

. This new file will appear in the WP-Content directory, so you only need to check to determine any server-side response that may cause the problem.

To enter the debug mode, please open your wp-config.php file and in the last line Added before:

// Enable wp_debug mode definition (\u0026#39; wp_debug \u0026#39;, true); // Removal to /wp-content/debug.log file record log record definition (\u0026 #39; wp_debug_log \u0026#39;, true); // Avoid displaying errors on the production site (if not declared, the default is true) definition (\u0026#39; wp_debug_display \u0026#39;, fake);

] After viewing the debug.log file, you can delete this code from the wp-config.php file to exit the debug mode. With serverbolt, you can visit PHP error logs by default, including errorLog and AccessLog. Except Slow query log You can ask for our support team. However, WordPress’s own debugging system is very suitable for identifying errors, so that you can run easily to control your code library.

This is indeed self-evident, but in

wp-config. When changing the pHP

, please do it with caution, which helps to back up your site. Websites running on Servebolt Cloud are backup twice a day -we run the day backup (3 days of storage) and night backup (storage 30 days).

You can also back up your WordPress website yourself. To restore backup, just contact our support team, we will restore your recent backup for free.

Step 5 -Disables all WordPress plug -in and check again If you suspect that the error is caused by the WordPress plug -in on your website Solve the problem.

For this reason, just turn to

plugins , and then select Installed plugins. Then, just choose all plug -ins, and use to operate in batches drop -down menu to stop them at one time.

Next, return to your screen, check whether the WordPress update or release failure still exists. If not, now you will know that the plug -in running on your website causes errors. At this stage, the brute force recognition method is to re -activate the plug -in to check when to report an error. Moreover, by eliminating the process, you will be able to identify the fault plug -in.

After discovering the problem, we strongly recommend that you contact the plug -in author and let them know and provide any information they need to debug, because it helps them to improve their products for you (and all other users). This is of course not our first choice during debugging, because it is obviously very tedious and time -consuming.

Temporary solution: Installing classic editor plug -ins (not a solution) The launch of the version 5.0 version of WordPress marks the launch of the Gutenberg editor, that is, we are widely called today. 123] Concept.

Although this is just a temporary solution, switching from Good Tengbao editor to the classic editor may allow you to save and update your post.

Note:

This is obviously not a solution, so it can only be used as a temporary solution.

To switch from Gutenberg to Classic Editor, you only need to the Classic Editor plug -in and activate it on your site. Once it is activated, you only need to return to the post you are editing, and then you should be able to update or publish it again as usual.

Step 7 -Contact our support team

If the above cannot solve your problem, and you have made a wise decision to host your WordPress website on the Servebolt cloud, Please contact our support team at any time. We can contact us by chatting and email. Our team will be very happy to investigate the cause of this problem.
• Conclusion

In particular, it is not what anyone wants to prevent you from preserving your work or clicking the error you have been dealing with. Therefore, although you encourage you to often find direct repair and temporary solutions, we strongly recommend that you determine the root cause of the problem so that you can take measures to ensure that it will not happen again.

• Are you interested in the faster custody host? Try the server:
• Extensible: In the actual user work load test, the average response time of the server is 65 milliseconds, which is 4.9 times faster than the second response time faster than the second response time. Essence

The fastest global loading time:

The average page load time of 1.26 seconds allows us to be among the best in the global webpageTest results list.

The fastest calculation speed:

Servebolt server provides the database speed of the previously unheard of database. The query per second is 2.44 times higher than the average speed. 2.6 times!