collective.behavior.localregistry 1.0b2

Dexterity behavior to add a local plone.app.registry for content types, it adds a local component with a layered proxy registry.

Table of Contents

• Life, the Universe, and Everything

• Mostly Harmless

• Don’t panic

• Share and Enjoy

• Changelog

  • 1.0b2 (2014-03-12)

  • 1.0b1 (2013-04-21)

Life, the Universe, and Everything

Dexterity behavior to add a local plone.app.registry for content types, it adds a local component with a layered proxy registry.

Mostly Harmless

Got an idea? Found a bug? Let us know by opening a support ticket.

Don’t panic

Installation

To enable this product in a buildout-based installation:

1. Edit your buildout.cfg and add collective.behavior.localregistry to the list of eggs to install:

   [buildout]
   ...
   eggs =
       collective.behavior.localregistry

2. If you are using Plone 4.1 you may need to extend a Dexterity known good set (KGS) to make sure that you get the right versions of the packages that make up Dexterity:

   [buildout]
   ...
   extends =
       https://good-py.appspot.com/release/dexterity/1.2.1?plone=4.1.6

After updating the configuration you need to run ‘’bin/buildout’’, which will take care of updating your system.

Go to the ‘Site Setup’ page in a Plone site and click on the ‘Add-ons’ link.

Check the box next to collective.behavior.localregistry and click the ‘Activate’ button.

Note

You may have to empty your browser cache and save your resource registries in order to see the effects of the product installation.

Share and Enjoy

collective.behavior.localregistry would not have been possible without the contribution of the following people:

• Juan Pablo Giménez

• Héctor Velarde

• David Beitey

You can find an updated list of package contributors on GitHub.

Changelog

There’s a frood who really knows where his towel is

1.0b2 (2014-03-12)

• Fix package credits. [hvelarde]

• Pillow was removed as a package dependency. [hvelarde]

• Allow objects with this behavior applied to be renamed. Previously, this failed with a KeyError as the underlying registry needed to be reconfigured for a new path. [davidjb]

1.0b1 (2013-04-21)

• Initial release.