[Vitaly]

Almost finished testing Easy-Forms as "feedback system". Here is list of comments, applyed to such use-case.

1. No option to "disable preview button".

Preview is good for forum posts, but very bad for feedback emails. User should not see, if additional information generated.

Possible solution - one more form option.

2. "Add field" has only basic fields set.

Almost any field have to be edited twice. Once - created. Second - to edit additional parameters.

Not critical. Just unconvenient.

3. Date separator is sent as HTML code in text emails

And date format is hardcoded. It's better to use format string from VB options (not from language preferences).

4. Form description is not "templateable" (no conditions, no variables)

Not convenient, when you wish to automatically generate helper lins, for example, based on user id, and so on.

It would be good to have the same power there, as in form template. With the same variables, just without questions.

(*) Don't know, if the same needed for field descriptions. For now - not, in my case.

5. Additional Notice would be sweet for page with forms list.

(shown as standard VB notice at the top)

Possible solution - one more product setting.

6. When form is hidden from list, it's good to hide "Forms" link from navbar path.

Imagine, that you have multiple forms, used for contacts, forum posts and so on. When user fill "hidden" form for forum post, he will see link to contacts page (forms list) in navbar. That's confusing.

Dont's know, what is better:

- separate option
- hide if form is not listed
- hide if preview button disabled

7. When user fill form, navbar shows text "Viewing form: FormName"

"Viewing form:" - absulutely unnecesary and confusing. Looks like strange debug message.

8. I'd show asterisks (*) for compulsory question with red color.

Can do so with template edit, but think, that would be useful for all as general template.

9. Email has wrong return-path.

If someone write me email via contacts (forms list) page, I expect reply back, but not to forum administrator's email

Possible solution:

- add "email" field and use it automatically in return-path, if filled. Also automatic check can be done, that email conforms to standard.
- if no such field used (or empty) - try to take from member profile

- can be done by hooks, but not convenient (and i don't know how now )

10. Captcha takes the whole row and have unnecessary border (group separator with name)

Is is possible to

- move captcha to right column, as other fields
- remove border
?

=================================================

More general things:

1. Form IDs and fields IDs are absolute and fixed.

That can cause huge problems, if you wish to export form to another site. If those IDs are already reserver to another form, information can be destroyed.

Possible solution:
- address form by text tag.
- numerate field in form namespace and allow duplicated field IDs, if those used for different forms.
- It would be also good to call form not by id, but by tag (as option). For example: misc.php?do=form&ftag=myformname

2. Mass import/export

It's normal practice to develop forms on debug site and then setup those on production. Function "export all" and "import all" would be convenient. At least for backups.

====================================

That's all for interface. Will review code a bit later.