EXT: QForms¶

What does it do?¶

It is an easy to use formgenerator. The complete configuration can be made with a graphical interface. It is based on Typo3's mailform plugin. Mailform is extended with fieldsets and database driven <select>-fields. A special <select>-configuration is added. It is now possible to create <select>-fields which depend on each other, e.g. country -> province. It also supports multi-page forms and a user management for each single field. It provides an on the fly validation of all textfields.

The forms in the Frontend can be be completely styled via CSS. Every element got its own lable field and a <div> container with an unique class and id. A basic CSS file is created when finishing the wizard. You can use almost every character set due to complete UTF-8 encoding.

Screenshots¶

main configuration

simple database browser

frontend display without styles

Installation¶

The installation of this extension is very simple. Just connect to the Typo3 Extension Repository and download «QForms» (qforms), located in the frontend plugin section.

After installation insert a content element from type plugin and choose QForms. Next to the configuration field you will find the Qforms-configuration wizard button.

How to create a form?¶

To create a form element just choose the element you want from the “type” field and press the save button. After saving, you can see new input fields for all attributes the chosen element can handle.

When chosing a text element like textarea, text or password you can choose a validation method containing

• alpamumerical validation
• letters only
• numbers only
• valid Email
• your own hook-function

Every element needs a table and field where its data is saved. In the configuration wizard are two required fields, tablename and fieldname. This will be the table configuration. If you enter a tablename that doesn’t exit, the table will be created once the create tables and css button is pressed. Any entered field that doesn’t exist will be created too, either in a new table or in an existing one.

You have to assign usergroups to each element, that can be seen by that group.

There are some special configurations for the following items:

• radio buttons To use a set of radio buttons you have to use the following notation in the field “list options”buttonLable1|buttonValue1buttonLable2|buttonValue2...
• select fields There is a possibility to create database driven select fields.First click on the DB button next to the “keycolumn” fieldthe next step is to chose the field in the database which contains the values for the items in the selector boxe.g. the UID of the backend user groupsIn the last step the field containing the text for each option is pickedThis example would produce a select field with all names of the backend user groups, when submitted the UID of the chosen user group will be send as value.

In the configuration of a database driven select field you need two tables. One where the formdata is saved and one where the fields you want to show can be found. In the fields tablename and fieldname must be entered the table and the field the submitted data will be saved. For the configuration of the select options you can either choose it from the DB-browser or use the fields tablename_sel and textcolumn_ sel.

After adding a usergroup you can configure the rights of each usergroup. The checkboxes stand for:

ADD - usergroup can add options

EDIT - usergroup can edit options

DEL - usergroup can deleted options

OO - only the user who created the option can see it

GO - only the group containing the user who created the record can see it

To delete a selected usergroup, you have to click the usergroup first and then click thrash can.

dependent select fields The dependent select field can only be configured through the database. It is almost the same procedure as configuring the simple select. The only difference is that you have to choose more fields.The first “keycolumn” field should contain the field with the key that got a reference in the other table.The second step should point on the field containing the optiontext.

For the third step you need to know in which field is the foreign key referenced in step one, choose this one and continue to the fourth step. Now you have to chose two more columns, the one with the optiontext and the one with the value to submit.

FAQ¶

- no questions yet ;-)