Collective-formcriteria

Latest version: v2.1

Safety actively analyzes 630523 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 5

2.0a3

------------------

* Change the permission for the grouped listing view so that anonymous
visitors can access the view when the content is published.
Thanks to Larry Pitcher for the report.
[rossp]

* Add support for columns that don't have corresponding catalog
metadata. Be aware that using such columns can greatly affect
performance as export requires looking up every object to retrieve
the data.
[rossp]

2.0a2

------------------

* Fixed a problem with a faulty type assumption regarding
DateTimeFields in the FormDateCriterion. The FormDateCriterion
doesn't actually used a DateTimeField.
[rossp]

* Refactor the <form> and <button> based batch_macros so as to not
conflict with other uses of the full "navigation" macro within an
existing form resulting in nested <form>s.
[rossp]

2.0a1

------------------

* Ensure that the "default" profile is used by portal_quickinstaller
by... well, default. :-)
[rossp]

* Use a <form> and <button> elements in the navigation/paging
batch_macros to prevent "uri too long" errors when using paging with
many form criteria.
[rossp]

* Use method="post" for the criteria form to address "uri too long"
when lots of form criteria are used. Reported by mauro and
confirmed to happen with just two date fields.
[rossp]

* Added defines for Plone4 complatibility in folder_listing
skin template.
[seletz]

* Fix navigation_recurse template to match current Plone 4 version.
[seletz] [ramonski]

* Add a collection listing portlet that makes use of the
folder_listing macros for a richer portlet. [rossp]

* fix issue producing
AttributeError: 'NoneType' object has no attribute 'title_or_id'
when adding path criterions.
[hplocher]

* Fix '<input type="hidden" name="sort_on"...', now uses the default
sort criteria if present

* Use individual persistent objects to represent table columns such as
with the fodler_contents view. UI for editing the folder_contents
column objects has yet to be implemented.

* Fix <tfoot> usage [rossp]

* Integrate sort criteria with folder contents view columns for KSS
sorting [rossp]

* Add pulldown/select, single-value criterion based on
FormSelectionCriterion, FormPortalTypeCriterion, and
FormReferenceCriterion [rossp]

1.1.1

------------------

* "Select all" and "Show all" (KSS) on folder contents view [rossp]

1.1.0

------------------

* Use folder_contents instead of folder_contents_view to fix the links
back to the folder contents form. [rossp]
* Tighten up the search form portlet spacing. [rossp]
* 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 [rossp]
* Fix folder contents form buttons, "Copy", "Cut", "Rename", "Change
State", and "Delete" now all work for objects listed by the
collections even if they are in different folders. [rossp]

1.0.2

------------------

* Add some missing portal_types for criteria [rossp]
* Fix a unicode bug with GS portlets.xml import of the search portlet
[rossp]

Page 2 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.