PloneFormGen 1.1.3

Up to Product page

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

Available downloads

Release Notes

Tested with	Plone 2.5, Plone 2.1
State	Final release
License	GPL
Release Manager	Steve McMahon
Released	2007/01/01

Major new features in this release:

• Fieldset folders may be used to group fields into XHTML fieldsets with optional legends.
• More fine-grained permissions controlling the availability of features by user role. A control-panel configlet makes it easy to adjust these for the portal as a whole.
• Overrides for mailer subject, sender and recipient.
  
• Control-panel configlet allows setup of defaults for mail addressing, template and MIME type.
  
• A new "Custom Script Adapter" by Mikko Ohtamaa (#plone: Moo). This is an action adapter that makes it easy to script success actions without having to use the ZMI to add/manipulate a python script. Note: PythonField (from the ScriptableFields bundle) is now required.
• A rudimentary facility to return friendlier, hopefully translatable, alternatives to the Archetypes validation messages. Ideally, we'll abandon it when this gets straightened out in Archetypes.
• It's now possible to add form fields from outside the product and have them operate on the same level as the built-in ones. The "examples" directory contains an example product that adds a third-party widget as a form field (DataGridField).
  
• Optional tabular and record supplemental views for save data adapter.
• Dutch, German, Polish and Spanish translations.
  

Dependencies

• Requires PythonField, TALESField and TemplateFields from Jens W. Klein's ScriptableFields bundle.
• If you are using Plone 2.1.x, you will need to either 1) rename or delete PloneFormGen's configure.zcml or 2) upgrade to Five 1.2. See the Five Compatability Matrix.
  

Feature enhancements in this release

The following features are associated with this release:

#2: Fieldsets

Add ability to organize forms with XHTML fieldsets

#3: Provide ways to hide advanced options from classes of users

Site admins should be able to use a configlet to control the level of complexity revealed to different classes of users.

#4: Make it easy to add new widgets

Refactor, clarify APIs and provide examples to help widget authors integrate their widgets with PloneFormGen

Change log

1.1.3

• 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.

1.1.2

• 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)

1.1.1

• The "strip trailing white space" fix in 1.1 handled the issue for validation, but the unchanged field was still processed and mailed/saved. Fixed.
• Fix a bug introduced by "strip trailing white space" fix in 1.1 that would cause a name error when validating an individual field (not a form).
• When htmlValue for Selection and Multi-Selection fields doesn't find the submitted value in the field vocabulary, it should go ahead and return what was submitted. (Thanks, lzdych for a code fix)
• Use the portal_transforms text_to_html transform to convert multi-line text field inputs to html. This will convert eols to breaks rather than collapsing lines. (Thanks: Darrick Servis)
  

• Minor i18n fixups.
  

1.1

