[TYPO3-dev] Is there a serious bug in frontend rendering (CSSstyled content) in TYPO3 4.3-dev (revision 4741)?
Erik Svendsen
erik at linnearad.no
Sun Jan 18 18:21:04 CET 2009
Hello Franz,
> Hi,
>
>> I notice that the datawrap is changed from the old <a id="c26" /> to
>> be a part of the "innerWrap" (rendering). Can't find these changes in
>> the TypoScript for CSS Styled Content, so I presume it's somewhere in
>> the php code.
>>
> nope - it's pure typoscript - so easily adoptable. As the innerWrap is
> now a CASE/COA construct you have to adopt your TS if you intend to
> use the new approach. If you can live with the old one, just include
> the 4.2 compliant static template of CSC.
>
Thanks, I found the changes in CSC. They are easy enough to change when neccessary.
I don't find two different static templates of CSC.
>> I have tested also on another installation, with same result.
>>
>> If there are made changes which makes specific configuration of
>> tt_content.stdWrap.innerWrap not working, this will proabably break a
>> lot of TYPO3 installations.
>>
>> But maybe I have missed a point.
>>
> It'll only break if you use the CSC-rendering definition for 4.3, but
> you're free to use the static template of 4.2 branch (which is
> provided in addition to the new rendering behavior). So it won't break
> anything if updated with the update wizard of Typo3.
>
But there wasn't anything in the upgrade process (yes I have used the upgrade
wizard) which gave me any clue about the change as far as I remember. Which
should be clearly stated, because of the consequences of the change. In both
cases I did a upgrade through the Upgrade Wizard. And the upgrade gave the
rendering of 4.3 behavior. If I don't upgrade the compat_version, then nothing
is going to be broken.
Also nothing new in the TypoScript Object browser, before I set conditions
to 4.3.0. Look like the opposite of what you are writing.
I suppose CSS Styled Content still has to be included as static from extension.
But I suppose to get the old version to work I have to reset compat_version
to 4.2 (tested amd correct).
So I feel there are missing part of this change, which look to me as a real
change to someting better.
1. In Update Wizard it has to be stated very clear that an upgrade to compat_version
will break any use of tt_content.stdWrap.innerWrap.cObject. Because as it
is today an straight upgrade will break the rendering.
2. The solution is either to not do the upgrade of compat_version, or set
it back under all configuration to 4.2 or adapt the new TypoScript. Which
probably are the best solution, but a lot of people will find a bit more
complicated.
Maybe I have misunderstood everything, but thats the way it looks like i
works from my side.
WBR,
Erik Svendsen
www.linnearad.no
More information about the TYPO3-dev
mailing list