Products-plonekeywordmanager

Latest version: v3.0.3

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

Scan your dependencies

Page 3 of 4

1.7

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

- Added ability to mix unicode and non-unicode keywords and changes.
Fixes a bug with collective.dancing (and plone.z3cform) upgrading
form inputs to unicode automagically.
[dunlapm]

- Restify the CHANGES.txt file.
[toutpt]

- Add keywords import through genericsetup.
[toutpt]

- Add a default profile based on Extensions/Install.py.
[toutpt]

- remove zope2 interface.
[toutpt]

1.6

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

- Fixed handling of non-ASCII Keywords in Controller Python Scripts
prefs_keywords_action_change.cpy and prefs_keywords_action_delete.cpy [disko]

- Added tests for the above mentioned bugfixes. [disko]

- Added German translation. [disko]

1.6b2

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

- No longer assumes that the index name is the same as the name of the
underlying schema field. [jessesnyder]

1.6b1

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

- Eggification from PloneKeywordManager into Products.PloneKeywordManager. This
package is only supported for Plone 3 now. It may or may not work in Plone 2.5. [dunlapm]

- Added support for multiple keyword indexes. If you have more than one keyword
field on your content type(s) then you will still be able to manage all of your
keywords. If you only use the single default field then you will get the normal
interface.

1.5alpha1

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

- Plone 2.5 and Plone 3 compatibility for product PloneKeywordManager. [glenfant]

0.4

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

- Added Brazilian Portuguese i18n support.
[Rafahela Bazzanella <rafabazzanellayahoo.com.br>]

Page 3 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.