I finally got a chance to look at this now. I think I see the problem - in
your case, "free text" is the name of an actual template field. When that's
the case, then of course it should be defined in the form as "{{{field|free
text...". It's only when it's the actual free text input that it should use
"standard input" instead. In fact, it's that ambiguity that caused me to
change this in SF, so that it's obvious which of these two a field named
"free text" is.
-Yaron
On Tue, Oct 14, 2008 at 10:57 PM, CNIT <[EMAIL PROTECTED]> wrote:
>
> > Hi,
> >
> > That's very odd. I don't quite understand the last question - do you
> > have a template field called "freetext"?
> >
>
> Yes, I do. If you're interested, my form and template in utf8 is attached.
> I don't know whether replacing
>
> {{{field|free text|input type=textarea|rows=10|cols=80}}}
>
> with
>
> {{{standard input|free text|input type=textarea|rows=10|cols=80}}}
>
> will cause the same problem on other installations, though.
> 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
-~----------~----~----~----~------~----~------~--~---
