Another gem from IRC conversation with merlinofchaos. I wanted a way to hide the "max in queue" column on the nodequeue tab off of nodes, since on my site, none of my queues have a limit, and this column just takes up spaces and confuses the matter. Obviously, on sites that use the limit, it's a killer feature, and the existing UI is just fine. However, if you're not using it, it'd be nice to hide it without having to hack your own copy of the module or override the tab completely via hook_menu() or something.
While we're at it, merlin suggested we add another setting to provide the label used on the "node queue" tab itself. Each site should have a simple way to change that, since the current tab name doesn't mean much to most site admins.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | nodequeue_admin_settings.patch.txt | 4.9 KB | dww |
| #1 | nodequeue_admin_settings_UI.png | 100.32 KB | dww |
Comments
Comment #1
dwwFirst pass at this, which does the following:
- Adds the settings tab at admin/content/nodequeue/settings.
- Checkbox to control if the nodequeue tab should be created at all.
- Checkbox to control if the nodequeue tab should have the "Max nodes" column.
- Text area for the 'nodequeue_tab_name' setting. I see that's already honored in nodequeue_menu() when generating the tab, there was just no UI to set it. ;) Now there is.
I was thinking of getting fancy with a little jQuery to hide the other 2 settings if you uncheck the "Create a menu tab..." box, but I figured I should keep this relatively simple for now. I tested with/without the max nodes column, and the existing nodequeue.css rules for the tab seem to still work ok for me. YMMV, I suppose. I couldn't think of a clean way to conditionally specify the width on those classes based on this drupal setting, and using different classes seemed evil, so I just left it all alone.
Attached is a screenshot of the settings tab provided by this patch, for quick reference and UI feedback (e.g. titles, descriptions, etc).
Comment #2
merlinofchaos commentedCommitted! Great work, dww!
Comment #3
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.