Let's say there are 1000 nodes in a given term and we want to order them. We'll probably only be interested in a small subset of the nodes, so there should be a way of filtering the list while still allowing the drag-and-drop ordering to work.

This may be a bit more difficult in 6.x now that weight_in_tid goes from 1 to N where N is the number of nodes in a tid.

Comments

pvanderspek’s picture

pvanderspek commented

Filtering is an idea, but I definitely think paging should also be introduced.

pvanderspek’s picture

pvanderspek commented

Paging shouldn't be much of problem, but filtering is a bit more tricky. What kind of criteria would you want to use? Node titles, node types, weights?

yingtho’s picture

yingtho commented

I would like node type as a criteria. Alternatively you could provide a hook in nodeorder_select_nodes where other modules could provide with additional where clause.

okokokok’s picture

okokokok commented

I'm interested in this. I only need the ordering for a specific node type, but the taxonomy is used for a few other node types.

hikey’s picture

hikey commented

Subscribing. I'm interested in a solution as well. I'm using one vocabulary for several node types but the view to be sorted contains just some of them. Sorting works well (BTW: many thanks for a great module!). Still, most nodes listed on the nodeorder page are not part of the view, which renders the task of ordering really difficult.