Active
Project:
Settings Menu Link
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
18 Dec 2011 at 20:39 UTC
Updated:
19 Dec 2011 at 06:44 UTC
This module sounds promising.
However, I don't understand why I should create a new menu item.
- If I create a new item, does it always generate a settings page?
- Can I also use it as a normal menu? (So, first create a settings page item, then move subitems from existing 'old-style' menu item to new item.)
It would be nice if I can edit a normal menu item, and set that as settings-page-relevant, perhaps with a new path.
This way, you can use the menu-item+sub-items both normally, and as a settings page (like a mega-menu, or like a reversed administration menu, which takes the settings page, and turns it into a normal menu.)
Comments
Comment #1
frans commentedSounds like a lack of documentation ;) Patches welcome!
Basicly it is a new menu item type. That new type works exactly like a normal menu item.
Yes and no... Yes when you use the 'Add settings link' link to create an item. No when you use the normal, existing 'Add link' (and No when menu items are controlled by other modules, such as node module or the views module)
Yes, in that sense it is a normal menu item. I removed the expanded option, but further more it is exaclyt the same as a menu item.
I am afraid, I don't get what you say... I think it works exaclty like you describe... but since you ask the question, I think I don't get the point...
Tnx for the feedback, try it out... it is simple and elegant. Comments welcome!
Comment #2
johnvThanks for your quick reply.
My last point is answered with your reply.
It is just that it feels more safe if this module adds an extra option to an existing item. My fear is: what happens with my menu item if it is happily living amidst all other menus/items, and I decide to disable this module? Will it behave like a normal menu? will it be lost?
Perhaps it is just a UI issue: a new checkbox 'use as menu settings page' seems a bit safer then the current situation.
(Especially it seems like merely a nice feature (to me at least), and not an 'important' one like Taxonomy menu...)
Comment #3
frans commentedNot tested, but I am sure that the menu item will still exist when you remove the module. But it is useless... it points to a path with no page. You will probably have no UI anymore to edit/delete the item.
Didn't thought this case through, but I have a feeling that this is an edge case. First of all why do you want to remove modules that you are using? I understand that that happens, but then second: when you put the module back, make changes to your menu and then uninstall it again, the problem is solved.
To me this sounds like "I cannot use views when I uninstall views"
It might be a good idea to transform the menu items to 'normal' menu items when the module is uninstalled?
Comment #4
johnv(Ah, we kunnen ook Nederlands praten..)
Sometimes you just want to reduce the number of enabled modules, (due to memory problems, etc?)
Think of it as a widget: I might have enabled 10 widgets, and want to reduce the number of enbled modules. A field using an disabled widget should fall back to a default one.
I still prefer an add-on (=option) to the menu item .. :-)
Groeten
Comment #5
frans commentedAs said, I understand that sometimes you want to disable or remove modules...
To be honest ... I had my doubts about releasing this as contrib, because the functionality is rather specific. But while I was building my 100st settings page custom module, I had the feeling that, when generalized a little more, this could be useful for the 101st time. That is what this module is.
When I build this as a widget, it would be as heavy (or light) as the current implementation. I then have the same issue with removal of the module, the UI would simply disappear for edit/delete. It just comes down to preferences of UI. I am for sure no UI guru, but I don't like the over bloated edit forms, with a gazillion options for one menu item..
Kortom not gonna fix ;) But I am considering the option for transforming to normal menu items on uninstall. One of the issues i have with that, is that there is no way back, when you re-install the module, the menu items will still be normal menu items.
Comment #6
johnvYep, I understand.. (That would not happen with an option-field :-) )
let me just test your module for a while.
I'll be back!
Let's leave this issu eopen, perhaps someone else has better ideas (or even a patch)
Comment #7
frans commentedIt would happen with an option field, unless you keep track of the menu items in a seperate table.
And that is exactly how it is designed. The menu items act like they do, just because this module is responsible for them. It does not need extra tables now, and i like to keep it that way.
I just think that a seperate add link is cleaner, but I am willling to listen to UI gurus.
Comment #8
frans commentedDouble post... 3G to the max!