![]() |
Cannot set max execution time limit due to system policy [was CI 2.x!?] - Printable Version +- CodeIgniter Forums (https://forum.codeigniter.com) +-- Forum: Using CodeIgniter (https://forum.codeigniter.com/forumdisplay.php?fid=5) +--- Forum: General Help (https://forum.codeigniter.com/forumdisplay.php?fid=24) +--- Thread: Cannot set max execution time limit due to system policy [was CI 2.x!?] (/showthread.php?tid=69050) |
Cannot set max execution time limit due to system policy [was CI 2.x!?] - nazomaniaque - 10-01-2017 Hello, first sorry for my bad English... ![]() Then ! I worked today without internet, so i made some changes on a few controllers and models. When i uploaded these files, i got a blank page. So i tried to find where was the bug, but ... did not found ! I looked in my logs, and got this : ERROR - 2017-10-01 23:44:48 --> Severity: Warning --> set_time_limit(): Cannot set max execution time limit due to system policy I tried to search on Google but ... Nothing. ![]() So you're my last hope ! Can someone help me ? Thank you ! RE: Cannot set max execution time limit due to system policy [was CI 2.x!?] - rtenny - 10-02-2017 Try removing the line with set_time_limit() or comment it out. I dont think that CI will set a time limit so I presume its something you added. But with out a bit of code from you its impossible to say. RE: Cannot set max execution time limit due to system policy [was CI 2.x!?] - superior - 10-03-2017 Looks to me like you don't have any permission to change the settings for "set_time_limit()". This should be a PHP setting "php.ini" the function is i guess disabled to be used. Is this on a local machine or Shared Hosting or own server (VPS, Dedicated)? RE: Cannot set max execution time limit due to system policy [was CI 2.x!?] - nazomaniaque - 10-03-2017 I do not use set_time_limit()... That's why I don't understand why i got this error. I know on which file the bug is. Fortunately, I found an old save of this file, so I uploaded it back and my website is working. I'll check the file and try to find where the bug is to tell you. It's on a shared hosting. |