Old position of a node inside the queue (position before saving the queue with new order of nodes) would be very usable data. Using that number, nodequeue could be for example used for displaying music charts where last week's entry is usually displayed next to the current position.

Comments

ezra-g’s picture

ezra-g commented
Title: nodequeue history » Queue Revisions
Component: User interface » Code

What you're describing sounds like queue revisions. This could be achieved by storing nid, qid\sqid and queue_vid information. The revision of the queue would have to be changed each time the queue was re-ordered and old node position values would be stored either in the current table or possibly another queue_revisions table. This would likely create a lot of extra values in the database. Perhaps there could be a configurable limit, "Store x number of revisions to a queue."

I wonder what Merlinofchaos thinks about this.

amateescu’s picture

amateescu commented
Status: Active » Closed (duplicate)

This would be a very nice feature. We should take it into consideration in #461826: Generalize to entities.

Closing as a duplicate in lack of a better status, and posted a note about it in the issue above.