PloneFormGen 1.2

For additional information about this project, please visit the project page.

Available downloads

Click to enlarge

Product Package (1.2.0)

For all platforms (221.3 kB)

PloneFormGen 1.2.0 / Scriptable Fields 1.1 Bundle

For all platforms (244.4 kB)

Product Package (1.2RC2)

For all platforms (219.9 kB)

PloneFormGen (1.2RC2) / Scriptable Fields Bundle

For all platforms (242.8 kB)

Release Notes

1.2 Development Roadmap

Few architectural changes are anticipated for 1.2. I plan to release betas as new features are added. All betas should be reliable except for new features, and all tests should pass.

New in this release

• This version is meant to work with Plone 3, Plone 2.5.x and Plone 2.1.x. It is the last version which will work with Plone 2.1.x.
  
• It's now possible to specify multiple e-mail recipients for the TO field via either the recipient override or using a multi-select field.
• Added specialValidator method to BaseFormField to give form fields a way to do a more sophisticated validation than what's allowed by Archetypes-style validators.
• Changed underlying storage mechanism for save-data adapter to use an IOBTree rather than Archetypes lines field storage (a sequence). This should cure a problem with data storage growing geometrically with new inputs (Tracker #81, thanks Jean-Paul Ladage).
  Existing save data adapters will be migrated when first touched by the new PFG version.
  This is NOT backwards compatible! So, you will not be able to save data in 1.2 and revert to 1.1.
• You may now dynamically enable/disable fields via TALES override. Disabling a field removes it from the rendered field list. It will not appear in the form and will not be validated.
• String validators and messages for use with the FormStringField may now be customized by editing the config.py file. I may eventually figure out a way to get this into the configlet.
  
• Add a content override for the RichLabelField.

Feature enhancements in this release

The following features are associated with this release:

#5: Turn Fields On/Off Dynamically

Add form field override to control whether or not field is displayed on form.

Change log

1.2.1

• Using non-ascii chars in the title of a required field would provoke a UnicodeDecodeError on failed validation. Fixed. (Tracker #174; Thanks, Daniel Kraft)
• In a Plone 3 site that has Kupu's UID Linking and/or Image Captioning features enabled, PFG textarea fields show a format select field and cause server crashes. Fixed. (Tracker 173; Thanks John Stahl and Jon Baldivieso)
  

1.2-RC2

•  Dramatically simplify schema for most components by hiding most metadata fields in Plone 3. (Tracker 161; Thanks, Jon Stahl)
•  Empty, hidden lines field caused error on form display. Fixed. (Tracker #151)

1.2-RC1

• Improve error message on mail attempt when no recipient address is found and form owner has no e-mail address. Also, make it less likely by using portal email_from_address as a fallback. (Tracker #140, thanks Andreas Jung)

1.2-Beta-6

• Mailer was having problems with i18n characters in fields in Plone 3+. Fixed. (Tracker #144, thanks Anders Avlesen)
• Manually editing saved data (in a save data adapter) was not working since storage change in 1.2 beta 1. Fixed. (Tracker #145)
• Fixed: Exception when submitting a form with a text field that exceeds the "Max Length" character limit. (Tracker #142)

1.2-Beta-5

• Thanks page editing was having kupu problems in Plone 3 for fields off the default schema. So, when running Plone 3.0, pack them on the default schema. This also brings the schema count down to 5, to avoid schema selection widget. Not ideal, but it's working.
• When a form date field was not required, it was possible to enter invalid dates. Added a special validator that should cause a validation error when a bad date is actually entered, but not if the month or year is left as "--" (Tracker #132)
• Added README_PLONE3.txt to document workaround for permissions problem using selection and multi-selection form fields in Plone 3.0 (fixed in 3.0.1). (Tracker #136)
• There was no status message when validation failed in Plone 3. Fixed. (Tracker #133, thanks Lucie Lejard)
• Validation script was discarding any errors that might already be in the CMFFormController state. Fixed. (Tracker #134, thanks Lucie Lejard)
• Fields in fieldsets were not being offered as options in the mailer's extract recipient and extract replyto options. Fixed. (Tracker #123, thanks Marie Robichon)
• The validation message rewriter for Plone 2.1 was broken, resulting in an error whenever a form wouldn't validate. Fixed. (Tracker #124, thanks Aleksandr Vladimirskiy)
  

1.2-Beta-4

• In Plone 3, Kupu has started saving "<p>&nbsp;</p>" for empty inputs. This  forced white space into the the form if prologue and/or epilogue were empty. Fixed with custom mutators. (Tracker #120, thanks Michael Dunlap)
• Check ids of fields to make sure they don't collide with known  troublesome ids ('zip', 'location', 'language'). Also prevent use of ids that duplicate those in fieldset folders. (Tracker #94, thanks Gregory Hnatiuk; Tracker #107, thanks Kim Nielsen)
• Turn off KSS blur event handling for rendered forms in Plone 3. Maybe  we'll be able to implement in-line validation later.
• Bring Plone 3 macro versions into line with Archetypes 1.5.
• Remove several workarounds for Archetypes 1.5 beta bugs that were fixed in RC3.
• Partial date entries to a Date/Time Field would raise a DateError exception. Fixed. (Tracker #118)
• New Czech translation of plone-ploneformgen domain. Thanks, Jan Pokorny.
• Updated Dutch translations, thanks to: markvl, justi and jladage and  initial translations by Atopia.
  

1.2-Beta-3

• Several changes to address Plone 3.0 beta 3 compatibility. Beta 3 is basically functional with Plone 3.
  
• The 1.2-Beta-2 customizable string validators change introduced a problem that caused an error if a string field had no validator. Fixed.
• Add ability to set display strings for boolean field checked and unchecked. These are used in the thanks page and mailer in place of '0' and '1'. (Tracker #112)

1.2-Beta-2

• Changed "Cancel" button to act as a reset button on rendered forms. It really has no other imaginable purpose. Change default to hide this nearly useless artifact. Add option to set button label.
• Added start, end and future year options to DateTime Field. (Tracker #65, Thanks to Paul Eipper for the suggestion and Jeremy Keiper for the patch.)
• Added new French message translations. Thanks, Gaël Le Mignot.
• Add override to selectively enable/disable fields. Disabling a field removes it from the rendered field list. It will not appear in the form and will not be validated.
• Add facility for customizable string validators and messages for use with the FormStringField. Currently, customization is via the config.py file. I may eventually figure out a way to get this into the configlet.
• Add a content override for the RichLabelField.
• If "PloneFormGen" was missing from any skin layer sets, uninstall or reinstall would fail. Fixed. (Tracker #109, Thanks: Yuri)
  

1.2-Beta-1

• Eradicate use of context['global_vars'], which is not supported in Plone 3. All tests now pass in Plone 3b3 (with patched Archetypes, see http://dev.plone.org/archetypes/ticket/724).
• Extended characters in field title or description would provoke unicode cannot decode error. This occurs on indexing the field, and may be an Archetypes problem. Since there's no good reason to have these searchable, fixed by setting searchable false for field titles and descriptions. (Tracker # 102 and 104, Thanks: Petrus Wang)
• Added Italian translation for Plone domain (add-item menu, schema names and such). Thanks to Carrer Yuri.
• It's now possible to specify multiple e-mail recipients for the TO field via either the recipient override or using a multi-select field. (Tracker #59, Thanks, Edouard Mercier)
• Fixed-point field minimum-value field changed from required to not-required. Requiring it made it impossible to set 0 for a minimum value. (Tracker #98, Thanks: Jeremy Keiper)
• Added specialValidator method to BaseFormField to give form fields a way to do a more sophisticated validation than what's allowed by Archetypes-style validators.
• Changed underlying storage mechanism for save-data adapter to use an IOBTree rather than Archetypes lines field storage (a sequence). This should cure a problem with data object size growing geometrically with new inputs (Tracker #81, thanks Jean-Paul Ladage). Existing save data adapters will be migrated when first touched by the new PFG version.
  This is NOT backwards compatible! So, you will not be able to save data in 1.2 and revert to 1.1.
• Change default download format of new save-data adapters to csv.