quintagroup.dropdownmenu 1.2.2

Building you dropdown menu with portal_actions

Starting from Plone 3 portal actions introduced CMF Action Category containers, it opened opportunity to build nested actions trees. Though CMF Action Category does not behave as a regular action, it has different set of properties. We introduced convention in quintagroup.dropdownmenu that requires to have a specially named Action for each Actions Category. The id of each such action must be build using the rule:

action_id = prefix + category_id + suffix

where:

category_id:

is id of correspondent CMF Action Category

prefix:

defined in DropDownMenu configlet, default value ‘’

suffix:

defined in DropDownMenu configlet, default value ‘_sub’

So, the actions structure can look like:

+ portal_tabs
|- home
|- blog_sub
|-+ blog
| |-- 2009
| |-- 2010

By default the root of dropdown menu is ‘portal_tabs’ category.

Compatibility

• Plone 4 sample CSS file based on Sunburst theme provided

• Plone 3.0-3.3 the default CSS file has to be overridden

Installation

• add http://good-py.appspot.com/release/plone.app.registry/1.0b2 to your versions

• add quintagroup.dropdownmenu to eggs in your buildout

• install in Plone with Quick Installer

• find more details inside docs/INSTALL.txt

1.2.2 - June 21, 2011

• Fixed caching content tabs and action tabs

• portal_action generated menu caching is conditional and switched off for now

1.2.1 - June 15, 2011

• Caching fixed

1.2 - Apr 6, 2011

• Changed z3c.autoinclude includeDependencies to simple include to work in plone 3.2 [kroman0]

• drop-down overlay bug fixed [wald]

• cleared unnecessary classes, changed styles to current and hover element [gvizdyk]

• Fixed uninstallation. Added unisntallation with QI [mylan]

• Tests refactoring [mylan]

1.1.1 - Sep 23, 2010

• fixed the docs markup [chervol]

1.1 - Sep 22, 2010

• removed debug code [chervol]

• fixed the dropdown CSS

• fixed the Home tab highlight

1.0 - Sep 08, 2010

• Initial release