Latest version: 1.2 (for 2.x - I've run on 2.4.5+)

xForms is essentially a fork of Liaise 1.26, but adds anti-spam-bot security via captcha. Functionality includes custom forms, required fields, send to groups, (sortable) forms listing, hidden forms, and many other preferences. Like its predecessor, it lacks database storage and individual ad-hoc email addressing.

Installation

Install per standard XOOPS module installation.

Other Notes

Note: the installation sets up a cryptic directory in the XOOPS uploads directory (security through obfuscation). If desired, change this to whatever seems appropriate in the preferences, and then add the index.html file to the directory.

Making forms is generally intuitive and easy. You'll need to make a XOOPS group for the users to receive a form (even if only one person). I suggest using names of ContactUs-Groupname.

Defects

Introduction Text

For some reason, xForms removed the index intro preference - and added noforms (and captcha). The problem is in the xoops_version.php file for the configs. The config array value [9] is written twice, once for the intro, and then overwritten by the noforms. To fix the issue, renumber the config array in xForms and then update the module.

The intro field no longer allows HTML. To allow, in index.php on line 56, change the displayTarea() call to be makeTareaData4Show() (as it was in Liaise). Note that it still adds breaks tags to every line, thus delete the linebreaks in any HTML (run it all as a "single line of HTML code/text") (although one will still appear at the end). Otherwise, remove the BR tags using smarty replace or edit the code to not make breaks.

Enhancement Requests

Additional Variables

The only replacement variables built in to the system are {UNAME} and {EMAIL}; however, in /class/elementrenderer.php, you can add others in the switch statement with case 'text.'

Separation of Presentation and Functional Layers

There remains too much HTML in the functional layer passed to the presentation layer. Break them up into array items with individual component variables and then use the templates as originally intended. This is a legacy issue.

Send To Configurations

Instead of using groups, often times, I need to send to just a single user and/or just a simple e-mail address (that gets changed as the person behind the position changes). Instead of having to setup a group for this and add one user to it, why not allow for the option of a single user, an e-mail address, and/or possibly a combination of all.