[TYPO3-english] Problem with colPos related definitions

Loek Hilgersom hilgersom at xs4all.nl
Fri Nov 28 13:57:24 CET 2008


Hi Tapio,

tt_content.image.20 used to be a USER objecct, but you've changed it into a CASE 
object. The tt_content.textpic object is build upon this image.20, so you'll 
have to change that definition too.

I've made a quick and dirty fix that works, but I'm sure more elegant solution 
is possible. Add this below your typoscript:

tt_content.textpic.20 =< tt_content.image.20
tt_content.textpic.20 {
   default {
     text.10 = COA
     text.10 {
       if.value = 24
       if.isGreaterThan.field = imageorient
       10 = < lib.stdheader
       10.stdWrap.dataWrap = <div class="csc-textpicHeader 
csc-textpicHeader-{field:imageorient}">|</div>
     }
     text.20 = < tt_content.text.20
     text.wrap = <div class="csc-textpic-text"> | </div>
   }
   0 < .default
   3 < .default
   23 < .3
}

Cheers,
Loek


Tapio Markula wrote:
> Hi
> 
> Sorry, that I create a new topic, which relates with an old issue but I 
> regarded better to create a new.
> 
> I have this TS config:
> 
> temp.customRenderImage = CASE
> temp.customRenderImage {
>   key.field = colPos
>   default < tt_content.image.20
>   0 < tt_content.image.20
>   0.maxW = {$styles.content.imgtext.maxWNormal}
>   0.maxWInText = {$styles.content.imgtext.maxWInTextNormal}
>   3 < tt_content.image.20
>   3.maxW = {$styles.content.imgtext.maxWBorder}
>   3.maxWInText = {$styles.content.imgtext.maxWInTextBorder}
>   23 < 3
> }
> tt_content.image.20 < temp.customRenderImage
> 
> That works as expected if the content type is 'image' and it doesn't 
> have any side effect, if the content type is 'text'
> 
> The problem is that using text with images content type,
> the content from the 'bodytext' field would not be rendered at all.
> What I should do another way in order to avoid the nasty side-effect of 
> this defintion.


More information about the TYPO3-english mailing list