I've been playing with this module and it's working great. This will be driving a good portion of our homepage content.
USABILITY REQUEST: I am a bit concerned with how it handles new posts once the queue is full. It automatically dumps the first post in the queue and appends the new one to the bottom of the list.
In my perfect world there would be an alert letting the admin know the queue is full, with the possibility of choosing which node in the queue will be replaced by the new addition.
Thanks again for a great tool!
Comments
Comment #1
merlinofchaos commentedInteresting request.
Would putting a message on the 'add to queue' page stating that the queue is full be enough? Seeing this message the admin could then go to the queue-admin page and rearrange the queue before adding the new post. That wouldn't require a great deal of coding and would still allow the flexibility you need. Whereas giving the admin an option at the time of adding would create more clicks and more screens; more code and a less crisp interface.
Thoughts?
Comment #2
thinkinkless commentedI like the idea and think it would be a good enhancement.
If I understand corectly this will mean there's someting (ideally in red) next to the add link on the 'node/xxx/nodequeue' page.
The editor will know they are bumping the top post from the queue and can act accordingly.
You may want to include that behavior in the documentation as well. We had to experiment a bit before we realized that was how full queues were handled.
Comment #3
merlinofchaos commentedThis is now in the 4.6 branch. Please leave feedback about the solution; is it enough? For example, I could add some CSS info. I could probably also pull some of the text out into a theme function.
Comment #4
thinkinkless commentedThis is great.
I don't think any more is needed. I'll let you know if anything else comes up. We launch in a week so the admin will be using it a lot. Thanks again for your responsiveness!
This issue is closed.