Friday 19 August 2011 1:49:47 pm

You should look at the php error log and eZ Publish error log to get some information...

Indeed.

Welcome to the eZ Community Ahmed.

One common pitfall is a too short max_execution_time value in the PHP configuration. Set it to 120 for eZ Publish, or even 180 to be on the super safe side.

Let us know how things go,
Cheers, 

--
Nicolas Pastorino
Director Community - eZ
Member of the Community Project Board

eZ Publish Community on twitter: http://twitter.com/ezcommunity

t : http://twitter.com/jeanvoye
G+ : http://plus.tl/jeanvoye

Monday 22 August 2011 12:47:24 am

You should look at the php error log and eZ Publish error log to get some information...

Indeed.

Welcome to the eZ Community Ahmed.

One common pitfall is a too short max_execution_time value in the PHP configuration. Set it to 120 for eZ Publish, or even 180 to be on the super safe side.

Let us know how things go,
Cheers, 

Hi Nicolas Pastorino

How are you?

I hope to bee fine

Really i feel there are interesting with my post i percolated your efforts and thank you very much

For your Suggestion Nicolas Pastorino (max_execution_time=180), i did that but the error still found

If you have any other suggestion don/t hesitate to conatct me

thax

Monday 22 August 2011 7:54:51 am

The error log you showed says that the ini files you have on the webserver have a creation date set in the future (according to the webserver). This poses a serious problem to eZ Publish caching mechanism.

What is probably happening is that

- either you have installed ezpublish on the server then changed the server clock to a past value

- or you are using an ftp client to upload ezpublish files that sets modification date on the server of the uploaded files to the same modification date they had on the client - and the client clock is in the future compared to the server

In any case, you should always have clocks set to proper time, in both servers and development machines. Please set up the sntp service on unix or windows time service to achieve this.

You can then use the touch command to change modification timestamp of ezpublish files on the server

ps: if on windows, it is also a good idea to prevent any antivirus to scan the ezpublish folders. This does generally make eZ very slow, as a lot of cache files are created by the system, and I would not exclude that it could have an impact in extreme cases on timestamp mismatch...

Principal Consultant International Business
Member of the Community Project Board