Friday 06 June 2008 6:13:46 am

What a coincidence... I was just about to write about this as we're struggling with it right now! Same thing, same impossibility to reproduce, and seems related to one of extensions with an abstract datatype class. This also happens only at one location with Debian-based server, when moved elsewhere it doesn't happen...

One thing. In our case, this eZFile error mentions the very last line of a class that implements the abstract class:

class ClassName extends OurAbstractDatatype {
...
} <---- This line is mentioned in the error message...
?>

Maybe that would be a hint of some sort...

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

Monday 09 June 2008 2:38:21 am

After further testing, the problem seems to be related to the server configuration (in this case Debian) which is causing the following strange behaviour: from time to time, the server is catching a STRICT php error as a fatal error. In order to fix the problem, I have updated the code of my extensions in order to get rid of all the STRICT errors and until now, I did not get any more these fatal errors.

About the error on the closing brackets '}', it is about the definition of the class which does not match the parent class. You have to go to each of the methods declarations and update them to match the parent declarations (which are slightly different in v4 - from what they were in v3).

Hope this might help.

Hakim

Monday 09 June 2008 11:48:01 pm

Hi Piotrek,

By any chance, do you know if they were any kind of maintenance on your Debian server (update code or config of PHP, Apache...)?

Hakim

Tuesday 19 August 2008 10:12:00 pm

I also had a "Class 'eZFile' not found in" error a month ago or so.
If I don't remember incorrectly the problem was that I was missing a } in the end of a file in one of my custom extension:

I had code like

<?php
class vtest
{
	function foobar()
	{

	}

// no } at the end here
?>

In the first post in this thread I see you got a "Fatal error: Class declarations may not be nested in". This could indicate that you have the same problem.

Tuesday 19 August 2008 11:22:37 pm

Hi Piotrek.
Sorry, I don't have all the answers. I just wanted to inform you about my problem and my solution as it sounded related to your problem.
It is weird if it only happens from time-to-time, indeed.

However, I would recommend to everybody which experience this problem to double check that they have no such syntax errors as I mentioned above in their files.

If it only happens from time-to-time, maybe some generated code in some cache file lacks a ending "}" ?

Wednesday 17 June 2009 4:13:39 am

Just experienced this myself, and it does seems like a cache file is causing the problem. Clearing the cache will make the problem go away (for a while anyways).

Senior Software Engineer - Vision with Technology

http://www.visionwt.com
http://www.omh.cc
http://www.twitter.com/omh

eZ Certified Developer
http://ez.no/certification/verify/358441
http://ez.no/certification/verify/272578

Thursday 27 August 2009 2:03:06 am

I have also experienced class not found messages during the last weeks (with eZPage and eZPageZone). Once the problem occur, I have to restart apache in order to make the problem go away.
I kinda suspect it to be an APC problem but just clearing the APC cache ( using apc_clear_cache() ) doesn't help. Apache has to be restarted