Products.facultystaffdirectory

Latest version: v5.0

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

Scan your dependencies

Page 1 of 4

5.1

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

- Nothing changed yet.

5.0

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

* Works with Plone 5.0 [vangheem, tkimnguyen]

* Update to not use Products.ATReferenceBrowserWidget
[vangheem]

* Avoid finding extraneous people in classification query
(e.g. graduate students) by looking up only classifications_people
relationships [tkimnguyen]

* Load only Products.ATContentTypes:base profile. Fixes
https://github.com/collective/Products.FacultyStaffDirectory/issues/4
[gil-cano]

3.1.3

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

* Added a MANIFEST.in to exclude the examples folder from being packaged with
the egg to work around the SandboxViolation from EasyInstall when installing
FSD via buildout on Windows systems.
[cah190]

* Work around membrane shortcoming which caused group property providers to
be enumerated as users, raising an error and preventing further user
enumeration.
[Laurence Rowe]

3.1.2

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

* Added a 'use site default' option to the available editors list. Thanks to
David Carter for reporting this issue and supplying a patch.
[cah190]

* Require Products.membrane >= 2.1.4 to get the property sheet typing fix which
affects the ext_editor field.
[cah190]

3.1.1

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

* Added a sample-content profile. [pumazi]

* fsd_atoz_view and department_textual_view should now work on Department objects
living outside the FacultyStaffDirectory root on a site. Warning: external
Departments will only work reliably for situations where there is a single
FacultyStaffDirectory object in a site. If there are multiple
FacultyStaffDirectory objects, then use of external Departments will have
undefined behavior.
[cah190]

* Fixes to author.cpt to support Plone 4.x. Thanks to Paul Roeland for reporting
this problem and supplying a patch.
[cah190]

* Fixed fsd_atoz_view to work with last names having first characters outside the
A to Z range. We now allow for any valid unicode character. Thanks to
Toni Haka-Risku for reporting this problem and supplying a patch which served
as a starting point for this fix.
[cah190]

3.1

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

* Retagging as 3.1.
[cah190]

Page 1 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.