Support/Comments for FormIt 1.1.6-pl

This is an auto-generated topic for FormIt 1.1.6-pl by splittingred.

Brief Description:

Automatically validate, parse and email forms. Redirect to thank you pages. Add your own hooks as Snippets to handle forms dynamically. Validate with custom Snippets. All is possible in FormIt, the new form processing Snippet for MODx Revolution 2.0.
New in 1.1.6

• Added emailReplyToName and emailReplyTo properties for email hook
• i18n of Snippet properties
• Removed SMTP properties as those are now in Revolution 2.0
• Added multibyte support
• Added islowercase, isuppercase validators
• Fixed bug in html emails where linebreaks were being ignored

See the Official Documentation here:
http://svn.modxcms.com/docs/display/ADDON/FormIt

I’m just getting into Revolution and with it FormIt (my Page is already up and running with revolution, works beautiful! Nice work!) I have to wrap my head around a new Form Snippet (I have a good experience with eForm), which is genreally kind of, let’s say, not very easy =)...

so version 1.1.6 came out yesterday? =)...great, I installed it via package management, so far so good, but I don’t even understand the "what’s new"-points.

what do "i18n of Snippet properties" and "multibyte support" mean and how does it affect formIt?

I also had a look at the documentation and saw the form template chunk and I asked myself if this would be valid html with the :validator in the name attribute? Or will this be stripped out before parsing?

thanks for your reply!

Why don’t you just get started with a basic form and see what problems you run into along the line. This is the best way to learn, in combination with the docs.
A quick pass through some html validator tool would show that <input type="text" name="username:required" value="[[+fi.username]]" /> is perfectly valid html, so there doesn’t seem to be a problem with validators in the name attribute.

i18n of Snippet properties : it is made easier to make the property description in other languages.
multibyte support: It now is configurable if you want to use php’s multibyte functions instead of the regular ones.

for changes on the code level see:
http://github.com/splittingred/FormIt/commits/

Thanks for your answer,

this is what I try, "just get started" =)...and it is also my preferred way to learn, but I often try to get all information about a topic first (or whatever I try to learn) and mostly some (maybe stupid) questions come up at this point, so that’s where I am right now.

I didn’t say it is invalid, I just never saw it this way but as you said, I could validate it myself! Does the validator just not care about the content of an attribute, can this be the case?

there comes another question along with the inputs: How about the placeholders in the value attribute, the [[+fi.name]], as you mentioned above... I don’t see through technically yet but I would like to because I want to make FormIt work as an "AJAX-Form" (I had this with eForm...) and I think these placeholders are something crucial...

so for what are they there and what do they do?

thanks for your patience!

Quote from: lluuuk at Aug 11, 2010, 01:53 PM

....................
I didn’t say it is invalid, I just never saw it this way but as you said, I could validate it myself! Does the validator just not care about the content of an attribute, can this be the case?

From the HTML4 spec...
ID and NAME tokens must begin with a letter ([A-Za-z]) and may be followed by any number of letters, digits ([0-9]), hyphens ("-"), underscores ("_"), colons (":"), and periods (".").
IIRC HTML5 loosens this, the only rule is that the name attribute can’t be an empty string if given. Just to be sure i tend to always use simple lowercase alphabetical names.

there comes another question along with the inputs: How about the placeholders in the value attribute, the [[+fi.name]], as you mentioned above... I don’t see through technically yet but I would like to because I want to make FormIt work as an "AJAX-Form" (I had this with eForm...) and I think these placeholders are something crucial...

so for what are they there and what do they do?

In that respect i don’t think there is a big difference with eform:

renders to


So i’m guessing in Formit things like value="[[+fi.username]]" will also become something like value=""

Just wanted to say thanks for contributing this great form building tool. I’ve been using it extensively on a current project and haven’t come across any bugs or stability problems so far. Very extensible as well with the hooks functionality. I love it.

~ Mike