[1154] | 1 | Introduction |
---|
| 2 | ============ |
---|
| 3 | |
---|
[1157] | 4 | This package allows Plone websites display multilevel portal dropdown menu based |
---|
| 5 | on portal actions settings and site structure. |
---|
[1154] | 6 | |
---|
[1173] | 7 | You may ask why we may need one more dropdown menu product for Plone, having |
---|
| 8 | already qPloneDropDownMenu, webcouturier.dropdownmenu and other products |
---|
[1158] | 9 | providing similar functionality. While qPloneDropDownMenu product just displays |
---|
[1173] | 10 | manually edited html code with nested unordered list, webcouturier.dropdownmenu |
---|
[1158] | 11 | went further and is trying to display submenus for each standard portal tab be |
---|
| 12 | it action from portal_actions tool or be it auto generated tab based on content |
---|
| 13 | structure. |
---|
[1157] | 14 | |
---|
[1158] | 15 | But neither of those products use newly introduced portal_actions tool's |
---|
| 16 | feature: nested categories. That's why quintagroup.dropdownmenu package was |
---|
| 17 | introduced. It allows to build multilevel portal dropdown menu based on nested |
---|
| 18 | portal_actions categories inside portal_tab category as well as on portal |
---|
| 19 | content structure. |
---|
| 20 | |
---|
[1179] | 21 | It also allows you to define whether to put content tabs before or after action |
---|
| 22 | tabs, and a bit more... For details see below. |
---|
[1158] | 23 | |
---|
| 24 | |
---|
[1173] | 25 | Requirement |
---|
| 26 | ----------- |
---|
[1157] | 27 | |
---|
| 28 | Plone 3.0+ |
---|
| 29 | |
---|
| 30 | |
---|
[1173] | 31 | Installation |
---|
| 32 | ------------ |
---|
[1157] | 33 | |
---|
| 34 | * first follow instructions inside docs/INSTALL.txt document |
---|
| 35 | |
---|
[1173] | 36 | * then install product with Quick Installer in Plone |
---|
[1157] | 37 | |
---|
| 38 | |
---|
| 39 | Migration from qPloneDropDownMenu |
---|
| 40 | --------------------------------- |
---|
| 41 | |
---|
[1179] | 42 | In case qPloneDropDownMenu product was previously installed, it will |
---|
| 43 | automatically detect legacy settings, migrate it to a newly created settings |
---|
| 44 | registry and update portal_actions tool if required along with removing old |
---|
| 45 | portal_dropdownmenu one. |
---|
[1157] | 46 | |
---|
| 47 | Also installation procedure will uninstall qPloneDropDownMenu product itself |
---|
| 48 | (in case it's still installed) and clean up everything after it. |
---|
| 49 | |
---|
| 50 | Note: to successfully migrate old tabs it's required to have a valid html |
---|
| 51 | markup, otherwise migration procedure won't be able to move tabs correctly. |
---|