Author Topic: Fatal error: Maximum execution time (Read 1368 times)

HanV · May 12, 2011, 09:37:07 am

I have made in Drupal a post to resolve this problem, because I think the error is in the way Drupal looks at the modules (i.e. CiviCRM).
But the problem appears (in my opinion) in modules with a great number of directories (in CiviCRM 939).

If you get this error, you can try my solution.
My solution is not to increase to max_execution_time or changing php.ini

see: http://drupal.org/node/1155336

apmg · May 18, 2011, 05:06:34 pm

If you're on shared hosting, your max execution time is being regulated. Ask you host provider to copy the php.ini file to your home directory and then open it up and change the max execution time there. You'll need to add SuPHP_ConfigPath /home/your-home-directory-here/ to the top of your .htaccess file.

When you do that, create a file called phptest.php and put "<?php phpinfo() ?>" in there by itself (without the "") and save it in your public directory. type yourdomain(.)/phptest.php and it will show you on the screen what php.ini file is being referenced

Good Luck.

HanV · June 03, 2011, 12:04:45 pm

I dont know if i am the only one with CiviCRM on Drupal who gets errors on the maximum execution time.
I know that it is possible to increase this time, but you have a solution also for shared hosting. My solution is not to increase the time, but to get a faster working system. (I think only for the admins.)

CiviCRM Community Forums (archive)

News:

Author Topic: Fatal error: Maximum execution time (Read 1368 times)

HanV

Fatal error: Maximum execution time

apmg

Re: Fatal error: Maximum execution time

HanV

Re: Fatal error: Maximum execution time