Resolving WordPress errors may seem difficult, especially for new users, but in reality this is not the case – most WordPress errors can be fixed quickly and easily. this Maximum execution time exceeded The error is very common. It can appear when doing something as simple as updating WordPress, themes or plugins. When it appears, the error is followed by a message similar to the following:
Fortunately, this fatal WordPress bug has a very simple fix. In this article, we’ll show you a few different solutions you can try, for example:
Resolving the Error
The maximum execution time (max_execution_time) is a time limit on how long a PHP script can run. It is a way that hosting providers can limit the use and abuse of server resources, especially for shared hosting. The actual default value depends on hosting but is usually set to 30. (ie 30 seconds). If a script exceeds the time limit, Maximum execution time of X seconds exceeded error. The easiest solution to this problem is to increase the time limit. Changing it to 300 seconds (5 minutes) is usually more than enough.. If that doesn’t work, you can try setting even higher values for the maximum execution time.
Before we continue, some of these solutions will involve editing local WordPress files, so be sure to back up your site beforehand.
We will show you four different ways to increase max_execution_time by adjusting the values set in local WordPress files. The first two methods are for cPanel users, the other two are for FTP client users.
Sign in to cPanel using your credentials. go to: Software Click on the section and MultiPHP INI Editor.
In the new window, select your domain name from the drop down menufind your place max_execution_time PHP directive and change the value associated with it to 300.
To finish, press the Apply button at the bottom.
There is another way to change the same value in cPanel. If you are already logged in, go to: Software Click on the section and MultiPHP INI Editor.
In the new window, find and select Editor Mode tab Click it and then select your domain name from the drop-down menu at the bottom. Add the following line of code to the field below that:
max_execution_time = 300;
If the field already contains code for max_execution_time, simply change the value to 300.
To finish, Save button.
If you don’t have access to a hosting control panel, you can also increase the max_execution_time via FTP in the same way. connect to your server Go to the root WordPress directory using your FTP credentials (usually public_html). back then Find the .htaccess file inside. If you can’t see it, it’s probably hidden, so you need to enable showing hidden files in your FTP client. For example, in FileZilla the option is called Force show hidden files and you can find it below presenter tab.
after locating Right click on the .htaccess file on and choose Edit View from the drop-down menu.
Open the file using a text editor and then add the following code at the bottom:
php_value max_execution_time 300
Save the changes. Restore the edited file to your server to overwrite the old one.
If you can’t edit the .htaccess file, the file permissions probably need to be set. Here’s how you can set file permissions for the .htaccess file: 644 typing read and write. You can do this by locating the .htaccess file and right-clicking on it and File permissions… choice. Find numerical value Write the number in the field 644button and then OK.
come back now Editing the .htaccess file. Change execution time by adding php_value max_execution_time 300– just as mentioned above. Save the changes and load the edited file to your server to overwrite the old one.
You can also increase the max_execution_time value by editing the wp-config.php file. Connect to your server via FTP and navigate to the root WordPress directory (usually public_html). find wp-config.php file, right click on it and select Edit View from the drop-down menu.
Open the file using a text editor and /* That’s it, stop editing! Happy blogs. */ liner. Just add the following code above:
set_time_limit(300);
If you can’t edit the wp-config.php file, the file permissions probably need to be set. Default permissions for this are usually set to 440 or 400. These permissions only grant read privileges, so you need to temporarily set them to 644 or 666 so you can write too.. Right-clicking on the wp-config.php file and File permissions… choice.
Find numerical value area and type 644 or 666 there. print OK to finish.
Then edit wp-config.php file as stated above. When you’re done, save the file and upload it to your server to overwrite the old one. After that (and when you check if the error is gone), change permission on wp-config.php File back to 440 or 400.
If you’ve tried increasing the allowed execution time and that didn’t help, then the error could be due to a faulty plugin or theme. To check if this is the case, log into your WordPress admin dashboard and navigate to: Plugins > Installed Plugins. back then start deactivating your plugins one by one. Disable one then check if the error persists; continue like this until you’ve reviewed all your plugins. When the error stopped showing, the last plugin you disabled was causing the problem.
If you’ve tested all the plugins and still haven’t found the problem, try replacing your current theme with another theme. We recommend using one of the WordPress default themes like Twenty Twenty. If the error notification stops after changing themes, your theme was causing the problem.
This can be solved even more easily if you are using WordPress 5.2 or higher. Any fatal error prompts newer WordPress versions to send a message to the admin email address. This message will contain information Which plugins/themes are currently paused due to fatal errors and what exactly are these errors?. You will be provided with a link so that you can access the recovery mode and continue troubleshooting from there.
Therefore, once you determine whether the theme or the plugin is causing the error, you should contact their authors for further assistance.
final thoughts
this Maximum execution time Exceeded error is a relatively common error, and now you’ve seen that there are a few simple solutions to it. We hope that the steps and methods we show you here will help you troubleshoot the problem with ease. Feel free to bookmark or save this page so you can refer to these tips again in case you need them again.
Support our work ❤️
If you enjoyed this article, consider leaving a tip to help us keep publishing great content.
