Fatal error: Allowed memory size of 8388608... - community.ez.no

Wednesday 17 September 2003 6:17:59 am - 5 replies

Modified on Wednesday 17 September 2003 6:18:49 am by James Packham

5 replies

Author	Message
Karsten Jennissen	Wednesday 17 September 2003 6:52:30 am Check here: http://ez.no/developer/ez_publish_3/documentation/installation_and_configuration/troubleshooting/not_enough_php_memory Regards, Karsten
James Packham	Wednesday 17 September 2003 7:18:49 am Thanks, but I'd already tried this (I should have mentioned it really). It seems that even when I put the max allowed memory up I still get the error (I tried all the way up to 50M). I've had something like this before (on PHP Nuke), but can't remember for the life of me how I fixed it! Anyone had this problem before? It's kind of annoying because I had the beta version of 3.2 working of sorts until this morning, when I tried to replace it with this one... ~James~
Paul Borgermans	Wednesday 17 September 2003 7:40:04 am OK, brute force method: 1) clear the entire var/cache by hand 2) clear any php accelerator files (probably in /tmp); this you should always do after a release upgrade. If that does not work, 3) put phpinfo(); at the top of index.php and find the line which says which php.ini file it is using. If you used the installers, there may be a problem that the php.ini file is not the right one or it cannot find it. So your max memory settings are ignored. hth -paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
Tony Wood	Wednesday 17 September 2003 7:57:09 am I know this is a stupid question, but what settings did you change in the php.ini file and did you restart httpd afterwards? service httpd restart? Tony 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
James Packham	Wednesday 17 September 2003 8:09:29 am AH HA! It was because I didn't clear the cache, it seems to be working fine now. Sorry if I wasted your time! Cheers, ~James~

You must be logged in to post messages in this topic!

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.