Hi,
That's very odd. I don't quite understand the last question - do you have a
template field called "freetext"?
-Yaron
On Tue, Oct 14, 2008 at 4:55 AM, CNIT <[EMAIL PROTECTED]> wrote:
>
>
> > Hi all,
> >
> > Version 1.3.4 of Semantic Forms has been released. It has the
> > following changes:
> >
> > - the 'free text' field is no longer defined as "{{{field|free
> > text}}}" - it's now "{{{standard input|free text}}}". This was mainly
> > done so that the free text field could be placed among the various
> > fields of a template - currently, the parser assumes that, if it's
> > placed between "for template" and "end template", it's just another
> > template field. Also, this change makes it clearer, when reading a
> > form definition, that the free text field is different from regular
> > fields. The old definition still works, for backwards compatibility.
> >
>
> Hmm.. I've tried to replace
>
> {{{field|free text|input type=textarea|rows=10|cols=80}}}
>
> with
>
> {{{standard input|free text|input type=textarea|rows=10|cols=80}}}
>
> and now the page using template returns
> {{{freetext}}} string
>
> instead of value of freetext field.
>
> Reverting back to old syntax - template works properly again.
>
> Shall I replace {{{freetext}}} in template with something else?
> Dmitriy
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
