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.
I'm more or less duplicating this issue from Drupal 7 to Drupal 8.
https://www.drupal.org/project/nodeorder/issues/590622
We need to get this fixed in the D8 version, but I'm not sure how actively maintained this module is now.
Comments
Comment #2
joelstein CreditAttribution: joelstein commentedI solved this by using the "Content with term" relationship and then patching core with #2674832-3: "Content with term" views relationship not working due to wrong base table.
Comment #3
lubwn CreditAttribution: lubwn commentedAny progress in this? I am pretty much stuck. My view is easy but adding nodeorder sort filter just triples all the results. When I use aggregation I am able to reduce the number of duplicates or completelly eliminate them, but they are not ordered right as they should be. I kind of do not understand why nodeorder module does not take any arguments. Maybe adding token / relationship to noderorder would solve this problem?
Comment #4
lubwn CreditAttribution: lubwn commentedThere is no other workaround currently as follows. Write your custom module and in .module file add:
You need to replace node__field_druh_materialu.field_druh_materialu_target_id with a field used in node to reference a taxonomy. So for example im my case the field was "field_druh_materialu" which is a taxonomy reference field added to node content type.
Comment #5
xpersonas CreditAttribution: xpersonas commentedIs this still an issue? I'm having trouble reproducing it now. Maybe I'm not understanding how the view is set up. Happy to look at it with more specific steps to reproduce.
Comment #6
xpersonas CreditAttribution: xpersonas commented