TYPO3 Core

Hey.

I'm pretty sure this has always been the case: The fluid parser tokenizes everything, including inner content of f:comment and throws exceptions if that fails. I'm unsure on why this pops up only after upgrade in your project, though. The only way around that is a cdata section to my knowledge, the VH has an according example in the class header section.

I worked on the fluid parser some weeks ago and stumbled upon this as well. It is however probably not easy to solve to make fluid not parse f:comment body at all.

In any case, this issue should be raised within fluid standalone at https://github.com/TYPO3/Fluid - this is a thing of the standalone library, not of typo3 core fluid.

As such, we'll not follow this issue further here at forge, but within the fluid standalone issue tracker. Please feel free to raise an issue over there, maybe someone could come up with an according patch within the regex based parser of fluid standalone.