Collective.contact.widget

Latest version: v1.13

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

Scan your dependencies

Page 3 of 4

1.2.1

Not secure
------------------

- UI : improve prefill of add new contact overlay form.
[thomasdesvenain]

1.2

Not secure
----------------

- We can give as source param a 'relations' value to filter on contents
related to an other content.
[thomasdesvenain]

1.1

Not secure
----------------

- Don't include closeOnClick: true in javascript, so it defaults to
global configuration.
[vincentfretin]

- UI improvements :
- Add contact link is displayed after user has filled a search.
- We have and explicit help message next to contact link.
- Contact creation form title is pre-filled with user search.
- The search input has a placeholder.
[thomasdesvenain]

- Execute prepOverlay only if it hasn't been done yet, this avoid to have a
pbo undefined error when you have recursive overlays.
[vincentfretin]

- The jqueryui autocomplete plugin conflicts with the jquery autocomplete
plugin used by plone.formwidget.autocomplete, disable the jqueryui one.
[cedricmessiant]

- Do not break dexterity content type when we don't have a REQUEST
(in async context).
[thomasdesvenain]

- We can add contact and contact list fields TTW on dexterity content types.
[thomasdesvenain]

1.0

Not secure
----------------

- Check do_post_sort attribute on source to be able to disable the sorting.

- Declare dependencies on z3c.relationfield and plone.formwidget.contenttree.

- Remove ploneform-render-widget view for content provider, this is now
in plone.app.z3cform since 0.7.3.

1.0rc1

Not secure
-------------------

- Added hidden and rtf mode templates.
[vincentfretin]

- Don't open tooltip in tooltip.
[vincentfretin]

0.12

Not secure
-----------------

- Decode title, returning unicode, to standardize term attributes
[sgeulette]

Page 3 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.