{"id":24484,"date":"2022-01-27T08:00:38","date_gmt":"2022-01-27T06:00:38","guid":{"rendered":"https:\/\/vipestudio.com\/how-to-fix-the-max-execution-time-error-on-wordpress-increasing-the-limit-part-2\/"},"modified":"2022-01-27T08:00:38","modified_gmt":"2022-01-27T06:00:38","slug":"how-to-fix-the-max-execution-time-error-on-wordpress-increasing-the-limit-part-2","status":"publish","type":"post","link":"https:\/\/vipestudio.com\/en\/how-to-fix-the-max-execution-time-error-on-wordpress-increasing-the-limit-part-2\/","title":{"rendered":"How to Fix the Max Execution Time Error on WordPress: Increasing the Limit (Part 2)"},"content":{"rendered":"

And\u2026. We’re back, wrapping up this series on handling the WordPress max_execution_time<\/strong> fatal error. In the preceding part<\/a>, we described how the error occurs, and how we can remove the element that’s the cause of the error. This time, we’ll be taking a different approach \u2013 actually increasing the time limit \u2013 either with a plugin, by making changes to some files, or by just contacting your host. Read on to find out!<\/p>\n

\"\"<\/p>\n

Increase the Time Limit with a Plugin<\/h2>\n

As discussed previously, this time limit exists for a good reason \u2013 protecting your server from unoptimized elements like themes<\/a> and increasing your website security<\/a>.<\/p>\n

On the other hand, sometimes you legitimately need to give a particularly heavy element a little more time, or your hosting provider may have set a particularly sort time limit, so you’d be justified in increasing the time limit.<\/p>\n

The quick way is a plugin that modifies the execution time configuration without having to actually access those files directly. For instance, you could use one of the many all-round plugins \u2013 such as Google PageSpeed Insights<\/a>\u00a0\u2013 where the max_execution_time<\/strong> value can be increased.<\/p>\n

You could also try a dedicated plugin like WP Maximum Execution Time Exceeded<\/a> that, once installed, edits the .htaccess file and sets the time limit to a whole 5 minutes by default. This is pretty generous, and any time you need to revert to your original limit, you just need to uninstall the plugin.<\/p>\n

For more customized time limits, talk to your WordPress agency for development and they will usually handle it for you, but if the hands-on method will need editing a few files in WordPress via (preferably Secure) FTP.<\/p>\n

\"\"<\/p>\n

Increase the Time Limit by Editing Files \u2013 wp-config.php<\/h2>\n

For this first way, we’ll edit wp-config.php. Once you’ve opened the WordPress root directory over FTP, locate the ‘public’ folder and open it to reveal the file in question. Open it for editing and insert this line of code:<\/p>\n

set_time_limit(240)<\/strong>;<\/p>\n

Preferably placing it at the end, right before it says ‘stop editing’, though the exact position isn’t an issue because the existing contents of the file are untouched. Save the file and reupload it if needed, and the time limit is now 4 minutes (or any other value you choose). Of course, ensure that the error has been dealt with.<\/p>\n

\"\"error fix<\/p>\n

 <\/p>\n

Increase the Time Limit by Editing Files \u2013 .htaccess<\/h2>\n

In the same ‘public’ folder, there’s .htaccess, especially if you’re using a shared host that runs on Apache. Backup the file, open it for editing, and insert this code:<\/p>\n

php_value max_execution_time 240<\/strong><\/p>\n

Use any other value you’d like, of course. Save and reupload .htaccess to the ‘public’ folder over FTP, and verify that the error no longer appears.<\/p>\n

\"\"<\/p>\n

Increase the Time Limit by Editing Files \u2013 php.ini<\/h2>\n

Next on our list is a less common file. If you find it in the ‘public’ folder, php.ini is another way we can increase the execution time available. On FTP, open the file and edit it by adding the code:<\/p>\n

max_execution_time = 240<\/strong><\/p>\n

Feel free to use any value, but once the file is saved and re-uploaded, do check that you’ve fixed the error.<\/p>\n

Increase the Time Limit by Talking to Your Host<\/h2>\n

On a dedicated server, all these methods will work great, but some shared hosts would want to protect their server, and may not even allow you to modify the execution time limit. In this case, contact your WordPress agency for development, or the hosting support directly, and inform them about the error you’re facing. Request the hosting provider<\/a> to increase the time limit to somewhere in the 1-to-5-minute range, and if they can, that ought to be the last you see of this error.<\/p>\n

\"\"<\/p>\n

Effortlessly resolved<\/h2>\n

Heavy PHP scripts in a WordPress element can bog your server down, and sometimes even trigger this error, causing you some trouble both in the backend and frontend. However, we hope that thanks to this tutorial, you now know it is hardly ‘fatal’<\/strong> and effortlessly resolved.<\/p>\n

We’ll see you next time, with more tutorials and tips from our team here at Vipe Studio.<\/p>\n","protected":false},"excerpt":{"rendered":"

And\u2026. We’re back, wrapping up this series on handling the […]<\/p>\n","protected":false},"author":1,"featured_media":23600,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[113],"tags":[601,1717,1737,1191,1757,108,1219],"class_list":["post-24484","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-website-wordpress-development","tag-error","tag-error-fix","tag-fatal-error","tag-fix","tag-max-execution-time-error","tag-plugin","tag-wordpress-error"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/posts\/24484","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/comments?post=24484"}],"version-history":[{"count":0,"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/posts\/24484\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/media\/23600"}],"wp:attachment":[{"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/media?parent=24484"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/categories?post=24484"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vipestudio.com\/en\/wp-json\/wp\/v2\/tags?post=24484"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}