Monkey-patch Plone 3 to make Plone 4 Generic Setup import steps to continue working
Project description
Introduction
This product is only useful if you are in the very sad situation of needing a Plone product on a Plone 3.3 installation, but the product is now compatible only with Plone 4+.
Keeping code compatibility with older version is commonly simple (see “Upgrading Plone 3.x to 4.0” and “Upgrading Plone 4.0 to 4.1”).
However there’s a major problem: Generic Setup import step changes. Sadly those changes are difficult to be backported (because no-one wants to maintain a Plone-3-only compatible profile).
How it works
This product will not backport Generic Setup new features to Plone 4.3, but monkey-patch Generic Setup to tolerate new XML parameters.
cssregistry
Old CSSRegistry registration didn’t know nothing about authenticated, applyPrefix and bundle paramenters.
Those parameters are now ignored.
If authenticated is provided and expression is not provided, the new authenticated feature is translated in the old way (using expression).
jsregistry
Old CSSRegistry registration didn’t know nothing about authenticated, and bundle paramenters.
Those parameters are now ignored.
If authenticated is provided and expression is not provided, the new authenticated feature is translated in the old way (using expression).
types
Old PropertyManagerHelpers supports only content_icon registration instead of the new icon_expr.
If icon_expr is provided, it will be used as content_icon. Also: an attempt to fix the data format is done.
Authors
This product was developed by RedTurtle Technology team.
Changelog
0.2 (2012-12-12)
added log messages when patches are used [keul]
added support for substitution of new style icon_expr with old-style content_icon [keul]
0.1 (2012-12-12)
Initial release
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
