Great module, Conor!
It would be great though to be able to select only the links you want to use/expose. E.g. on my site I don't use "promote" and "make sticky" functionalities and I don't want to confuse my users. For now I just commented out the lines 250 - 271 in the admin_hover.module, but it would be a nice, complementing feature.
Comments
Comment #1
conortm commentedThanks Michal! Yes, absolutely right. I am working on an admin screen for this module where users with a new perm to 'administer admin_hover' can turn links off and on, and do other things (TBD). So, stay tuned and thanks again!
Comment #2
mkrakowiak commentedFantastic. Looking forward to it. Thanks for the module, Conor.
Comment #3
looplog commentedGreat module - just the kind of usability improvement Drupal needs and its the kind of module that has instantly affected my workflow in a positive way. Whilst I'm keen to wait and see what you'll add, I'll second the request above. I imagine you have all sorts of plans, but I'd love to see one very useful addition - user defined links/actions. By incorporating token support, a user could build their own context dependent actions, effectively creating a toolbar for node actions, centralising and focusing user actions in the process. Another way to achieve this would be to hook into CCK Links and provide an admin:hover formatter for those links which are context sensitive node actions, as CCK Links already has Token support and would reduce the code overhead required by your module. Anyway, I'm no uber-coder, so these are just suggestions from a user-centric perspective.
Thanks again for contributing this module.
Comment #4
conortm commentedMichael (omjn),
Thanks much, glad you like it so far and that has improved your workflow!
The module begins to implement a hook that I hope will (after further development and proper documentation) allow other modules to add their own administrative links to nodes and blocks (and beyond)... So, this is in the works on that front.
However, you raise an interesting point of providing more flexible, user-defined actions... I'll need to have a think on this one, but off the top of my head, i can see an admin wanting to define an Admin:hover link for a specific node type that will take him/her to a View they've configured whose path is built from the node's attributes (nid, uid, tid, etc.)...
I would like to hear more of your thoughts on this (and anyone else who would like to chime in).
Thanks, again, for your feedback and suggestions, and take care.
~conor
Comment #5
looplog commentedSorry I couldn't get back to you earlier. I don't have a lot to add but I'll take you up on one front:
Yes, a similar thing I had in mind was building hierarchical content with Node reference, taxonomy and prepopulate modules in a token defined CCK Link. In fact, this is where I thought token module support would shine, and especially if CCK Links were to have the an Admin:hover formatter as I suggested. The node type links would be defined at the CCK Admin level, using Tokens to build the links in whichever way including in the View with arguments fashion you envisage. This would allow content type administration to be concentrated at the CCK admin level, as should be appropriate, through a single interface, and as many links could be defined as wished. It would also mean you don't have to code anything directly related to Token or link building support - CCK Link does all that already. You can see how flexible this solution is, providing possible actions for any Token related Drupal module function expressible as a URL.
This would require on your behalf the implementation of the hook you stated, possibly provision of a patch to the CCK Link module to provide a formatter utilizing the hook, and then only a simplified admin in the Admin:hover module allowing for selecting and/or reordering of node admin actions. The only thing that doesn't solve is providing the user/admin with an interface for defining the Admin:hover icon for each CCK Link they wish to format as an Admin:hover link, which might be necessarily a part of the Admin:hover configuration interface detailed prior.
I'm not at all sure that I'm articulating this well, and unfortunately I'm still all ideas and no code. Nevertheless, this is how I see it working in an ideal world, where everybody has unlimited time and coding skills. Whatever you ending up producing will be more than appreciated...
Comment #6
conortm commentedPlease check out the latest 5.x dev release of Admin:hover to see "Deselect links you don't want" functionality and leave any feedback here. Once the functionality is moved to an official release, I will close this issue.
omjn, if you would like to continue your feature request, please post another issue. I have begun to explore Token integration. It's in its early stages, so stay tuned. Thanks!
Comment #7
conortm commentedMarked as fixed and switched Version to 5.x-1.x-dev.
Comment #9
mkrakowiak commentedSorry about this late reply, Conor. The new features seem to work fine and integrate well with other modules. Thanks for your work on this module.