My form's templates perform {{#set}} on behalf of a page. But when the
page is transcluded, those {{#set}} commands are being executed on
behalf of the transcluding page -- clearly in error. I tried having
the form's templates output a <noinclude> and <includeonly>
elements, but that doesn't do the trick (duh). Then I tried manually
inserting the <noinclude> element via Edit Source, but when the page
is then edited by form, SF repositions the template calls outside of
the <noinclude> element that I inserted.
So I'm wondering if there needs to be an ability to identify when &
where <noinclude> & <includeonly> are to be inserted into a page
managed by SF. My two suggestions are to (a) add a wrap=elementname
parameter to the free text field which encapsulates (default) content
in an <elementname> element (b) create a special syntax, e.g., >
%elementname%< and >/elementname< and >elementname/<, to indicate a
begin, end, or empty tag to be inserted into the output.
Previous discussion about this issue (Subject: Trying to put
<noinclude>{{Books}}</noinclude> in an auto-created page) talked about
a workaround that's undesriable as a permanent solution -- I'll bet
there are better choices. I am heartened by Yoren's view (@Tue, 7 Oct
2008 23:41:51 -0400) that "it might make sense for SF to directly
handle <noinclude> tags".
Thanks - John
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Semantic Forms" 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/semantic-forms?hl=en
-~----------~----~----~----~------~----~------~--~---
