shouldn't that be changed in your php.ini?
Bear
On 1/1/2015 17:18, Sergio Manzi wrote:

Lately I was unable to use com_patchtester (code from 'master') as I
was getting errors of max execution time (30 seconds) exceeded.

I don't know if this is the CORRECT solution, but with this I solved
my problems...

---

    You can merge this Pull Request by running

git pull https://github.com/smz/patchtester FixMaxExecutionTime

Or view, comment on, or merge it at:

#59

    Commit Summary

• Increase PHP max execution time to 5 minute

  File Changes
  

• M administrator/components/com_patchtester/patchtester.php
  https://github.com/joomla-extensions/patchtester/pull/59/files#diff-0
  (3)

  Patch Links:
  

• https://github.com/joomla-extensions/patchtester/pull/59.patch

• https://github.com/joomla-extensions/patchtester/pull/59.diff

—
Reply to this email directly or view it on GitHub
#59.

No virus found in this message.
Checked by AVG - www.avg.com http://www.avg.com
Version: 2015.0.5577 / Virus Database: 4257/8849 - Release Date: 01/01/15

shouldn't that be changed in your php.ini?

It's a possibility, but that would act globally, while this is the only place where this is needed at the moment.

Beside that, I think there are cases (not mine) where you are not allowed to modify that php.ini option (shared hosting). I'm unsure if my patch would work in those cases, anyway...

Now that there is batch stepping in here, we shouldn't need to bump the execution time unless you're trying to use the component on a host where their configs are just garbage. If it's still an issue, maybe we can revisit later, but for now I'm going to close this.