|
Author
|
Message
|
|
zackwlg zackwlg
|
Monday 12 May 2003 5:37:03 am
hi,
after the installation step "Registration" i have got the following error message:
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 39 bytes) in /mnt/ls1/06/966/00000004/htdocs/ezpublish/lib/ezi18n/classes/ezutf8codec.php on line 106
Fatal error: eZ publish did not finish it's request The execution of eZ publish was abruptly ended, the debug output is present below. who can help?
bye
zackwlg
|
|
Tony Wood
|
Monday 12 May 2003 6:00:58 am
Try increasing the amount of memory needed by PHP in the php.ini file... This is normally set to 18M for most setups.
Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development
Power to the Editor!
Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future
|
|
zackwlg zackwlg
|
Monday 12 May 2003 6:13:24 am
i have a web package by the webhoster strato (germany) and no access to this file.
|
|
Tony Wood
|
Monday 12 May 2003 6:16:51 am
Arh.... I don't know then... Sorry.
Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development
Power to the Editor!
Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future
|
|
Karsten Jennissen
|
Monday 12 May 2003 6:17:19 am
You could ask Strato, whether a) you can override via .htaccess or whether they can do this for your virtual account.
See here:
http://ez.no/developer/ez_publish_3/documentation/ez_publish_3/typical_problems_and_solutions/not_enough_php_memory Hope there is a solution for you. This large amount of memory is only needed a few times I think as certain cache files are generated. Karsten
|
|
zackwlg zackwlg
|
Monday 12 May 2003 6:37:59 am
thanks for the suggestion but strato said no. i am looking for a another webhoster. thanks. zackwlg
|
|
steve oshea
|
Saturday 24 May 2003 9:19:59 pm
I also get this message, why should i increase the memory size when every other portal/cms works fine! This appears to be either a programming error or bad design!! which is it?
|
|
Karsten Jennissen
|
Sunday 25 May 2003 2:59:08 am
Try this one:
http://ez.no/developer/ez_publish_3/contributions/30_second_timeout_remedy Maybe it'll help.
|
|
Stephen Trembath
|
Tuesday 24 June 2003 5:14:49 pm
There's one very poor workaround to this problem, if you can't access php.ini, but simply want to get a look at how your ezPublish site looks. Keep refreshing the page a few times (you have to do it less as you move through the site, as it seems the classes are loaded) and eventually each page will load. This certainly isn't a permanent solution though! It would be great if the developers could address this issue. I imagine a lot of people with web hosting would have this problem, and many hosting providers are unlikely to agree to the change in PHP memory.
|
