Closed (cannot reproduce)
Project:
Administration menu
Version:
7.x-3.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
29 Apr 2012 at 16:40 UTC
Updated:
2 Nov 2018 at 21:29 UTC
Jump to comment: Most recent
Comments
Comment #1
sunI like the idea.
However, Views itself does not seem to allow to filter the views by tag; e.g.
admin/structure/views?tag=admin
We'd need something like that in order to make any sense of the injected category parent links (i.e., when grouping all "admin" views below an "admin" views category link, then you'd expect to see the same listing of all "admin" views when clicking on that parent/group/category link).
Comment #2
moniuch commentedI thought that if we can have filter panel above Views list, we could also use it to group menu items. Oh well, then maybe each view could have a "Show in menu" checkbox, or maybe we could have top 10 recently edited... It could be a pref setting.
It's difficult to me to judge which is possible and which should be taken care by Admin Menu authors for example, but definitely if I'm not sure if the View will fit in the screen when reaching out for menu, I always tend to open the overlay first. Thus, the menu seems to be barely useful.
Comment #3
Leagnus commentedsubscribing
Comment #4
truls1502I am sorry for no reply until now.
There are many issues regarding this module admin_menu which is a bit difficult for us to follow up since some of the issues might be already outdated, or is already fixed by the module or any other modules or itself core which means that the problem might no longer need to be fixed.
We can see that the issue has been created for a few years ago, I hope it is okay for you that I am postponing the issue, and give you around two weeks. If you still face the problem, could you tell us the step by step when until you get the error message or what is frustrated you, and a list of modules you are using related to admin_menu and a screenshot that might help us? So it makes us easier to reproduce your issue.
However, after two weeks with no feedback - we will close this issue. So in case, you noticed it after the issue is closed, do not hesitate to reopen it like and fill information which is mentioned above.
So before giving us a feedback, do you mind to test it again with our latest 7.x-3.x-dev?
Thank you for understanding! :)
Comment #5
truls1502This issue has been automatically marked as closed because it has not had recent activity after the last post.
However, if you or someone is still facing the same issue as described to the issue, could you please to re-open the issue by changing the status of the issue, and add an explanation with more details which can help us to reproduce your situation.
Again, thank you for your contributions! :)