I have a similar problem with the top zone where the resulting code is not
valid XHTML.
With 3.3.
In my top zone I have on *1* line with no line breaks:
[(pagecount)][[main|[^tnetwiki-header.gif alt='Some Alt Desc' title='Some
Title'^]]][if ! set {?myid}]<(persist)>[if]$$actions
The code generated is...
<div id='top'>*<p>*<a href="http://somewebsite/main"; ><img src='
http://somesite/home/files/tnetwiki-header.gif' alt='Some Alt desc'
title='Some Title' width="401" height="53" /></a><div class='actions' >
</div>*</p>*
</div>
Validator is not logged in, so none of the actions show up as I have them
all hidden when the user is not logged in.
While I can make the spacing in the <p>'s disappear in CSS, I can't make
them themselves disappear which is resulting in XHTML validation errors that
I can't seem to prevent. Since this is the top zone of basically every
page, all pages won't validate.
If I take out the page link, the <p>'s disappear but so does the clickable
link in the title.
[(pagecount)][^tnetwiki-header.gif alt='Some Alt Desc' title='Some
Title'^][if ! set {?myid}]<(persist)>[if]$$actions
So it is related to the link code which insists on placing a <p> in there.
Then I run into the exactly same problem in the side zone... I have buttons
created using <div>'s. The system adds <p>'s which makes it no longer valid
XHTML
I thought of perhaps an option to say don't do that in a specific zone but I
suspect the output in even the body using that would be invalid.
On Wed, Nov 25, 2009 at 6:06 AM, The Editor <[email protected]> wrote:
> On Tue, Nov 24, 2009 at 2:09 PM, Markus <[email protected]>
> wrote:
> >
> > The goal should be that no if-hacks are needed like this one:
> >
> > [if whatever]...[if][if whatelse]
> > here I need the line break but not that huge white space (see above)
> > when whatelse is false[if]
>
> It looks like you are getting exactly what is expected. If you put the
> line return outside the [if whatever] [if] then it will appear whether
> the condition is passed or not. If you want the line return to only
> appear when the condition is met, you need to put it inside the
> conditional. It is simply a question of seeing the actual line return.
> In your example it is **after** the closing [if].
>
> Though this issue has come up before, I think it is much more a hack,
> and even counter-intuitive to extend the conditional to a line break
> that follows or precedes the if wrappers. In other words, the if
> statement's are behaving very literally, and in my view doing exactly
> what they should be doing.
>
> Cheers,
> Dan
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "BoltWire" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<boltwire%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/boltwire?hl=en.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en.
