Sort Menu Items in alphabetical order

Bug #484502 reported by Gavin Treadgold
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Sahana Agasti
Won't Fix
Wishlist
Unassigned
Sahana RELIEF Experiments
New
Undecided
Unassigned

Bug Description

Until such time as we can introduce a more flexible and structured menu system, it would be useful to have the main menu items sorted alphabetically to make modules easy to find by name. In the meantime they appear to be sorted in a random order and it can be difficult to search for modules. In addition, the unsorted list looks slightly messy when demonstrating to potential end users.

Tags: core ui
Revision history for this message
dot dot dot (dotdotdotdeactivated-deactivatedaccount) wrote :

The menu items are sorted by the order in which they are specified by the module designers/coders. It's part of the conf.inc in each module to specify its menu order. This is not a bug.

Changed in sahana-relief-experiments:
status: New → Invalid
Changed in sahana-agasti:
status: New → Invalid
importance: Undecided → Low
Revision history for this message
Gavin Treadgold (gt) wrote :

It is a bug that menu orders are hard-coded into conf files. It should be possible (longer term) to have the admin determine menu order through the UI. Hard coded menu positions are poor practice, and existing modules have been copying and duplication the same order number, so the current system is in effect broken. The administrator should have full control over where the module lies in the menu, NOT the module developer.

Changed in sahana-agasti:
status: Invalid → New
Changed in sahana-relief-experiments:
status: Invalid → New
Revision history for this message
dot dot dot (dotdotdotdeactivated-deactivatedaccount) wrote :

I hate to argue semantics, but this is more of a design flaw than a bug. The original specification as part of the framework dictated that they should be handled in the module conf files and they ARE in fact handled as such. Thus, as the expected behavior does not deviate from the design specification, this is not a bug.

Now, more along the lines of whether I think this was a good design choice to include in the specification?... I certainly do not. I agree that they should be handled in the manner in which you describe. I however would call this a feature request at this point as we need to be recode the framework/modules to handle this proposed behavior.

Changed in sahana-agasti:
importance: Low → Wishlist
Changed in sahana-agasti:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.