Version 0.1.3 released

WFF Version 0.1.3 has been released after some testing.

The main features introduced in this version are

1. Simple form validation.
2. Tagging engine

1. Simple form validation
Simple form validation is just that. You can specify which fields
you want to make mandatory by having an associated label containing an
asterisk. (*). For example, if you have a textfield named “firstName”,
which you want to make mandatory, you simply need to have a
corresponding label within your form that looks like this:

<label for="firstName">First Name *</label> 

2. Tagging engine
The tagging is what enables WFF to currently perform validation and will help introduce more complex validation rules as well as new features in the future. WFF tags look like this:

<wff:tag_name options/>

or

<wff:tag_name options></wff:tag_name>

Tags must be placed in the html form file by the form author (that’s you!) before submitting it to WFF. Each tag, of course, has a specific purpose. Currently, WFF recognizes only 1 tag:

<wff:validaton_errors /> 

This tag must be present in any form submitted to WFF 0.1.3+. (If not, WFF will raise an error upon generation) This tag, in particular, represents a placeholder for the location where the user wants the form validation errors to appear. For e.g: at the top of the form in red letters, or below the submit button. Upon form generation, WFF will replace this tag with the corresponding PHP code which will show any form validation errors.

Feel free to give the new WFF a try and let us know how you feel about it!

In the next few blog posts, we will cover in more details how Tagging works, its purpose as well as more info on form validation.