Hi again,
Does anyone have hint what might be the cause of such symptom? In which direction should I dig?
Error gone. It was due to some custom script not yet adapted to 6.2 and kicking in very early in the bootstrap process. However I must say that this error message in absolutely not helpful. I haven't looked at the corresponding place in the source code, but I wonder if there's any way such an exception could be caught at some place where a more helpful error message could be issued (in this case, what class was it trying to cache).
Cheers -- Francois Suter Work: Cobweb Development Sarl - http://www.cobweb.ch TYPO3: Help the project! - http://typo3.org/contribute/ Appreciate my work? Support me - http://www.monpetitcoin.com/en/francois/support-me/ _______________________________________________ TYPO3-english mailing list [email protected] http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
