For instance if a field value contains something like
it won't render and will show as =my value=.
Same with [], InterWiki
links, Wikiwords and probably most %VAR%.
This was done by purpose to suppress autolinking of form values.
See the file
Form definitions may be imported from another web and WikiWords
used in these forms are only valid in that other web.
For example, let's have a form definition in
that defines a formfield
The values for this formfield are defined in a table in
. Each value in this
table is a WikiWord
etc. Now, if I use this form in a
web, all above WikiWords
try to autolink in the current web. And fail.
FindElsewherePlugin is no option as this would clutter the namespace for WikiWords
even more, i.e. when using more applications.
should be allowed to link to the correct place in the
the currently must be of the form
But this sucks in formfields of type
now as you get this full qualified WikiWord
(FQWW) where I only
want to offer the tail of it in the selection. Squared brackets link
don't display as expected during edit either. Last not least I want to store the data
in the form.
Out of the box, TWiki does not distinguish the data from how it is displayed during edit and during view. Therefor I don't even try
to display it as WikiWords
on a normal page trying to link to the correct topic.
Now, what if I have the name of Participants in a SeminarForm
and all participants are named using a WikiWord
that should link to
a topic for him/her. You can't click on the name in NatSkin
as it does not render WikiWords
automatically in the form at the bottom of the topic.
What you can do is to make use of the FORMFIELD tag and extract the form data in the topic area. Advantage: full control of the view on the model.
Disadvantage: more complicated. Rendering the data of a form properly can then be eased by defining VIEW_TEMPLATEs that in addition hide the normal form
at the bottom completely.
- 07 Mar 2007