I’ve already moved on to work on version 4 so I thought it was time to share this one publicly.
Version 3.1 of my plugin has pretty much the same output as version 2, so ’til I find the time to write a new documentation check the old topic. One of the new things is that you will be in full control of how the menu is sorted through your admin panel. This enables you to sort the menu even by extra data added to the XML-file like the creation date or custom fields.
Download the plugin here.
The plugin should work with any language and in every GetSimple version starting from 2.0.
• • •
Now for the more important part that needs discussing, what features should be included in version 4?
This is the current plan, whenever I talk about “the main menu†I’m referring to the menu generated by menu_master():
*: I would like your opinion about what this feature should look like. How do you want it?
¹: When should the cache be generated? Every time you edit a page? Only when you edit the slug of a page? Maybe even only when you press the cache button? What do you think?
²: Do you think the HTML output of my previous menu plugin was bad? Let me know what you think the HTML of a menu should look like!
Version 3.1 of my plugin has pretty much the same output as version 2, so ’til I find the time to write a new documentation check the old topic. One of the new things is that you will be in full control of how the menu is sorted through your admin panel. This enables you to sort the menu even by extra data added to the XML-file like the creation date or custom fields.
Download the plugin here.
The plugin should work with any language and in every GetSimple version starting from 2.0.
• • •
Now for the more important part that needs discussing, what features should be included in version 4?
This is the current plan, whenever I talk about “the main menu†I’m referring to the menu generated by menu_master():
- Ability to switch sorting order between A-Z and Z-A.
- Menu caching: ¹
- Cache the exact menu HTML.
- Cache the menu data so it can be used by other plugins.
- Cache the exact menu HTML.
- Ability to choose what to do with submenu(s) in the main menu:
- Always render the submenu(s) in the main menu,
- only render the submenu for the active page in the main menu, or
- never render the submenu(s) in the main menu.
- Always render the submenu(s) in the main menu,
- Functions apart from rendering the main menu:
- isParent() — Boolean, true when the current page has children.
- isChild() — Boolean, true when the current page has a parent.
- hasSubmenu() — Boolean, true when the current page has children that are set to show in the menu or when the current page has a parent and is set to show in the menu. *
- submenu_master() — Renders only the menu of the current page’s children, or the menu of the current page’s parent. *
- isParent() — Boolean, true when the current page has children.
- Custom hooks so you can make plugins for my plugin. *
- Translation file so the plugin can be changed for any language.
- Better HTML output. ²
*: I would like your opinion about what this feature should look like. How do you want it?
¹: When should the cache be generated? Every time you edit a page? Only when you edit the slug of a page? Maybe even only when you press the cache button? What do you think?
²: Do you think the HTML output of my previous menu plugin was bad? Let me know what you think the HTML of a menu should look like!
“Don’t forget the important ˚ (not °) on the a,†says the Unicode lover.
Help us test a key change for the core! ¶ Problems with GetSimple? Be sure to enable debug mode!
Help us test a key change for the core! ¶ Problems with GetSimple? Be sure to enable debug mode!