= quintagroup.dropdownmenu =

[[PageOutline]]

quintagroup.dropdownmenu package allows to build multilevel portal dropdown menu based on nested portal_actions categories inside portal_tab category as well as based on portal content structure.

== Links ==

  * Home page - http://quintagroup.com/services/plone-development/products/quintagroup.dropdownmenu
  * Releases - http://pypi.python.org/pypi/quintagroup.dropdownmenu
  * Repository -  http://svn.quintagroup.com/products/quintagroup.dropdownmenu

== Introduction ==

This package allows Plone websites display multilevel portal dropdown menu based on nested portal_actions categories inside portal_tab category. It also allows to define whether to put content tabs before or after action tabs, and a bit more... For details see below.
	
== Notes ==
	
You may have actions/content-based tabs as deep as you wish, but then you'll need to tweek default dropdown menu css rules a bit, default css rules show only the first 4 levels of tabs 

== Requirement ==

Plone 3.x, Plone 4.0

== Migration from [wiki:qPloneDropDownMenu qPloneDropDownMenu] ==

In case qPloneDropDownMenu product was previously installed, it will automatically detect legacy settings, migrate it to a newly created settings registry and update portal_actions tool if required along with removing old portal_dropdownmenu one.
	
Also installation procedure will uninstall qPloneDropDownMenu product itself (in case it's still installed) and clean up everything after it. 
	
Note: to successfully migrate old tabs it's required to have a valid html markup, otherwise migration procedure won't be able to move tabs correctly.

== Installation ==

quintagroup.dropdownmenu can be installed as a Python package by adding it to eggs section of a buildout:

{{{

[instance]
....
eggs =
    ....
    quintagroup.dropdownmenu

}}}

Then Re-run buildout with: 

{{{
   $ ./bin/buildout
}}}

Restart the Zope server with the following command in the terminal: 

{{{
   $ ./bin/instance restart
}}}

Activate lone Drop Down Menu via Quickinstaller in Plone: Site Setup -> Add-ons. 

== Configuration ==

After installation in Plone, you'll see '''!DropDown Menu''' item under '''Add-on Configuration''', that include the following setting options:

 [[Image(settings.jpeg, nolink)]]

== Usage ==

quintagroup.dropdownmenu allows to create multilevel portal navigation using CMF Action Category containers. But the requirement is 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, to create the following 3-level portal dropdown menu:

 [[Image(screenshot.jpeg, nolink)]]

 * Go to '''ZMI -> portal_actions -> portal_tabs'''
 * Add '''CMFAction'''s to represent navigation first-level items (ids: folder1, folder2) and '''CMF Action Category'''s to include second-level navigation items (ids: folder1_sub, folder2_sub).

 [[Image(portal-tabs.jpeg, nolink)]]

 * Each '''CMF Action Category''' will include  '''CMFAction'''s - 2nd-level navigation items (ids: subfolder1, subfolder2,..)  and '''CMF Action Category'''s - containers for 3-rd navigation level (ids:  subfolder1_sub, subfolder2_sub,..).

 [[Image(folder1.jpeg, nolink)]]

 * 2-nd level '''CMF Action Category'''s will include '''CMFAction'''s - 3rd-level navigation items (ids: subsubfolder1, subsubfolder2,..)  

 [[Image(subfolder2.jpeg, nolink)]]

You can change items order by using '''Up/Down''' buttons.

== Note ==

Changes you make in portal_actions may not immediately appear in Plone interface right after being done - this is because menu is cached (for an hour). That's why to see your drop down menu at once - go to the RAM Cache control panel (site URL/@@ramcache-controlpanel) and clear cache.

[[Image(ram-cache.jpeg, nolink)]]