You may wonder: is it possible to have a website where PHP scripts take longer, yet they don’t cause any harm to the server? Some developers may opt for as much as a 300-second maximum, but anything over that isn’t a wise decision. However, you may need to increase the limit to 60 seconds, depending on your code and server response. In general, a 30-second time limit should work well for high-quality PHP scripts. This range gives your PHP scripts enough time to complete their jobs, even if they take some time to execute. Most hosting companies enforce a max execution time that’s anywhere between 30 and 60 seconds. What’s the Standard Maximum Execution Time Limit? Your hosting company usually sets this limit at the server level. Regardless of the cause, there aren’t many reasons to have a PHP script running for a significant amount of time therefore, a maximum execution time limit is in place. Furthermore, plugins come from all sorts of developers, so it’s harder to check out the good ones backed by solid code and frequent updates. Plugins seem to trigger this error message more often than other elements-likely because WordPress users install plugins more frequently than they modify code or install themes. It’s not uncommon for malicious attacks to utilize neverending PHP scripts to bring the site to a crawl.īesides, some plugins, themes, or other WordPress elements can strain server resources if they take too long to run. This limit looks at all the PHP scripts running on your site and blocks those running past the time limit.īecause WordPress site files mainly use PHP, it’s essential to keep an eye on PHP scripts to see if they run for too long and eat up too many server resources. Why Does the max_execution_time Error Happen?Įvery WordPress site has a maximum execution time limit for processing server requests.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |