Loading...
 
Skip to main content

Features / Usability

Forum List Topic List

Forums » Features / Usability » Menu sections not working as expected
 
Thread actions
Print this page
  • Print all pages

    • Menu sections not working as expected

    Posted by Steve posts: 40 United States

    Hello All,

    I am building a custom menu and would like to add some collapsible sections. Am I limited only to using preexisting sections associated to preexisting features? That is what I am drawing from the documentation. I would like to just have a collapsible section that serves no function other than to organize my subitems. As an example, I want to create a list of members managing a nonprofit group under a section called "GroupMembers" that I would then use for options with a URL entry like "tiki-index.php?page=bioHaroldHecubah" using the same "GroupMembers" section name. Every time I try this absolutely nothing shows up in the menu related to the member bios, not even the section header.

    So, I guess my question boils down to, "Do I need to somehow register section names before using them?"

    Any thoughts, suggestions or constructive comments would be appreciated.

    Steve

    Reads: 1214
    Posted by Gary Cunningham-Lee posts: 4664 Japan

    Nothing in particular is required for menu items. They can be links to any page, or whatever. But their form has to be right for them to show up. Be sure wiki pages have "feature_wiki" input in the "Sections" box of the new-item form.

    The word "section" is confusing because it's used for more than one thing, related to menus. As a label for a menu item, "section" means a (formerly top-level) item that can contain "children," which are called "options" when making up a menu. (Now — as of 1.9.8 — that we have multi-level menus, there are new section levels, indicated by number. A section1 item is a "parent" that is a child of a section0 item.) These items can have any name and can link to anything, but . . .

    . . . what goes in each one's "Sections" box in the form must match up with a Tiki feature, which is confusingly referred to as a section, also. This second use of the term "section" is in reference to such parts of the Tiki site as "feature_wiki," "feature_blogs," etc. See how the default menu is specified to get an idea of what is input as sections.

    -- Gary

    Posted by Steve posts: 40 United States

    > Nothing in particular is required for menu items. They can be links to any page, or whatever. But their form has to be right for them to show up. Be sure wiki pages have "feature_wiki" input in the "Sections" box of the new-item form.
    >
    > The word "section" is confusing because it's used for more than one thing, related to menus. As a label for a menu item, "section" means a (formerly top-level) item that can contain "children," which are called "options" when making up a menu. (Now — as of 1.9.8 — that we have multi-level menus, there are new section levels, indicated by number. A section1 item is a "parent" that is a child of a section0 item.) These items can have any name and can link to anything, but . . .
    >
    > . . . what goes in each one's "Sections" box in the form must match up with a Tiki feature, which is confusingly referred to as a section, also. This second use of the term "section" is in reference to such parts of the Tiki site as "feature_wiki," "feature_blogs," etc. See how the default menu is specified to get an idea of what is input as sections.
    >
    > — Gary


    Thank you for the detailed reply Gary. I am going to take this as confirmation that the theory is sound, but that my intended use strategy of the "section" field is incorrect and that I must tie this submenu to a feature, preferably in this case, the feature_wiki section keyword.

    Again, thanks for the quick reply. It's always good to have a little validation when venturing into new territory.

    Steve