Collective.lineage

Latest version: v3.0.0

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

Scan your dependencies

Page 2 of 4

2.0

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

- Fix upgrade steps and migration for 1.x based versions. Please migrate your
site to the latest 1.1.2 version before using 2.0.
[calvinhp]

- Content type framework agnostic: Compatible with Dexterity and Archetypes by
allowing definitions of Subsites on plone.folder.interfaces.IFolder objects.
[thet]

- Remove dependency on p4a.subtyper. Enable and disable subsite menus are now
in the object_buttons action menu.
[thet]

- Remove controlpanel. Use language translations for translating interface
elements instead.
[thet]

- Remove deprecated ChildFolder content type.
[thet]

- Remove upgrade steps. Please upgrade to most recent 1.x version in the 1.x
branch, deinstall collective.lineage and use the 2.x branch then and
reinstall.
[thet]

- Make objectactions and site-switchter translateable and add German
translations [fRiSi]

1.1.2

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

- This is a migration step to `2.0` release **only**. Once installed,
run the upgrade from the Plone Add-Ons control panel and then upgrade
to `2.0` to re-enable management of child sites.
[calvinhp]

- Add upgrade step to remove `p4a.subtyper` interfaces and created a
GenericSetup profile to remove the component from the component registry
[calvinhp]

1.1.1

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

- Add an adapter to allow the child site to use the portal image
scales. Fixes https://github.com/collective/collective.lineage/issues/18
[ableeb]

- In the uninstall profile, remove componentregistry
``collective.lineage.childsite`` utility from the component registry.
[thet]

- Add Chinese translations.
[adam139]

1.1

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

- Fixed imports to allow lineage to be compatible with
Plone >= 4.1
[calvinhp]

- Update dependencies and import locations and make
collective.lineage compatible with Plone 4.3.
[thet]

- Add new events for ``WillBe`` created and removed. This will make
add-ons like lineage.registry able to properly deal with the child
site before the component registry is removed.
[claytron]

- Restored Plone 3.3 compatibility (if plone.app.registry is present)
[keul]

- i18n fixes and added italian translation
[keul]

- Uninstall step fixed (closed 8 and 11) but also removed other stuff
left behind
[keul]

1.0.1

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

- Remove ``setup_site`` from the ``install`` function since this is no
longer needed. Also bumped the metadata version so that the upgrade
step actually runs.
[claytron]

- PEP8
[clayton]

1.0

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

- PEP8 and pyflakes cleanup
[claytron]

- modernized tests, using layers now.
[jensens]

- fixed failing test with subscribers, subtype added event is not an object
event!
[jensens]

- moved code to github and increased Plone version used in integrated buildout
to 4.1-latest.
[jensens]

- The subscribers are now registered to the IChildSite interface so
that custom child site types are still made into IObjectManagerSites.
[rossp]

- Added an ``isChildSite`` method to the ``LineageUtils`` view, to determine if
the current context is part of a child site.
[davidblewett]

- Id attribute added to the lineage selection form to make Diazo/XDV theming
easier.
[timo]

- German translation added.
[timo]

- added support for plone domain
[macagua]

- Added Spanish translation
[macagua]

- Changed the ``collective.lineage.childsite`` component to use the
``IFolderishContentTypeDescriptor`` interface instead of
``IPortalTypedFolderishDescriptor``, allowing any folderish type to become
a child site.
[davidblewett]

- Fixed issue where deactivating a Child Site wouldn't remove it from the
Lineage dropdown menu
[calvinhp]

- Format README so that it fits within 72 columns.
[claytron]

Page 2 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.