[TYPO3-mvc] Empty/faulty extension output after migrating to productive system (because of faulty fluid naming settings?)
Franz Koch
typo3.RemoveForMessage at elements-net.de
Tue Nov 30 12:42:09 CET 2010
Hey Bastian,
> Please be aware of the fact, that Extbase 1.3 won't be compatible with
> TYPO3 < 4.5 as it relies on features that have been added lately (e.g.
> FE support for the t3lib_FlashMessageQueue)
I didn't follow the changes done in extbase to implement that, but can't
we wrap it in a compatibility layer, or would it be to complex?
--
kind regards,
Franz Koch
More information about the TYPO3-project-typo3v4mvc
mailing list