Changes between Version 37 and Version 38 of quintagroup.dropdownmenu


Ignore:
Timestamp:
Jun 5, 2013 2:54:04 PM (11 years ago)
Author:
naomin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • quintagroup.dropdownmenu

    v37 v38  
    33[[PageOutline]] 
    44 
    5 [[Image(quintagroup.dropdownmenu.jpg, nolink)]] 
     5 [[Image(quintagroup.dropdownmenu.jpg, nolink)]] 
    66 
    7 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. 
     7Many sites, even responsive ones, stick to the belief that navigation belongs at the top of any given page. This approach can cause usability problems on mobile devices because mobile users are often short of two things: screen space and time. Quintagroup.dropdownmenu package offers a solution by providing mobile-first multilevel navigation menu. It means the product enables device-native interactive interface for navigating through the website in more accessible way. Smart select box takes up minimum space on mobile phones, while tablet users are presented with a glorious multilevel top menu. 
     8 
     9 [[Image(mobile-navigation.jpeg, nolink)]] 
    810 
    911== Links == 
    … …  
    1517== Introduction == 
    1618 
    17 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. 
    18  
     19This package allows Plone websites to display multilevel drop-down menu based on site content. It also allows to define whether to put content tabs before or after action tabs, and a bit more... For details see below. 
    1920 
    2021== Notes == 
    2122         
    22 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  
     23You may have actions/content-based tabs as deep as you wish, but then you'll need to configure default drop-down menu css rules a bit, default css rules show only the first 4 levels of tabs  
    2324 
    24 == Requirement == 
     25== Compatability == 
    2526 
    26 Plone 3.x, Plone 4.0 
     27Plone 3.x, Plone 4.x 
    2728 
    2829== Migration from [wiki:qPloneDropDownMenu qPloneDropDownMenu] == 
    … …  
    6061}}} 
    6162 
    62 Activate Plone Drop Down Menu via Quickinstaller in Plone: Site Setup -> Add-ons.  
     63Activate Plone Drop-Down Menu via Quickinstaller in Plone: Site Setup -> Add-ons.  
    6364 
    6465== Configuration == 
    … …  
    6869 [[Image(settings.jpeg, nolink)]] 
    6970 
    70 == Usage == 
    7171 
    72 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: 
    73  
    74 {{{ 
    75     action_id = prefix + category_id + suffix 
    76 }}} 
    77  
    78 where: 
    79  
    80  * 'category_id' is id of correspondent CMF Action Category 
    81  * 'prefix' defined in !DropDownMenu configlet, default value -  
    82  * 'suffix' defined in !DropDownMenu configlet, default value - _sub 
    83  
    84 To create the following 3-level portal dropdown menu: 
    85  
    86  [[Image(screenshot.jpeg, nolink)]] 
    87  
    88  * Go to '''ZMI -> portal_actions -> portal_tabs''' 
    89  
    90  * 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). 
    91  
    92  [[Image(portal-tabs.jpeg, nolink)]] 
    93  
    94  * For every '''CMFAction''' you should specify: its '''''Title''''' - as it will be visible in Plone and its '''''URL (Expression)''''' - URL on a site where it will be linked to. URL should be provided in the following format: 
    95  
    96   {{{ 
    97   string:${globals_view/navigationRootUrl}/folder1 
    98   }}} 
    99    
    100  where 'folder1' is id of the folder, located in the site root, to which this tab should be linked.    
    101  
    102  In case you want your tab to be linked to an object inside some folder, you should specify the entire path, for example:  
    103  
    104   {{{ 
    105   string:${globals_view/navigationRootUrl}/folder1/subfolder/page1 
    106   }}} 
    107  
    108  [[Image(action-edit.png, nolink)]] 
    109  
    110  * 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,..). 
    111  
    112  [[Image(folder1.jpeg, nolink)]] 
    113  
    114  * 2-nd level '''CMF Action Category'''s will include '''CMFAction'''s - 3rd-level navigation items (ids: subsubfolder1, subsubfolder2,..)   
    115  
    116  [[Image(subfolder2.jpeg, nolink)]] 
    117  
    118 You can change items order by using '''Up/Down''' buttons. 
    119  
    120 == Note == 
    121  
    122 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. 
    123  
    124 [[Image(ram-cache.jpeg, nolink)]]