• The mail adapter was truncating subject lines longer than 76 characters due to a bad interaction between security testing and header encoding. Fixed. (Tracker #84, thanks to Mike Sassak for a great bug report)
• Restore document actions to base view template. The reason for leaving them out probably wasn't as good as I thought when first excising them. (Tracker #86, thanks to Gregory Hnatiuk)
• Strip trailing white space in all string-ish fields. Also, don't accept required fields when only white space is submitted. (Fixes Tracker #79: thanks Rene Pijlman)
• For Selection or Multi-Selection form fields, no input could result in an error "AttributeError 'NoneType' object has no attribute 'encode'". This was a bug in the display labels fix in RC3. Fixed. (Tracker #80, thanks Rene Pijlman)
• The "Thanks Page" option in the form folder edit view would display python scripts and other non-Plone objects. Fixed. (Tracker #78, Thanks Marie Robichon)
  

1.1-RC3

• The creation of sample objects in initializeArchetypes left catalog orphans for the portal_factory objects. Solve the problem by removing them from the portal_catalog and uid_catalog, hopefully not causing other problems in the process. (Tra cker #74, Thanks Jeremy Keiper)

• Made the thanks-page and mailer display labels for selection and multi-selection fields rather than the values. (Tracker #71; thanks to Radim Novotny for diagnosis and patch.)

1.1-RC2

•  Added localized time support for display (thanks page and mailer) renderings from Date-Time Field. (Tracker #71, thanks, Sufyan Patel)
• Removed the "hidden" option from most fields. Archetypes support for it was uneven and not really necessary for anything more than strings, lines and text. So, why not get it out of the way? (Tracker #69, thanks to Radim Novotny for pointing out the problem.)
• Added optional tabular and record supplemental views for save data adapter.
  

• Added convenience method 'getColumnTitles' to saver.

1.1-RC1

• File fields would not show up on the thanks page, and their column names would be omitted from saver data. Fixed.

• CustmScriptAdapter 'fields' parameter was mis-identified as 'results' in sample comment documentation. Fixed. (Thanks, Brook Milligan)
• Made the success action given to CFMFormController always be "traverse_to". The form previously would traverse to objects implementing IPloneFormGenThanksPage, but redirect to other pages or templates. While there might be reasons to do this, they're overwhelmed by the puzzle this might pose for the user trying to figure out why request was available for one type and not another. Note that this does not apply to overrides, where the action type must always be specified.
• Custom validators for File Fields always received None as "value" parameter due to the fact that the file widget appends _file to the input name. Fixed. (Tracker #64; Thanks, Kiran Jonnalagadda for a diagnosis and patch.)
  

1.1-Beta-4

• Attempts to use acquired scripts in form setup and after validation overrides of form would provoke an AttributeError. Scripts inside the form folder worked. This was due to an unfortunate choice of workaround for expression context poisoning: aq_explicit was being used for the context. Added a cleanExpressionContext routine to clean the expression context instead by deleting the cache for the object context after calling a TALES expression. That allowed fixing the context to allow acquisition. (Tracker #62)
• Added convenience method InputAsDictionaries to save-data adapter. Returns saved data as list of dictionaries with column keys.
• fgGetSuccessAction was unnecessarily causing a traverse from the Zope root. This was a problem if any parent of the form was private. Fixed. (Tracker #60; Thanks Marcel)
• Downloading data from the save data adapter would provoke a Unicode exception if data included non-ASCII, 'use column names' was in effect, and one of the preset extra data choices was checked. Fixed. (Tracker #55)
  
• DataGridField example: DGF field wasn't being added to fieldset allowed types. Fixed. (Tracker #61, thanks, Paul Eipper)
• Added explicit, empty .po files for English to (hopefully) resolve tracker #56 (thanks, Christof Haemmerle and sydw (#plone).

1.1-Beta-3

• Added Polish (PL) translation donated by Lukasz Lichota. Fixed up a couple of duplicate msgids revealed by the new translation files.
• More uninstall cleanup. On uninstall, remove FormFolder and FieldsetFolder from siteProperties use_folder_tabs and typesLinkToFolderContentsInFC. (Tracker #57, thanks DigitalD)
• The validation message cleanup routine introduced in 1.1 beta 1 would fail with a message "TypeError: cleanupMessage() takes exactly 1 argument (2 given)" under Plone < 2.5. Fixed.
• Added class selector to div surrounding form to facilitate CSS decoration. (Tracker #46, Thanks Steve Rauch)
• When possible, get guess_content_type from zope.app.content_types rather than OFS.content_types. Now no deprecation errors in 2.5.2 RC 1.
• A KeyError exception in an action adapter would be swallowed by a too extensive try/except. Fixed. (Tracker #54, thanks, Maurits van Rees)
• Added an example of adding a new widget to PFG from another product. Copy PFGDataGrid from the examples directory to Products/ to activate a DataGridField form field.
• Using an after-validation override was clobbering the expression context, causing an error if we ended up traversing to a template. Fixed.
• On uninstall, remove 'PloneFormGen' layer from all skin selections.
  

1.1-Beta-2

• Added "Execution Condition" override to action adapters. This allows conditional execution of action adapters depending on form input.

• Atopia <info@atopia.nl> has contributed a Dutch translation. Thanks!
• Simon Käser has contributed a German translation. Thanks!
  

1.1-Beta-1

• Added a rudimentary facility to return better alternatives to the Archetypes validation messages. These should also be translatable. This will probably need refinement. Ideally, we'll abandon it when this gets straightened out in Archetypes. Thanks to Matej Baric (#plone mte) for pressing me on the need for this.
• The thanks page option to ignore empty fields wasn't working. Fixed.
• Workaround what I consider a Zope marshalling error: the production of lists like ['one', ''] and [''] for list fields. PFG will now pop list results if the last item is an empty string. This is done before validation.
• Made installation add FormFolder to default_page_types. (Tracker #49: Thanks, Jon Stahl)

1.1-Alpha-4

• Fixed bad interaction between Thanks Pages and fieldsets. (Tracker #44, Thanks: David Sandy)
• Attempted to exterminate all the cases where PFG tests to see if a field is a label or file field by checking the meta_type. Replaced with tests of isLabel or isFileField methods. This is a first step towards making it easier to add support for new field types.

1.1-Alpha-3

• Added "Fieldset Folder", which puts its enclosed fields into an XHTML fieldset with an optional legend. (Feature Enhancement Proposal #2, thanks Michael Dunlap)

• Added TALES overrides for subject, sender and recipient to the mailer. (Tracker #43, thanks: Pierre-Yves Landure)
• Fix for Tracker #42 -  Editing Short Names Has No Effect. (Thanks: Kevin Strasser)
  

1.1-Alpha-2

• Added default mail addressing setup to configlet.
• Added default mail template setup to configlet.
• Activate action adapters on creation to save confusion.
• Set up a portal_properties property sheet for site configuration persistence.
  

1.1-Alpha-1

• Added a configlet to control association of roles and PFG permissions at the portal root.
• Moved recipient fields of mail adapter to default schema. They're the most likely to be customized.
• Added specific permissions for advanced and encryption-related fields. We'll use these to hide the fields from roles that needn't see them.
• Add framework to allow different add permissions for different content types. Set individual add permission for Custom Script Adapter.
• Mailer wasn't picking up owner e-mail address unless owner is a manager.  Fixed.
• Removing an active action adapter would result in a KeyError on form submit. Fixed. The missing adapter will now be ignored.
• Added "Custom Script Adapter" by Mikko Ohtamaa (#plone: Moo). This is an action adapter that makes it easy to script success actions without having to use the ZMI to add/manipulate a python script. Note: PythonField (from the ScriptableFields bundle) is now required.
• Change configure.zcml.plone25 to be configure.zcml. Users of Plone 2.1.x will need to delete or rename this file to avoid errors (unless they have independently updated Five).