Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By nitrospectide on
I have a Draggable Views use case in which:
I am sorting the nodes of a particular content type.
I have multiple sorting view displays (each view filtering for a particular category based on an entity ref) example: these nodes are part of the "Heating" category, and these others are part of the "Hand Tools" category based on a ref to a Heating or Hand Tools node of another content type.
Each of the sorting views appears to work properly, and shows only the nodes of that category, and retains the re-ordering of items after saving.
On the front end side, I have two view displays: one for Heating, and another that handles everything else. This is just because of a peculiarity on the Heating one, otherwise, they'd all go through a single view. Each uses a Relationship and Contextual filter to narrow the nodes it displays to only the ones that reference the category node the block is currently being viewed on.
When I re-order the Heating nodes in the sorting view, the sorting view retains their new order, and the front end view properly shows the new ordering of items.
THE PROBLEM: When I re-order nodes in any of the other sorting views for other categories, they retain the new sorting when I save, but when I go to the shared front end view, their order is unaffected. Why?
