redturtle.custommenu.factories 0.2.0b

Installation

Simply add the egg to your buildout, and re-run it. Remember to add also the ZCML overrides.

[instance]
...
eggs =
    ...
    redturtle.custommenu.factories
...

zcml =
    ...
    redturtle.custommenu.factories
    redturtle.custommenu.factories-overrides
...

After this, install the new product in Plone.

Uninstallation

You can reinstall the products safely without lose any customization data. If you uninstall it, all customization will be removed from your Plone site, leaving no garbage behind.

Customize the menu

In your “Add new…” menu you’ll find a new “Customize menu…” entry. This will lead you to a form where you must enable customization feature on the current context. After this you can use the a customization form where you can manage local menu changes.

The used context is always the container where you can find the context, or the context itself if it’s a container.

for every new entry you can/must fill this informations:

id

Enter here a string to be used to add an HTML id attribute to the new element. You can not provide it, but if you use an already existing ids, the new one will override the old. In this way you can replace one of the native (or inherited) menu entry with a new ones.

name

Required. Provide the string to be used for displaying the new element.

description

The description is used to provide a tooltips hovering the element.

icon

A TALES expression that can be used to give an icon to the new element (very common).

condition

A TALES condition expression. If not provided, the new element is added to the menu. In provided it is evaluated as True or False, so the element is displayed or not.

URL

Required. A TALES expression used to render the HREF attribute on the link in the element. You have total freedom here: you can also render a string as “javascript:…” to provide some Javascript features.

Also you can inherit the customization done in the site root everywhere in the site, adding this to all other customizations. You can also locally block the inherit of root customization but you can also make new menu elements defined in the root available only in the root itself.

Also, you can give a right id to new entries not only to override menu element from Plone normal behaviour, but also for change a customization done in the site root.

TALES expressions

In the TALES expression above, you can use those variables:

context

The current context, as Plone normal meaning

container

The container of the current context, or the context itself if the context is a container. This is useful when writing expression that keep in mind the default document in a folder.

portal_url

The portal_url tool, taken from the Plone site.

Examples and advanced features

Take a look to the README.txt file included to see some examples and to discover what this products can do in your Plone site.

0.2.0b - (2010-02-17)

• now local customizations must be enabled and disabled per-context

• fixes to XHTML structure and validation

• fixed CSS class names to be camelCase as Plone does

• added tests

• fixed templates to be test compatible

• fixed a bug on entry deletion

• added missing check on required element for entries (in facts were optional)

• added egg support for z3c.autoinclude

• now False condition for an element with id hide inherited element with same id

• added Plone 4 compatibility

0.1.0a - (2010-01-04)

• initial release