Changes between Version 39 and Version 40 of quintagroup.dropdownmenu

Timestamp:

Jun 5, 2013 3:14:05 PM (11 years ago)

Author:

naomin

Comment:

--

quintagroup.dropdownmenu

@@ -76 +76 @@
 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}}}
+{{{
+action_id = prefix + category_id + suffix
+}}}
 where:
 
-category_id:    is id of correspondent CMF Action Category
+category_id: 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
+
+{{{
++ portal_tabs
 |- home
 |- blog_sub
 |-+ blog
 | |-- 2009
-| |-- 2010}}}
+| |-- 2010
+}}}
+
 By default the root of dropdown menu is 'portal_tabs' category.