[TYPO3-english] RC2: What is the csc-default frame for?

Peter Russ peter.russ at 4many.net
Fri Nov 27 16:32:01 CET 2009

--- Original Nachricht ---
Absender:   Tyler Kraft
Datum:       27.11.2009 11:13:
> Hi Peter,
> No offence but I think thats a bit naive of an expectation perhaps. 
> Every upgrade that I can think of (from 3.6 - > 3.7 -> 3.8 - etc -> to 
> 4.3) has involved slight changes and modification to how the rendering 
> is done - from 'cset default' and 'content' in 3.6 to csc in v 4.3.
> That's just the nature of the beast and tbh in my opinion they keep 
> evolving in ways for the good. Granted I wasn't happy about this wrap 
> around the html items either when it first happened (as we've been using 
>  4.3 beta for an upgrade for sometime now) as it involved having to go 
> and rewrite how it worked in one instance. But that was only the one 
> instance.
> Additionally there are notes as to what has changed in each instance so 
> the admin can gauge if it will cause a problem. As well you can set the 
> rendering mode to be a former version of csc if you want it to be.
> All in all I think this is fine personally.
> Just my 2cents
> T
> Peter Russ wrote:
>> --- Original Nachricht ---
>> Absender:   Philipp Holdener
>> Datum:       27.11.2009 07:48:
>>> Francois Suter schrieb:
>>>> Hi,
>>>>> For what is this default frame
>>>>> <div .. class="csc-default"...>
>>>>> ?
>>>>> I have a lot of HTML CE that are puting some html code together --> 
>>>>> this are wrapped with this default frame too. That makes my code 
>>>>> invalid :(
>> [...]
>>>> I know this change should have been advertised more openly, but we 
>>>> (Core devs) are doing our best. It *is* documented in the NEWS.txt 
>>>> file. Actually every TYPO3 admin should read this file when 
>>>> upgrading, because it is the one reference about all changes.
>>>> HTH
>>> Hello everybody
>>> Thanks for your feedback!
>>> I think its a good thing.. but NOT for HTML CE!
>> It might be a good thing when starting a site from scratch.
>> But IMHO upgrading an extisting installation should NEVER add 
>> something to content by default that changes the display by disturbing 
>> the design.
>> Peter.

Hi Tyler,

please read my post correctly as it says:

 >> But IMHO upgrading an extisting installation should NEVER add
 >> something to content by default

If a admin is asked to confirm a version switch this is fine with me. 
But I haven't had time to test upgrading existing site to version 4.3.


loans that change lives http://www.kiva.org

uon GbR

More information about the TYPO3-english mailing list