Hi,
There was a need in our company to stick the node in the queue to specific position. For example some story should always be on top and not get shifted when you add new item to the queue.
I created a patch to support this functionality. While I was working on it, I made some addition changes, for example when you reorder the queue and the save it we now have just one INSERT query regardless of the number of items in the queue.
Basically the main idea is that you can have multiple sticky nodes in the queue and all new items will be added to non-sticky positions (skip sticky item
and shift other non sticky items).
This functionality makes sense only when you add items on top of the queue (reverse in admin view), so maybe later I can add it only when reverse in admin view is selected.
I will also attach some screenshots to visualize 'stick to position' functionality.
The patch was tested by me and Adding, Saving, Shuffle, Reverse functionality is working properly. I think this functionality could be very useful for publishing websites like us, where editors create and mange queues of content.
Will appreciate any feed back on this.
Thanks
| Comment | File | Size | Author |
|---|---|---|---|
| step2 - new item added and sticky items preserved positions.png | 28.37 KB | gansbrest | |
| step1 - current queue state.png | 24.02 KB | gansbrest | |
| sticky.patch | 11.52 KB | gansbrest |
Comments
Comment #1
mrryanjohnston commentedWas this never integrated due to lack of interest? This could be a very useful feature.
Comment #2
mrryanjohnston commentedI'm working to implement this patch in D7. I'll report back when I'm finished.
Comment #3
mrryanjohnston commentedCreated a new issue here for d7 version of this patch: #1351044: Sticky Nodes
Comment #4
amateescu commentedI posted my thoughts on this 'sticky' functionality in #1351044: Sticky Nodes.
As a separate review of the patch from this issue, please do not include extra functionality in the same patch as it makes it harder to review. If the improvements are small and don't need a separate issue, please open a new issue with small patches that clearly describe each change (like this issue, for example: #1317748: Align views field handlers with changing views api).