1 | Introduction |
---|
2 | ============ |
---|
3 | |
---|
4 | This package allows Plone websites display multilevel portal dropdown menu based |
---|
5 | on portal actions settings and site structure. |
---|
6 | |
---|
7 | You may ask why we may need one more dropdown menu product for Plone, having |
---|
8 | already qPloneDropDownMenu, webcouturier.dropdownmenu and other products |
---|
9 | providing similar functionality. While qPloneDropDownMenu product just displays |
---|
10 | manually edited html code with nested unordered list, webcouturier.dropdownmenu |
---|
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. |
---|
14 | |
---|
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 based on portal |
---|
19 | content structure. |
---|
20 | |
---|
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. |
---|
23 | |
---|
24 | |
---|
25 | Notes |
---|
26 | ----- |
---|
27 | |
---|
28 | * you may have actions/content-based tabs as deep as you wish, but then you'll |
---|
29 | need to tweek default dropdown menu css rules a bit, default css rules show |
---|
30 | only the first 4 levels of tabs |
---|
31 | |
---|
32 | Requirement |
---|
33 | ----------- |
---|
34 | |
---|
35 | Plone 3.0+ |
---|
36 | |
---|
37 | |
---|
38 | Installation |
---|
39 | ------------ |
---|
40 | |
---|
41 | * first follow instructions inside docs/INSTALL.txt document |
---|
42 | |
---|
43 | * then install product with Quick Installer in Plone |
---|
44 | |
---|
45 | |
---|
46 | Migration from qPloneDropDownMenu |
---|
47 | --------------------------------- |
---|
48 | |
---|
49 | In case qPloneDropDownMenu product was previously installed, it will |
---|
50 | automatically detect legacy settings, migrate it to a newly created settings |
---|
51 | registry and update portal_actions tool if required along with removing old |
---|
52 | portal_dropdownmenu one. |
---|
53 | |
---|
54 | Also installation procedure will uninstall qPloneDropDownMenu product itself |
---|
55 | (in case it's still installed) and clean up everything after it. |
---|
56 | |
---|
57 | Note: to successfully migrate old tabs it's required to have a valid html |
---|
58 | markup, otherwise migration procedure won't be able to move tabs correctly. |
---|