Introduction
============

This package provides a generic Plone form generator.
Use it to build simple, one-of-a-kind, web forms that save or mail form input.

Repository for this add on is at https://github.com/smcmahon/Products.PloneFormGen.
A documentation area is at http://developer.plone.org/reference_manuals/active/ploneformgen/
and an issue tracker at https://github.com/smcmahon/Products.PloneFormGen/issues

Please use the Plone users' mailing list or the #plone irc channel for
support requests. If you are unable to get your questions answered
there, or are interested in helping develop the product, contact Steve
McMahon: steve@dcn.org.

1.7 Notes
=========

PFG 1.7 is intended for use with Plone 4.1+. If you're using Plone < 4.1, PFG 1.6
will be a better choice.

If upgrading from an earlier version, uninstall and reinstall PFG to add new
functionality.

jQuery UI
---------

PloneFormGen depends on collective.js.jqueryui. Depending on the version
of Plone you're on, you'll have to install a different version of
collective.js.jqueryui. Please refer to collective.js.jqueryui documentation
for more information: https://pypi.python.org/pypi/collective.js.jqueryui/1.10.3

Overview
========

PloneFormGen is a generic Plone form generator using fields,
widgets and validators from Archetypes. Use it to build simple,
one-of-a-kind, web forms that save or mail form input.

To build a web form, create a form folder, then add form fields as
contents. Individual fields can display and validate themselves for
testing purposes. The form folder creates a form from all the contained
field content objects.

Final disposition of form input is handled via plug-in action products.
Action adapters included with this release include a mailer, a
save-data adapter that saves input in tab-separated format for later
download, and a custom-script adapter that makes it possible to script
simple actions without recourse to the Zope Management Interface.

To make it easy to get started, newly created form folders are
pre-populated to act as a simple e-mail response form.

Dependencies
============

Plone: Plone 4.1+

Requires PythonField, TALESField and TemplateFields from Jens W.
Klein's ScriptableFields bundle: http://plone.org/products/scriptablefields/
(automatically loaded if you install via Python package).

Encryption of e-mail requires the Gnu Privacy Guard, GnuPG, also known
as gpg. See README_GPG.txt for details.

CAPTCHA support requires either collective.captcha or collective.recaptcha.
See README_CAPTCHA.txt for details.

Installation
============

*   Just add ``Products.PloneFormGen`` to the eggs section of your buildout
    configuration and run buildout.

*   Restart Zope.

*   Go to the Site Setup page in the Plone interface and click on the
    Add/Remove Products link. Choose PloneFormGen (check its checkbox) and
    click the Install button. If PloneFormGen is not available on the
    Add/Remove Products list, it usually means that the product did not
    load due to missing prerequisites.

*   If necessary, use the PloneFormGen configlet in the "Add-on Product
    Configuration" section of Site Setup to customize the product for your
    site.

Permissions
===========

Site managers may control the visibility and availability of many
PloneFormGen functions by changing permissions for user roles. A
control panel configlet controls role/permission associations for the
portal root. For an explanation of how PloneFormGen permissions map to
form folder and form field fields, see improvement proposal #3, Provide
ways to hide advanced options from classes of
users: http://plone.org/products/ploneformgen/roadmap/3 .

Security
========

As shipped, only managers may use TALES expressions to override
defaults and validators. You may wish to add additional roles, but keep
in mind that this is a potential security risk; it basically gives the
same powers as scripting or skin editing.

Javascript/CSS Support for Some Fields
======================================

Some fields, like the rich text editor and the calendar widget on the
d