Synchronize queue
| Project: | Nodequeue |
| Version: | 5.x-2.0-rc3 |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Greetings:
I am planning to use nodequeue to manage the nodes that comes in frontpage. I am currently using taxonmy for that but I need more flexibility for ordering and want to separate node editing from node organisation. So nodequeue is the perfect candidate for that.
But I want to work with 2 queue : one (call it "pre") will be for the editors. They add the node to this queue, re-ordered them, check that everything is like they want, etc. The resulting page of this queue is visible only by the editors. The other one ("home") is visible by everyone and is the real frontpage.
When the editors are happy by what is generated by the "pre" queue, they should be able to sync "home" with "pre". It is important for me that the nodes are not directly added to the "home" queue because the rendering of the nodes are dependent of their position in the queue (the first one is different from the other). Also the first one, should say on top for around half a day, while several other nodes will be added to the queue in the same period.
Ideally the method should synchronize only the differences that are present in the "pre" and "home" queue. I guess that I could easely trash "home" and dump "pre" into it but 1) my queues are infinite (and very long), 2) it would be a mess if a user load this page while the "home" not fully populated.
Do you have any idea of how to do that or any pointers on how to do it ?
Thanks
damien
#1
this would be a useful add-on module. not likely to be part of core nodequeue AFAICT
#2
Ok, I will study the nodequeue API and see what I can do.
#3
I can't think of an efficient way to do this except to dump the queue and then recreate the queue. It's actually fairly efficient to do a mass insert, and it's much less efficient to move positions around and end up performing a lot of queries.