da Blocks

[Jensensen]

x

[update]

Yeah man, this exactly was what I tried to explain by using the expression "nested"!

I know that you know that I know

[update]

WOW - this is so cool: http://code.google.com/p/phpwcms/source/detail?r=253
.... just two minutes ago - can't believe it, really. Many thanks, Oliver - will go playing with it as soon as Günther has his new r edition up !!

[Jensensen]

Thank you claus for PM!
[x]

[update]

Hmm, let''s see WHO made/was responsible for issue 85...

Dig it!

(ich sach ja: "Hier wirste bekloppt bei")

[Jensensen]

... Hmm, let''s see WHO made/was responsible for issue 85...

ALTER SCHWEDE!
No mystery anymore --> claus [... and slackero fulfilled ]

[juergen]

Ok claus, we are waiting for Nesters ...

[update]

This is not as easy as expected (hope is a strange animal )
If I have an HTML Content Part template with - let's say- 3 CUSTOM_BLOCKS {B1}{B2}{B3} I'm able to target them as usual.
But putting another CP HTML template into e.g. {B2} with two new CBs {D1}{D2} they will be rendered as plain text only (still bold or other ones are rendered fine)
One rendering step, then finito...

So I tried to put in some CBs into the text area of different CPs and nested the - this seems to work as expected and nesting woks out, but is really unhandy
So why isn't it rendered - is there a difference between template and text field input rendering? Especially for the CP HTML it would come in handy to be able to render at least 2 or three steps while nesting ...

[Oliver Georgi]

You cannot nest replacement tags in looped manner. It will be rendered only once!!! You have a logical problem. Think twice what you really expect. You are now at an point where it is in-effective to handle it this way without custom frontend_render scripting.

Oliver

[Jensensen]

[x]

[update]

I'm wondering because
claus wrote:... putting another CP HTML template into e.g. {B2} with two new CBs {D1}{D2} they will be rendered ...
perfect!

No - not so!

they will be rendered as plain text only

showing their beauty as {CUSTOM1} ... not showing the contend that is meant to be in them....
My hope has been that this would be posible with templates too, but mmm...
... perhaps some FE-rendering script could do the trich.... I will draw some picture later on....

EXAMPLE: CP HTML
target: --> {B1}
content: --> {D1}{NAV_LIST_UL}{D2}

I'd like to have this in a template - so users don't need to fill in some {}

[Jensensen]

x

[Jensensen]

x

[update]

Here is a little nesting test. See how it is stopping render work.

[Jensensen]

x