[Typo3-dev] custom CTypes have header in 3.6.1; didn't in 3.6.0RC1

[Michael Johnston]

sorry. I assumed since it was a difference between two minor versions 
it could very well be a development issue.

What I would prefer is a way IN CODE to tell typo3 that my php script 
is solely responsible for producing the output of the CType I am 
defining. Having the output depend on typoscript of which there is no 
trace or inkling in the actual code responsible for defining the 
element just goes against the grain for me. With good reason, since it 
results in things like a minor version upgrade making a whole site 
completely fubarred!

Of course, it would have been wonderful if we'd had template voila when 
we started, it would render a lot of issues moot. Oh well, we started 
just a little too soon.

Cheers,
Michael

On 28-Jun-04, at 4:59 PM, Wolfgang Klinger wrote:

>
>  *hiya!*
>
>  On Mon, 28 Jun 2004, Michael Johnston wrote the following:
>> The first major problem is that now all our custom content elements
>> have an extra header:
>>
>> <!--  Header: [begin] -->
>> 	<div class="csc-header csc-header-n1"><h1
>> class="csc-firstHeader">Willkommen bei RBM</h1></div>
>> <!--  Header: [end] -->
>>
>> We would like to draw our own headers. Actually, after grepping in the
>> code, although the comment & div are new, I'm not sure why I DIDNT get
>> an h tag on all my custom elements before.
>
>  At first your question has nothing to do with Typo3 development,
>  so your are asking the wrong guys...
>  (next time ask in the general english list)
>
>  Anyway.. the comments come with a new version of css_styled_content 
> and you
>  may disable them with e.g.
> -----
> lib.stdheader.stdWrap.prefixComment =
> -----
>  And if you have your own header definition (TS) you'll have to set 
> this
>  as default (as usual)(?)
>
>
>  bye
>  Wolfgang
>
>
>
> _______________________________________________
> Typo3-dev mailing list
> Typo3-dev at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev