[TYPO3-dev] A ticking ticking timebomb with libxml update to 2.7.1?

Lee Perry leeperry at slack.de
Tue Aug 18 15:16:57 CEST 2009


Steffen Kamper schrieb:
>> you can fix it for new usages of a FCE - but please think about the 
>> existing FCEs without the CDATA - you have to fix every used FCE, 
>> because if you open this FCE (without CDATA in the flexform) the 
>> brackets will stripped and all tags will be wrong, even it is a 
>> bold-tag, a br-tag or a link-tag, and will looks like this example:
>>
>> "b Lorem ipsum/b dolor sit amet br/, consetetur sadipscing elitr, sed 
>> diam link 56 - internal-linknonumy!/link eirmod tempor invidunt"
>>
>> instead of:
>> "<b> Lorem ipsum</b> dolor sit amet <br/>, consetetur sadipscing 
>> elitr, sed diam <link 56 - internal-link>nonumy!</link> eirmod tempor 
>> invidunt"
>>
> did you ever tried it? This will be correct after the setting as it 
> forces CDATA! It's only less performant, so when ever libxml is updated 
> the setting should be removed.

Yes I tried it - and how can force it CDATA in flexforms, that are older 
  and without CDATA, because there were saved in the past without any 
forced CDATA.

When I fix such an used FCE, that means when I repair those stripped 
tags and save it now, than all is fine, because now with the CDATA 
forces, the CDATA will be inside the XML - BUT that is not my problem, 
the problem would be to update all these old used FCE, having no CDATA - 
there are many, many and more many of them <= that's the problem - 
that's the ticking timebomb ...




More information about the TYPO3-dev mailing list