This change shouldn't affect the functioning of the FCK editor. The problem
you're seeing is most likely caused by the fact that the FCK editor isn't
working on at least some versions of Internet Explorer. I haven't looked
into it yet; hopefully there's a fix.
-Yaron
On Mon, Oct 13, 2008 at 12:20 PM, Marc Feickert <[EMAIL PROTECTED]
> wrote:
> Does the new {{{standard input}}} allow for FCK editor to replace the
> free text area? I have been unable to get that t work with 1.3.3, though the
> documentation says it should.
>
>
>
> *From:* [email protected] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Yaron Koren
> *Sent:* Monday, October 13, 2008 9:35 AM
> *To:* [email protected]
> *Subject:* [Semantic Forms] Version 1.3.4 - free text now a "standard
> input", bug fixes
>
>
>
> 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.
>
> - the combination of "autocomplete on property" and the textarea input
> type, which wasn't working before, now works.
>
> - the YUI Javascript library has been upgraded from 2.5.2 to 2.6.0.
>
> - the #forminput parser function was doing incorrect URL-encoding that was
> causing a problem in some non-English languages: this has been fixed -
> thanks to Jung Gun Lim for the fix.
>
> - the #formlink parser function no longer adds a newline before the link.
>
> - the 'UploadWindow' mini-page has a new meta tag that fixes the encoding
> of Cyrillic and possibly other character sets; thanks to Dmitriy.
>
> - for email validation, the suffix no longer has to be at most 3 characters
> - now it can be up to 6 (this may have to be increased again later).
>
> - a fix was made so that autocomplete values that contain a newline won't
> break the Javascript.
>
> -Yaron
>
>
> ------------------------------
> NOTICE: This email message is for the sole use of the intended recipient(s)
> and may contain confidential and privileged information. Any unauthorized
> review, use, disclosure or distribution is prohibited. If you are not the
> intended recipient, please contact the sender by reply email and destroy all
> copies of the original message.
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
