Managing content with collections
collective.formcriteria is quite stable now and the latest release includes some additional features.
Firstly, an “Export” document action (ala “Print”, “Send to”, etc.) allows the collection’s results to be exported to CSV where the columns are those specified in the collection’s “Table Columns” fields. This merges (and deprecates) my collective.catalogexport package and duplicates SmartCSVExporter. One advantage of the collective.formcriteria version is that it will stream the results to the response. Since catalog results are lazy, this should be fairly efficient.
I’ve also tightened up the styling on the search form portlet so it’s not quite as unwieldy. I’d still love to get some contributions here from someone better at CSS than I.
But the most significant piece of work has been to get the folder_contents form to work with collection results. The “Tabular Form” display layout is now available for collections.
Use “Table Columns” fields for the folder contents form to control the folder contents columns
Use a “Table Column Links” collection filed to specify which folder contents form columns should link to the item
The “Copy”, “Cut”, “Rename”, “Change State”, and “Delete” folder contents form button now all work for objects listed by the collections even if they are in different folders
With all this in place, collections and formcriteria make a fairly powerful combination for managing Plone content. You can setup a collection with a search form portlet and use search queries to find all the objects you want to apply a workflow transition to, delete, or copy.
Updated on 23 August 2009
Imported from Plone on Mar 15, 2021. The date for this update is the last modified date in Plone.
Commentscomments powered by Disqus