It takes more than a minute to display !!!

Next topic

Author	Message
max imil	Thursday 10 July 2003 9:02:14 pm Hi to the EZ Crew. I'm looking foward to install the 'ezpublish-3.1-1.tar.gz' on my web server, but I wanted to try it before on my local machine. here's my config : win98 apache 1.3.24 php 4.1.2 mysql 3.23.49. I won't be able to change anything in the php.ini and Apache conf file on my web server. I've installed it on my localhost and it works all the way until the login screen. 30 seconds wasn't enough in php.ini so i had to change that for 300 (but again, i won't be able to change that on the remote host). After that, i can log in but it takes, at least 1 minute to display a page, and so on for each page. It's a bit annoying and I can't see how I can work with that !! I would really appreciate help on this issue. Thanks Maximil
Karsten Jennissen	Friday 11 July 2003 12:26:50 am That's definitely not "normal". What's your CPU / Memory? You didn't use the installer, right? Sounds to me like some kind of cache problem. Could you see what you find in /var/cache? The reason ez publish requires such a long time the first time it is called is because it builds the translation and puts it into the cache, much like an initialisation of the system. After that it should go much much quicker. Karsten
max imil	Saturday 12 July 2003 9:06:46 am CPU is 666Mhz intel RAM is 128Mb No, I didn't use the installer in the localhost/ezpub.../var/cache/... is present a lot of files with a lot of numbers and some directories (codepages, content, ini ...) I wasn't able to configure by myself the Virtual host options. Would it cause any probs ???
Jaroslav Satkevic	Wednesday 24 September 2003 5:22:38 am i am have same problem. When I install ez3.2 ( with installer ) in my redhat 9 i see message: Fatal error: Maximum execution time of 30 seconds exceeded in /opt/ezpublish/sites/default/lib/ezdb/classes/ezdbinterface.php on line 203 Fatal error: eZ publish did not finish it's request The execution of eZ publish was abruptly ended, the debug output is present below.