Introduction
============
Lineage is a Plone extension.
It allows subfolders of a Plone site to appear as autonomous Plone sites to the everyday user.
This hub and spoke structure allows site administrators to easily manage multiple, seemingly independent, sub-entity websites in one Plone. Furthermore, the "parent" site can access and view the content in all the "child" sites while the child sites only view their own content.
The parent site can also syndicate chosen content to the selected child sites.
Lineage is less complex and easier to manage than a cluster of nested Plone sites but gives users all the same benefits.
Lineage can be used within a large organization to manage multiple microsites, such as school district sites, university departments, corporate product sites, public library satellites, professional association events, and more.
Version information
===================
- 3.x: Plone 5.2, 6.0 - Python 3.8+
- 2.x: Plone 5.0, 5.1, 5.2 - Python 2.7
- 1.x: Plone 4.3
Useful links
============
.. image:: https://travis-ci.org/collective/collective.lineage.svg?branch=master
:target: https://travis-ci.org/collective/collective.lineage
.. image:: https://coveralls.io/repos/collective/collective.lineage/badge.svg?branch=master&service=github
:target: https://coveralls.io/github/collective/collective.lineage?branch=master
- pypi: http://pypi.python.org/pypi/collective.lineage
- Plone: http://plone.org/products/collective-lineage
- issue tracker: https://github.com/collective/collective.lineage/issues/
- code repository: http://github.com/collective/collective.lineage/
Detailed Documentation
======================
Installation
------------
Bootstrapped your buildout with all the dependencies.
Install Lineage via ``Site Setup -> Add on Products``.
Now you are ready to go.
Add a Child Site:
1. In Plone, go to the place where you want to add a new child site.
2. Click Add New, and add a `Folder`.
3. Enter the title and description for the Child site.
4. Click Save.
5. Click the `Actions` drop down and select `Enable Subsite`.
This "activates" the child site behavior.
6. The Plone site now has a child site.
A drop down will appear at the top of the Plone to the left of the site actions area.
A user can select the parent site or any child sites from this drop down.
Lineage extensions
------------------
There is a bunch of extensions available.
They are helpful when there is the need of more special features within subites.
`lineage.index <https://pypi.python.org/pypi/lineage.index>`_
Adds an index and metadata that allows to search for content of a specific childsite only
`collective.rooter <https://pypi.python.org/pypi/collective.rooter>`_
Force catalog queries to obey the current subsite
`lineage.registry <https://pypi.python.org/pypi/lineage.registry>`_
Provides a plone.app.registry for Lineage subsites.
It adds a local component with a layered-/proxy-registry
`lineage.themeselection <https://pypi.python.org/pypi/lineage.themeselection>`_
Provides custom theme selection for Lineage subsites.
For more search Pypi
Upgrading to 2.X
----------------
Lineage `2.0` is a major upgrade to the software and will require you to have
updated to the `1.1.2` version before you migrate any existing Lineage child
sites to the new version. Lineage `2.0` removes all dependencies on
`p4a.subtyper` and makes the product Plone 5 ready. The `1.1.2` release of
Lineage is only used to migrate your existing Lineage `1.1` sites up to the
needed state for the new `2.0` release.
Steps for upgrading:
1. Install version `1.1.2` into your existing Lineage powered site
2. Go to the Plone Site Setup and from the Add-Ons panel click the button to
upgrade the Lineage product
3. Install version `2.0` into your existing Lineage powered site
4. Go to the Plone Site Setup and from the Add-Ons panel click the button to
upgrade the Lineage product
5. Enjoy Lineage `2.0`
Changelog
=========
3.0.0 (2023-11-20)
------------------
- Drop Python 2.7 support and code cleanup.
[petschki, thet]
2.3.1 (2023-11-20)
------------------
- Add support for Plone 6 while keeping Plone 5 compatibility.
[petschki, thet]
2.3 (2020-02-16)
----------------
- Add support for Python 3
[cillianderoiste]
- Fixed for Plone 5.2
[ajung]
- Fix broken image link in README, fix project URL in setup.py
[tkimnguyen]
- Remove extraneous code that was causing a len() deprecation warning, #58
[tkimnguyen]
- require plone.dexterity >= 2.9.3 for Python 3 (#55)
[petri,tkimnguyen]
- use pyflakes 2.1.0 to fix tests
[tkimnguyen]
2.2 (2019-01-02)
----------------
- Load the image traverser only if plone.app.imaging is installed.
[thet]
- Support registering browser layers for child sites for per-child-site theming.
[rpatterson]
- Simplify travis configuration and fix travis test run.
[thet]
- Depend on ``Products.CMFPlone`` instead of ``Plone`` to not fetch unnecessary dependencies.
[thet]
- Add descriptors.py back in with a placeholder so the site doesn't complain about it missing.
[abosio]
2.1 (2016-10-03)
----------------
- Implement new utility method ``parent_site``.
[thet]
- Setup related cleanups.
[thet]
- fix ``IImagingSchema`` traverser for Plone 4, disable in Plone 5
[jensens]
- basic tests for enable/disable childsite
[jensens]
- household chores: make flake-8 happy (utf8-headers), some other minor pep8,
add travis configuration and let tests run against 4.1 to 5.0 (and fixed
them).
[jensens]
- Include ``get_image_traverser`` only when
``plone.app.imaging.interfaces.IImagingSchema`` is available, which is not
the case in Plone 5.
[thet]
- Peel out ``enable_childsite`` and ``disable_childsite`` from the
``lineage_tool`` view, so that it can be easily used programmatically.
[thet]
- We don't want to enable or disable a childsite on a default page. Traverse up,
until a non-default page is found.
[thet]
- Add ``current_childsite`` method to ``@@lineageutils`` view, which returns
the current lineage subsite object or ``None``, if no lineage subsite is
active.
[thet]
- Re-add the ``@@lineageutils`` browser page with it's useful ``isChildSite``
method. Fix ``isChildSite`` to be called as a method on it's view.
[thet]
- Added portuguese pt-br translation
[lccruz]
2.0 - (2014-10-29)
------------------
- 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 - (2014-10-29)
--------------------
- 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 - (2014-06-26)
--------------------
- 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 - (2013-06-02)
------------------
- 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 - (2012-10-13)
--------------------
- 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 - (2012-10-08)
------------------
- 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]
0.6.1 - (2011-01-12)
--------------------
- Making sure that we copy the fact that the item inherits from its parent or not
[lucielejard]
- Updated the ignores
[lucielejard]
- Fixed the upgrade so that when we grab the layout of a folder, it does not
get it using acquisition if it doesn't have one, fixes #18
[lucielejard]
- Copy over sharing settings from child folder to new folder, fixes #38
[anthonygerrard]
- Fix by not renaming the child folder, instead create new folder with temp
id and rename that to the child folder id after the child folder has been
deleted, fixes #37
[anthonygerrard]
- Adding a failing test case for #37 here as it is a serious bug but I have
no idea how to fix it
[anthonygerrard]
- In lineage 0.1 child folders never inherited their parent's portlets so
always block parent portlets when migrating, fixes #34
[anthonygerrard]
- Added a warning if portlet manager is not available on the new folder,
fixes #35
[anthonygerrard]
- Copy portlet assignments from and blocking settings across on migration,
fixes #34
[anthonygerrard]
- Refactor tests so that migration tests are in their own class and so can
have common setup logic
[anthonygerrard]
- Read the default page of the child folder before conversion and then set
it afterwards, fixes #18
[anthonygerrard]
0.6 - (2010-05-25)
------------------
- used z3c.autoinclude and removed the zcml slug in buildout.cfg
[tbesluau]
- update the security settings at the end of the migration so
that the workflow is applied correctly on the new migrated
folders, fixes #20
[lucielejard]
- updated the migration so it keeps the layout on the folder
fixes #18
[lucielejard]
0.5.1 - (2010-05-12)
--------------------
- updated docs as per duffyd suggestions
[lucielejard]
0.5 - (2010-05-11)
------------------
- updated docs with links to the branches created by
duffyd for the backports of the plip #234 mods to
Plone 3.1.7
[lucielejard]
0.4 - (2010-04-30)
------------------
- updated docs about PLIP
- Update docs with information about "activation" behavior.
[clayton]
0.3 - (2010-04-30)
------------------
- getting the unit testing to work with plone4 and allowing
childsite editing with plone4, refs #16 [tbesluau]
- updated README.txt with useful links [lucielejard]
- added tests for the uninstall of lineage [lucielejard]
- updated the list of items todo, removed rolemap.xml since
we don't use it anymore, updated the history with the recent
changes [lucielejard]
- moved the registration of the utility in component registry so
it gets registered locally, this fixes #5 [lucielejard]
- added a deprecation warning on the Child Folder type
[lucielejard]
- put back some old zcml so the Child Folder migration can be tested
[lucielejard]
- added a test for the migration from 0.1 to >0.1
[lucielejard]
- updated the version in metadata.xml for the upgrade step
[lucielejard]
- made the Child Folder type not globally addable
[lucielejard]
- added an upgrade step that will migrate the old Child Folder objects
[lucielejard]
- added an import various step so that the upgrade step gets run
automatically on reinstall
[lucielejard]
- Set up for i18n translations
[claytron]
- Moving over to an 'activation' based system instead of having a
'Child Folder' type. Now a folder will have the option for a
subtype named 'Child Site'.
http://plone.org/products/collective-lineage/issues/3
http://plone.org/products/collective-lineage/issues/1
[claytron]
- Remove 'Child Folder' add/edit interfaces. The type still remains
so that we can do a migration.
[claytron]
- Added uninstall profile and hooked it up to the Quickinstaller
[claytron]
- Added subtyper.xml to the uninstall profile that will deactivate
all 'Child Sites' in the portal. This depends on p4a.subtyper
code that has not yet been released. This also solves the
export/import issue
http://plone.org/products/collective-lineage/issues/2
[claytron]
- Added a subscriber to create the local component site (this was
in the 'Child Folder' type before)
[claytron]
0.2 - (2010-04-08)
------------------
- Doc clarifications
[claytron]
0.1 - (2009-02-10)
------------------
- Initial public release
Special Thanks
==============
Six Feet Up would especially like to thank Martin Aspeli for his
inspiration and the Duke Clinical Research Institute group for project
funding.
Raw data
{
"_id": null,
"home_page": "https://pypi.org/project/collective-lineage",
"name": "collective.lineage",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": "",
"keywords": "plone lineage",
"author": "Six Feet Up, Inc.",
"author_email": "info@sixfeetup.com",
"download_url": "https://files.pythonhosted.org/packages/5d/24/75d4aaf5fa400e6f04b20ed6d864c779509464f067ba4f36904c76569575/collective.lineage-3.0.0.tar.gz",
"platform": null,
"description": "Introduction\n============\n\nLineage is a Plone extension.\nIt allows subfolders of a Plone site to appear as autonomous Plone sites to the everyday user.\nThis hub and spoke structure allows site administrators to easily manage multiple, seemingly independent, sub-entity websites in one Plone. Furthermore, the \"parent\" site can access and view the content in all the \"child\" sites while the child sites only view their own content.\nThe parent site can also syndicate chosen content to the selected child sites.\nLineage is less complex and easier to manage than a cluster of nested Plone sites but gives users all the same benefits.\n\nLineage can be used within a large organization to manage multiple microsites, such as school district sites, university departments, corporate product sites, public library satellites, professional association events, and more.\n\n\nVersion information\n===================\n\n- 3.x: Plone 5.2, 6.0 - Python 3.8+\n- 2.x: Plone 5.0, 5.1, 5.2 - Python 2.7\n- 1.x: Plone 4.3\n\n\nUseful links\n============\n\n.. image:: https://travis-ci.org/collective/collective.lineage.svg?branch=master\n :target: https://travis-ci.org/collective/collective.lineage\n\n.. image:: https://coveralls.io/repos/collective/collective.lineage/badge.svg?branch=master&service=github\n :target: https://coveralls.io/github/collective/collective.lineage?branch=master\n\n- pypi: http://pypi.python.org/pypi/collective.lineage\n- Plone: http://plone.org/products/collective-lineage\n- issue tracker: https://github.com/collective/collective.lineage/issues/\n- code repository: http://github.com/collective/collective.lineage/\n\n\nDetailed Documentation\n======================\n\nInstallation\n------------\n\nBootstrapped your buildout with all the dependencies.\nInstall Lineage via ``Site Setup -> Add on Products``.\nNow you are ready to go.\n\nAdd a Child Site:\n\n1. In Plone, go to the place where you want to add a new child site.\n2. Click Add New, and add a `Folder`.\n3. Enter the title and description for the Child site.\n4. Click Save.\n5. Click the `Actions` drop down and select `Enable Subsite`.\n This \"activates\" the child site behavior.\n6. The Plone site now has a child site.\n A drop down will appear at the top of the Plone to the left of the site actions area.\n A user can select the parent site or any child sites from this drop down.\n\n\nLineage extensions\n------------------\n\nThere is a bunch of extensions available.\nThey are helpful when there is the need of more special features within subites.\n\n`lineage.index <https://pypi.python.org/pypi/lineage.index>`_\n Adds an index and metadata that allows to search for content of a specific childsite only\n\n`collective.rooter <https://pypi.python.org/pypi/collective.rooter>`_\n Force catalog queries to obey the current subsite\n\n`lineage.registry <https://pypi.python.org/pypi/lineage.registry>`_\n Provides a plone.app.registry for Lineage subsites.\n It adds a local component with a layered-/proxy-registry\n\n`lineage.themeselection <https://pypi.python.org/pypi/lineage.themeselection>`_\n Provides custom theme selection for Lineage subsites.\n\nFor more search Pypi\n\nUpgrading to 2.X\n----------------\n\nLineage `2.0` is a major upgrade to the software and will require you to have\nupdated to the `1.1.2` version before you migrate any existing Lineage child\nsites to the new version. Lineage `2.0` removes all dependencies on\n`p4a.subtyper` and makes the product Plone 5 ready. The `1.1.2` release of\nLineage is only used to migrate your existing Lineage `1.1` sites up to the\nneeded state for the new `2.0` release.\n\nSteps for upgrading:\n\n1. Install version `1.1.2` into your existing Lineage powered site\n2. Go to the Plone Site Setup and from the Add-Ons panel click the button to\n upgrade the Lineage product\n3. Install version `2.0` into your existing Lineage powered site\n4. Go to the Plone Site Setup and from the Add-Ons panel click the button to\n upgrade the Lineage product\n5. Enjoy Lineage `2.0`\n\n\nChangelog\n=========\n\n3.0.0 (2023-11-20)\n------------------\n\n- Drop Python 2.7 support and code cleanup.\n [petschki, thet]\n\n\n2.3.1 (2023-11-20)\n------------------\n\n- Add support for Plone 6 while keeping Plone 5 compatibility.\n [petschki, thet]\n\n\n2.3 (2020-02-16)\n----------------\n\n- Add support for Python 3\n [cillianderoiste]\n\n- Fixed for Plone 5.2\n [ajung]\n\n- Fix broken image link in README, fix project URL in setup.py\n [tkimnguyen]\n\n- Remove extraneous code that was causing a len() deprecation warning, #58\n [tkimnguyen]\n\n- require plone.dexterity >= 2.9.3 for Python 3 (#55)\n [petri,tkimnguyen]\n\n- use pyflakes 2.1.0 to fix tests\n [tkimnguyen]\n\n2.2 (2019-01-02)\n----------------\n\n- Load the image traverser only if plone.app.imaging is installed.\n [thet]\n\n- Support registering browser layers for child sites for per-child-site theming.\n [rpatterson]\n\n- Simplify travis configuration and fix travis test run.\n [thet]\n\n- Depend on ``Products.CMFPlone`` instead of ``Plone`` to not fetch unnecessary dependencies.\n [thet]\n\n- Add descriptors.py back in with a placeholder so the site doesn't complain about it missing.\n [abosio]\n\n\n2.1 (2016-10-03)\n----------------\n\n- Implement new utility method ``parent_site``.\n [thet]\n\n- Setup related cleanups.\n [thet]\n\n- fix ``IImagingSchema`` traverser for Plone 4, disable in Plone 5\n [jensens]\n\n- basic tests for enable/disable childsite\n [jensens]\n\n- household chores: make flake-8 happy (utf8-headers), some other minor pep8,\n add travis configuration and let tests run against 4.1 to 5.0 (and fixed\n them).\n [jensens]\n\n- Include ``get_image_traverser`` only when\n ``plone.app.imaging.interfaces.IImagingSchema`` is available, which is not\n the case in Plone 5.\n [thet]\n\n- Peel out ``enable_childsite`` and ``disable_childsite`` from the\n ``lineage_tool`` view, so that it can be easily used programmatically.\n [thet]\n\n- We don't want to enable or disable a childsite on a default page. Traverse up,\n until a non-default page is found.\n [thet]\n\n- Add ``current_childsite`` method to ``@@lineageutils`` view, which returns\n the current lineage subsite object or ``None``, if no lineage subsite is\n active.\n [thet]\n\n- Re-add the ``@@lineageutils`` browser page with it's useful ``isChildSite``\n method. Fix ``isChildSite`` to be called as a method on it's view.\n [thet]\n\n- Added portuguese pt-br translation\n [lccruz]\n\n\n2.0 - (2014-10-29)\n------------------\n\n- Fix upgrade steps and migration for 1.x based versions. Please migrate your\n site to the latest 1.1.2 version before using 2.0.\n [calvinhp]\n\n- Content type framework agnostic: Compatible with Dexterity and Archetypes by\n allowing definitions of Subsites on plone.folder.interfaces.IFolder objects.\n [thet]\n\n- Remove dependency on p4a.subtyper. Enable and disable subsite menus are now\n in the object_buttons action menu.\n [thet]\n\n- Remove controlpanel. Use language translations for translating interface\n elements instead.\n [thet]\n\n- Remove deprecated ChildFolder content type.\n [thet]\n\n- Remove upgrade steps. Please upgrade to most recent 1.x version in the 1.x\n branch, deinstall collective.lineage and use the 2.x branch then and\n reinstall.\n [thet]\n\n- Make objectactions and site-switchter translateable and add German\n translations [fRiSi]\n\n\n1.1.2 - (2014-10-29)\n--------------------\n\n- This is a migration step to `2.0` release **only**. Once installed,\n run the upgrade from the Plone Add-Ons control panel and then upgrade\n to `2.0` to re-enable management of child sites.\n [calvinhp]\n\n- Add upgrade step to remove `p4a.subtyper` interfaces and created a\n GenericSetup profile to remove the component from the component registry\n [calvinhp]\n\n\n1.1.1 - (2014-06-26)\n--------------------\n\n- Add an adapter to allow the child site to use the portal image\n scales. Fixes https://github.com/collective/collective.lineage/issues/18\n [ableeb]\n\n- In the uninstall profile, remove componentregistry\n ``collective.lineage.childsite`` utility from the component registry.\n [thet]\n\n- Add Chinese translations.\n [adam139]\n\n1.1 - (2013-06-02)\n------------------\n\n- Fixed imports to allow lineage to be compatible with\n Plone >= 4.1\n [calvinhp]\n\n- Update dependencies and import locations and make\n collective.lineage compatible with Plone 4.3.\n [thet]\n\n- Add new events for ``WillBe`` created and removed. This will make\n add-ons like lineage.registry able to properly deal with the child\n site before the component registry is removed.\n [claytron]\n\n- Restored Plone 3.3 compatibility (if plone.app.registry is present)\n [keul]\n\n- i18n fixes and added italian translation\n [keul]\n\n- Uninstall step fixed (closed #8 and #11) but also removed other stuff\n left behind\n [keul]\n\n1.0.1 - (2012-10-13)\n--------------------\n\n- Remove ``setup_site`` from the ``install`` function since this is no\n longer needed. Also bumped the metadata version so that the upgrade\n step actually runs.\n [claytron]\n\n- PEP8\n [clayton]\n\n1.0 - (2012-10-08)\n------------------\n\n- PEP8 and pyflakes cleanup\n [claytron]\n\n- modernized tests, using layers now.\n [jensens]\n\n- fixed failing test with subscribers, subtype added event is not an object\n event!\n [jensens]\n\n- moved code to github and increased Plone version used in integrated buildout\n to 4.1-latest.\n [jensens]\n\n- The subscribers are now registered to the IChildSite interface so\n that custom child site types are still made into IObjectManagerSites.\n [rossp]\n\n- Added an ``isChildSite`` method to the ``LineageUtils`` view, to determine if\n the current context is part of a child site.\n [davidblewett]\n\n- Id attribute added to the lineage selection form to make Diazo/XDV theming\n easier.\n [timo]\n\n- German translation added.\n [timo]\n\n- added support for plone domain\n [macagua]\n\n- Added Spanish translation\n [macagua]\n\n- Changed the ``collective.lineage.childsite`` component to use the\n ``IFolderishContentTypeDescriptor`` interface instead of\n ``IPortalTypedFolderishDescriptor``, allowing any folderish type to become\n a child site.\n [davidblewett]\n\n- Fixed issue where deactivating a Child Site wouldn't remove it from the\n Lineage dropdown menu\n [calvinhp]\n\n- Format README so that it fits within 72 columns.\n [claytron]\n\n\n0.6.1 - (2011-01-12)\n--------------------\n\n- Making sure that we copy the fact that the item inherits from its parent or not\n [lucielejard]\n\n- Updated the ignores\n [lucielejard]\n\n- Fixed the upgrade so that when we grab the layout of a folder, it does not\n get it using acquisition if it doesn't have one, fixes #18\n [lucielejard]\n\n- Copy over sharing settings from child folder to new folder, fixes #38\n [anthonygerrard]\n\n- Fix by not renaming the child folder, instead create new folder with temp\n id and rename that to the child folder id after the child folder has been\n deleted, fixes #37\n [anthonygerrard]\n\n- Adding a failing test case for #37 here as it is a serious bug but I have\n no idea how to fix it\n [anthonygerrard]\n\n- In lineage 0.1 child folders never inherited their parent's portlets so\n always block parent portlets when migrating, fixes #34\n [anthonygerrard]\n\n- Added a warning if portlet manager is not available on the new folder,\n fixes #35\n [anthonygerrard]\n\n- Copy portlet assignments from and blocking settings across on migration,\n fixes #34\n [anthonygerrard]\n\n- Refactor tests so that migration tests are in their own class and so can\n have common setup logic\n [anthonygerrard]\n\n- Read the default page of the child folder before conversion and then set\n it afterwards, fixes #18\n [anthonygerrard]\n\n\n0.6 - (2010-05-25)\n------------------\n\n- used z3c.autoinclude and removed the zcml slug in buildout.cfg\n [tbesluau]\n\n- update the security settings at the end of the migration so\n that the workflow is applied correctly on the new migrated\n folders, fixes #20\n [lucielejard]\n\n- updated the migration so it keeps the layout on the folder\n fixes #18\n [lucielejard]\n\n\n0.5.1 - (2010-05-12)\n--------------------\n\n- updated docs as per duffyd suggestions\n [lucielejard]\n\n\n0.5 - (2010-05-11)\n------------------\n\n- updated docs with links to the branches created by\n duffyd for the backports of the plip #234 mods to\n Plone 3.1.7\n [lucielejard]\n\n\n0.4 - (2010-04-30)\n------------------\n\n- updated docs about PLIP\n\n- Update docs with information about \"activation\" behavior.\n [clayton]\n\n\n0.3 - (2010-04-30)\n------------------\n\n- getting the unit testing to work with plone4 and allowing\n childsite editing with plone4, refs #16 [tbesluau]\n\n- updated README.txt with useful links [lucielejard]\n\n- added tests for the uninstall of lineage [lucielejard]\n\n- updated the list of items todo, removed rolemap.xml since\n we don't use it anymore, updated the history with the recent\n changes [lucielejard]\n\n- moved the registration of the utility in component registry so\n it gets registered locally, this fixes #5 [lucielejard]\n\n- added a deprecation warning on the Child Folder type\n [lucielejard]\n\n- put back some old zcml so the Child Folder migration can be tested\n [lucielejard]\n\n- added a test for the migration from 0.1 to >0.1\n [lucielejard]\n\n- updated the version in metadata.xml for the upgrade step\n [lucielejard]\n\n- made the Child Folder type not globally addable\n [lucielejard]\n\n- added an upgrade step that will migrate the old Child Folder objects\n [lucielejard]\n\n- added an import various step so that the upgrade step gets run\n automatically on reinstall\n [lucielejard]\n\n- Set up for i18n translations\n [claytron]\n\n- Moving over to an 'activation' based system instead of having a\n 'Child Folder' type. Now a folder will have the option for a\n subtype named 'Child Site'.\n http://plone.org/products/collective-lineage/issues/3\n http://plone.org/products/collective-lineage/issues/1\n [claytron]\n\n- Remove 'Child Folder' add/edit interfaces. The type still remains\n so that we can do a migration.\n [claytron]\n\n- Added uninstall profile and hooked it up to the Quickinstaller\n [claytron]\n\n- Added subtyper.xml to the uninstall profile that will deactivate\n all 'Child Sites' in the portal. This depends on p4a.subtyper\n code that has not yet been released. This also solves the\n export/import issue\n http://plone.org/products/collective-lineage/issues/2\n [claytron]\n\n- Added a subscriber to create the local component site (this was\n in the 'Child Folder' type before)\n [claytron]\n\n\n0.2 - (2010-04-08)\n------------------\n\n- Doc clarifications\n [claytron]\n\n\n0.1 - (2009-02-10)\n------------------\n\n- Initial public release\n\n\nSpecial Thanks\n==============\n\nSix Feet Up would especially like to thank Martin Aspeli for his\ninspiration and the Duke Clinical Research Institute group for project\nfunding.\n",
"bugtrack_url": null,
"license": "GPL",
"summary": "The microsite creation product for Plone",
"version": "3.0.0",
"project_urls": {
"Homepage": "https://pypi.org/project/collective-lineage"
},
"split_keywords": [
"plone",
"lineage"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "9eef4c653eab12152d38b50868e9bbeccb8a6cae4d662b4f34eec8737c31c7c2",
"md5": "34f754f636927b13987996f461c4e93d",
"sha256": "7d09ad3543f5facbade1ce58f3a22e8c07dc8cddc4d485470738d2be41736014"
},
"downloads": -1,
"filename": "collective.lineage-3.0.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "34f754f636927b13987996f461c4e93d",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 26453,
"upload_time": "2023-11-20T11:25:10",
"upload_time_iso_8601": "2023-11-20T11:25:10.251514Z",
"url": "https://files.pythonhosted.org/packages/9e/ef/4c653eab12152d38b50868e9bbeccb8a6cae4d662b4f34eec8737c31c7c2/collective.lineage-3.0.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "5d2475d4aaf5fa400e6f04b20ed6d864c779509464f067ba4f36904c76569575",
"md5": "20ad2d5fad293b516e990f58eba23f9b",
"sha256": "9911fd040d34acc304d4f7be51795d8bc8d1ab5a8593617ce818ce730968f05e"
},
"downloads": -1,
"filename": "collective.lineage-3.0.0.tar.gz",
"has_sig": false,
"md5_digest": "20ad2d5fad293b516e990f58eba23f9b",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 31493,
"upload_time": "2023-11-20T11:25:12",
"upload_time_iso_8601": "2023-11-20T11:25:12.646947Z",
"url": "https://files.pythonhosted.org/packages/5d/24/75d4aaf5fa400e6f04b20ed6d864c779509464f067ba4f36904c76569575/collective.lineage-3.0.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-11-20 11:25:12",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "collective.lineage"
}
JSON