collective.lineage 0.3

Introduction

Lineage is a Plone product that 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.

Useful links

• irc room: #plone-lineage

• pypi: http://pypi.python.org/pypi/collective.lineage

• Plone: http://plone.org/products/collective-lineage

• issue tracker: http://plone.org/products/collective-lineage/issues

• svn repository: http://dev.plone.org/collective/browser/collective.lineage

Detailed Documentation

After you’ve bootstrapped your buildout, installed all the dependencies, and installed Lineage via Site Setup -> Add on Products, you are ready to go.

Add a Child Site

1. In Plone, go to your Home folder.

2. Click Add New, and select Child Folder.

3. Enter the title and description for the Child site.

4. Click Save.

5. 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.

Installation Instructions

If you are using zc.buildout and the plone.recipe.zope2instance recipe to manage your project, you can add collective.lineage to your instance part:

[instance]
...
eggs =
  Plone
  collective.lineage
zcml =
  collective.lineage

Currently this code depends on PLIP 234 which should become a part of Plone 3.3. If you want to use it now you can add the branches of the eggs for the plip:

[buildout]
parts =
  ...
  plip234-branches

[plip234-branches]
recipe = infrae.subversion
location = plip234-branches
as_eggs = true
urls =
  http://svn.plone.org/svn/plone/Plone/branches/calvinhp-inavigationroot-fixes Plone
  http://svn.plone.org/svn/plone/plone.app.layout/branches/calvinhp-inavigationroot-fixes plone.app.layout
  http://svn.plone.org/svn/plone/plone.app.portlets/branches/calvinhp-inavigationroot-fixes plone.app.portlets

Now you can re-run your buildout to get the all the dependencies:

$ ./bin/buildout

Once your buildout is finished, you can start up your instance and install Lineage via the Add-on Products configlet in site setup.

Migration from 0.1 to >0.1

In versions of collective.lineage >0.1, the Child Folder type has been deprecated and you can know activate a folder using the subtyper action when you are on a Folder.

An upgrade step takes care of migrating the old Child Folder to Folder. Make sure to backup your data and then, once you have updated your instance to use the latest collective.lineage, reinstall “Lineage”, it will migrate the items automatically.

Working on the trunk of lineage

To work on the trunk of lineage, do the following:

$ svn co https://svn.plone.org/svn/collective/collective.lineage/trunk/ lineage-trunk $ cd lineage-trunk $ python2.4 bootstrap.py $ bin/buildout -v $ bin/instance fg

Then:

• go to http://localhost:8080/manage (admin/admin)

• add a plone site

• quickinstall lineage in the new plone site

• create a folder and subtype it to see if everything works fine

You can run the tests in debug mode with the following command:

$ bin/test -D

Changelog

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.