Max execution time error ... but cannot edit my php.ini file

Next topic

Author	Message
David Barker	Wednesday 30 August 2006 10:32:22 am Hey there, Well I used to use eZ a couple of years ago and thought I'd try it out again! I'm pretty sure I used it on the same hosts as I am now, but I'm having the maximum execution time of 30 seconds error when I go to access admin: Fatal error: Maximum execution time of 30 seconds exceeded in /pub/home/dbarker5/htdocs/bored/lib/ezfile/classes/ezdir.php on line 503 Fatal error: eZ publish did not finish its request The execution of eZ publish was abruptly ended, the debug output is present below. I can get on the main site itself fine, but it's logging into admin that gives me the error. Now from what I've read, the solution is to edit the php.ini file on the server. I've contacted my host but they refuse to edit it (as I'm on shared hosting). Basically, I'm just wondering if there is any way of getting around this problem without having to edit php.ini? Is it possible to do what it's trying to do in smaller steps or something? I'd love to get this working! Thanks in advance, Dave
Claudia Kosny	Wednesday 30 August 2006 11:36:42 am Hello David Try to add the following in your .htaccess file: php_value max_execution_time 30000 (the number is the number of seconds). If that does not work either (some hoster forbid this as well), try to add the following to the index.php: ini_set ('max-execution_time', '30000' ) Be sure to add this after the line ob_start() as otherwise you might get problems with sent headers. Apart from that - if you try to access the admin part of a site with lots of nodes, the problem might be caused by the menu on the lefthand side. Depending on the settings in contentstructuremenu.ini.append.php EZ might try to fetch all nodes on the site. So change the settings there if necessary. Infos about this here: http://ez.no/doc/ez_publish/technical_manual/3_8/reference/configuration_files/contentstructuremenu_ini Greetings from Luxembourg Claudia
David Barker	Wednesday 30 August 2006 12:09:58 pm I don't know how to thank you!!!! But thanks!!! haha. I tried the first suggestion and it worked :-D Like I say... thank you so much :) Dave

Author

Message

Wednesday 30 August 2006 10:32:22 am

Hey there,
Well I used to use eZ a couple of years ago and thought I'd try it out again! I'm pretty sure I used it on the same hosts as I am now, but I'm having the maximum execution time of 30 seconds error when I go to access admin:

Fatal error: Maximum execution time of 30 seconds exceeded in /pub/home/dbarker5/htdocs/bored/lib/ezfile/classes/ezdir.php on line 503
Fatal error: eZ publish did not finish its request

The execution of eZ publish was abruptly ended, the debug output is present below.

I can get on the main site itself fine, but it's logging into admin that gives me the error.

Now from what I've read, the solution is to edit the php.ini file on the server. I've contacted my host but they refuse to edit it (as I'm on shared hosting). Basically, I'm just wondering if there is any way of getting around this problem without having to edit php.ini? Is it possible to do what it's trying to do in smaller steps or something? I'd love to get this working!

Thanks in advance,

Dave

Claudia Kosny

Wednesday 30 August 2006 11:36:42 am

Hello David

Try to add the following in your .htaccess file:
php_value max_execution_time 30000

(the number is the number of seconds).

If that does not work either (some hoster forbid this as well), try to add the following to the index.php:
ini_set ('max-execution_time', '30000' )

Be sure to add this after the line ob_start() as otherwise you might get problems with sent headers.

Apart from that - if you try to access the admin part of a site with lots of nodes, the problem might be caused by the menu on the lefthand side. Depending on the settings in contentstructuremenu.ini.append.php EZ might try to fetch all nodes on the site. So change the settings there if necessary. Infos about this here:
http://ez.no/doc/ez_publish/technical_manual/3_8/reference/configuration_files/contentstructuremenu_ini

Greetings from Luxembourg

Claudia

David Barker

Wednesday 30 August 2006 12:09:58 pm

I don't know how to thank you!!!! But thanks!!! haha. I tried the first suggestion and it worked :-D

Like I say... thank you so much :)

Dave

eZ debug

Timing:	Jan 31 2025 04:32:17
Script start
Timing:	Jan 31 2025 04:32:17
Module start 'layout'
Timing:	Jan 31 2025 04:32:17
Module start 'content'
Timing:	Jan 31 2025 04:32:17
Module end 'content'
Timing:	Jan 31 2025 04:32:17
Script end

Main resources:

Total runtime	0.0199 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0077	588.4297	151.2422
Module start 'layout'	0.0077	0.0024	739.6719	36.6953
Module start 'content'	0.0101	0.0082	776.3672	90.2656
Module end 'content'	0.0183	0.0015	866.6328	33.9922
Script end	0.0198		900.6250

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0028	13.9291	14	0.0002
Check MTime	0.0011	5.7800	14	0.0001
Mysql Total
Database connection	0.0013	6.5270	1	0.0013
Mysqli_queries	0.0025	12.3849	3	0.0008
Looping result	0.0000	0.0599	1	0.0000
Template Total	0.0011	5.5	1	0.0011
Template load	0.0008	4.0991	1	0.0008
Template processing	0.0003	1.3476	1	0.0003
Override
Cache load	0.0006	2.8966	1	0.0006
General
dbfile	0.0003	1.4279	8	0.0000
String conversion	0.0000	0.0288	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs