Currently, the queues appear in whatever order in the nodequeue tab. This is confusing to our site editors.

If possible, it would be great if there was a way to re-order the queues so that similar queues could be grouped together.

Comments

ezra-g’s picture

ezra-g commented

Thanks for the suggestion.

This is interesting but introduces some complications. For example, would the order be on a per-user basis, or sitewide? I suppose the Core drag + drop/weight interface could take care of this, and also account for different users having access to different queues. I'd review a patch for this.

firebus’s picture

firebus commented

+1

It should be sitewide! I have bizarre and complicated use case that would benefit from this.

I've got a site that uses panels to include a view. The view has a nodequeue:subqueue relationship and a subqueue reference argument.

The panels page is configured to pass the subqueue reference argument over to the view, which then displays a navigation menu of nodes in the subqueue

What happens if a node happens to belong to more than one queue? Panels passes the subqueue reference for the nodequeue with the lowest qid. Which is not always the queue you want.

Allowing queues to have weights would make it possible to indicate which subqueue should be passed to the view in the case that a given node belongs to more than one queue.