Nodequeue integration
| Project: | Domain Access |
| Version: | 6.x-2.0-rc6 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | awolfey |
| Status: | closed |
Here's a little module that integrates DA with nodequeue. Nodequeue provides each node with a tab where users can assign that node to a queue. Queues are displayed in blocks provided by NQ or by Views.
This module provides a tab for each active domain so users can see the queues as being separated by domain, even though each queue really can contain nodes from multiple domains.
The use case for this is for multiple domains sharing a similar theme with views filtered by nodequeue AND domain. It simplifies the management process of moving nodes across various domains and queues.
The module also makes a few improvements to the standard nodequeue tab.
- You can configure the column labels to make sense for your site admins.
- The node titles are listed (no. of titles is configurable) in the tabs so it's easier to see what you're moving, and what is already in all the queues.
- The titles link not to the nodes' view tabs, but to the nodequeue tab for the same domain, so you save a few clicks and refreshes as you rearrange your queues.
I started making this as just a nodequeue sub module, so it's currently named nodequeue_tab. I would rename it if people feel there is enough of need for this to contribute it. Nearly all the code comes directly from the nodequeue module.
One more feature I would like to add is the ability to publish/unpublish a node to a domain from the tabs.
Feedback is appreciated.
| Attachment | Size |
|---|---|
| nodequeue_tab.tar_.gz | 3.21 KB |
#1
Interesting. I wish I had time to review.
#2
Here is an update with the following improvements:
- Option of preventing adding nodes to a queue if the node is unpublished and/or is not in that tab's domain.
- Option of included (or not) nodes published to the base domain in other domains' tabs.
#3
Subscribing, interesting, if I have time next week, will try it out.
greetings,
Martijn
#4
Interesting. Do you need this now that, with RC8, you can restrict views by domain?
I can see why you might in a UI...
#5
I think we do. The site editors need to see what is displaying in the various domains' front pages. A lot of it is UI. The nodequeue UI is not very friendly. This lets them easily move stories around, not only from queue to queue but also within a queue.
Nodes are not visible on the front page until they go into a queue.
Views blocks on the front page have a required relationship to a particular queue filtered by "visible in current domain."
A couple of screen shots are attached.
Add and remove from queue use ajax, and the node titles take you that node's domain tab retaining the same domain.
#6
Oooooo. Looks sexy.
#7
This needs to be released as a separate project.
#8
Instead of with domain bonus pack?
#9
Sorry, is it in DBP? That's fine. I just mean "separate from the code I maintain."
I will add DNQ to the home page. Issues should be filed against DBP.
http://drupal.org/project/domain_bonus
Hooray!
#10
Sounds good. It's on my list for next week if I'm lucky.
#11
This has been committed to http://drupal.org/project/domain_bonus.
#12
Automatically closed -- issue fixed for 2 weeks with no activity.