TYPO3 Core

Hallo Markus,

thanks for your feedback.
As I upgraded my site from TYPO3 6.2.6 to 6.2.9 the error occurred. I tried it using lower versions and the same error occurred in 6.2.8. Then TYPO3 6.2.7 was OK so I opened the bug report.

Now I checked again the situation and what can I conclude? - The error disappeared!
Perhaps there was an issue caused by not cleaned caches or so.

Please apologize this breakdown - you may close this issue.

Regards and a healthy start into the new year
Thomas

I got this issue as well. The reason for this was, that some symlinks either pointed to the old core or were cached somehow. Maybe indicates that the update procedure in the install tool can be improved?

Of course I flushed all caches and even removed typo3temp.

After renaming the old core (and re-creating the symlink manually), this error occured:
Fatal error: require_once(): Failed opening required '/var/www/html/typo3_src-6.2.6/typo3/sysext/core/Classes/Compatibility/LoadedExtensionsArray.php' (include_path='/var/www/html/typo3/contrib/pear/:.:/usr/share/php:/usr/share/pear') in /var/www/html/typo3_src-6.2.9/typo3/sysext/core/Classes/Core/ClassLoader.php on line 184

I don't understand yet why there can be a reference to 6.2.6 within 6.2.9...

UPDATE: A restart of the server solved the problem. Still no idea how paths and/or symlinks can get cached. Or how to prevent this error at updating without rebooting.

@Kappe: The restart of the server empties the PHP opcode cache. "All you need to do" is to empty this very cache.
Problem though: Might not be possible via CLI on some systems, as those use different contexts/configs for Web and CLI.

This problem only occurs if you switch the symlink manually. If the Install Tool takes care of the update, it will truncate the cache properly.
If you're lucky, you might be able to access the Install Tool after the manual update and click the Clear Caches button there, which will kill the opcode cache too.

Unfortunately this is a problem we can't do very much against in the TYPO3 area.

In fact I did the update using the install tool. And afterwards I cleared all possible caches (in the install tool, also removed typo3temp), and that did not resolve the problem.

So maybe there is a faulty server configuration. Thus I agree this is no TYPO3 topic.

At most patchlevel updates the problem will not produce error messages, just from below 6.2.8 to 6.2.8 or above (because checkPageForMountpointRedirect was added). Maybe the consequences will be more subtile (e.g. security hole not patched). To make sure to use the right core, rename the old core directory and reload.

At least I hope my experience can help others to recognise the cause for their error messages.

Seems like there's still some cache somewhere that keeps the old files at your server.
Maybe you wanna join TUGA on 3rd Feb 2015, so we can talk on that in person? (http://www.meetup.com/TUGA-TYPO3-User-Group-Austria/)