Order view results according to the order of the node references in the parent node.

This might be a neater way to do it:
http://www.eggheadcafe.com/conversation.aspx?messageid=31792141&threadid...

could add a sort order that picks up the nid argument.

I second that request. Views uses standard order to display a list of nodes. Since mutliple items of a node reference field can be reordered with drag and drop it would be nice to represent this order given by author to views display.

Have a look at the screenshots and the order of titles used.

cheers, Ronald

Adamo, thanks fpr this snippet, works great!

cheers, Ronald

Hello Ronald and all,

I ran over exactly the same problem: so it would be great to get this snippet to work for my folk music website, for user generated tunebooks like http://archive.folx.org/node/849

But how and where do I apply it?

Thanks a lot in advance!
Stephan

Hi stephan,

most drupal sites use their own mini module to override functions used elsewhere. Have a look at http://drupal.org/node/70903
Google for custom or mini module, build your own, paste the lines above into the module and enable it.

Hope this helps, Ronald

Hi Ronald,

needed a while to figure it out, but works perfectly now.

Thanks a lot!

Stephan

Works like a charm, thx guys.

Here some pointers for some other noobs like me:
- make sure you replace modulename in function modulename_views_pre_render(&$view) with the name you have chosen
- make sure to replace the 'field_name' in ($view->name == 'field_name') with the name of your view (which must be equal to the filed name of the noderef CCK field
- leave out the closing ?>

cheers,
Martin

handy snippet, adamo.

another vote for getting this included in the module.

Hmmm..... I really don't like code that has to run on every view and check the view name.
Also, in the module (as opposed to your site's code), how would we know which view name to check? We'd have to load all CCK fields and ask which ones are noderefs and which of those have their formatter set to show a view. That's a lot of stuff to do on every single view even if it's totally irrelevant -- which feels like too much over an imposition to me.

Any better ideas?

> Perhaps you could implement a dummy sort handler and not alter the query at all, and then in hook_views_pre_render() check if that sort handler has been added to the view, and if so sort the results as above.

That's quite possibly a cunning plan!
I don't have time to work on this right now, so feel free to beat me to it :)

Hi,

Any news regarding this issue?

Cheers
Zap

I'm afraid this is very low down on my list of priorities. I am very busy with paid work, so have little time to work on modules in my own time. I will however review patches posted here, and I will try do so fairly promptly. If you need this feature urgently, you can always contact me about paid work :)

Use this view to order the node reference by delta from parent node. No hook or custom module is needed.
This view is for Node reference views 6.x-1.2

$view = new view;
$view->name = 'field_node_ref';
$view->description = 'Clone this field as a starting point for your nodereference view, and give the new view the same name as your field.';
$view->tag = '';
$view->view_php = '';
$view->base_table = 'node';
$view->is_cacheable = FALSE;
$view->api_version = 2;
$view->disabled = FALSE; /* Edit this to true to make a default view disabled initially */
$handler = $view->new_display('default', 'Defaults', 'default');
$handler->override_option('relationships', array(
  'field_node_ref_nid' => array(
    'label' => 'Node-Ref',
    'required' => 1,
    'delta' => '-1',
    'id' => 'field_node_ref_nid',
    'table' => 'node_data_field_node_ref',
    'field' => 'field_node_ref_nid',
    'relationship' => 'none',
  ),
));
$handler->override_option('fields', array(
  'title' => array(
    'label' => 'Title',
    'alter' => array(
      'alter_text' => 0,
      'text' => '',
      'make_link' => 0,
      'path' => '',
      'link_class' => '',
      'alt' => '',
      'prefix' => '',
      'suffix' => '',
      'target' => '',
      'help' => '',
      'trim' => 0,
      'max_length' => '',
      'word_boundary' => 1,
      'ellipsis' => 1,
      'strip_tags' => 0,
      'html' => 0,
    ),
    'empty' => '',
    'hide_empty' => 0,
    'empty_zero' => 0,
    'link_to_node' => 0,
    'exclude' => 0,
    'id' => 'title',
    'table' => 'node',
    'field' => 'title',
    'relationship' => 'field_node_ref_nid',
  ),
  'delta' => array(
    'label' => 'Node-Ref (field_node_ref) - delta',
    'alter' => array(
      'alter_text' => 0,
      'text' => '',
      'make_link' => 0,
      'path' => '',
      'link_class' => '',
      'alt' => '',
      'prefix' => '',
      'suffix' => '',
      'target' => '',
      'help' => '',
      'trim' => 0,
      'max_length' => '',
      'word_boundary' => 1,
      'ellipsis' => 1,
      'strip_tags' => 0,
      'html' => 0,
    ),
    'empty' => '',
    'hide_empty' => 0,
    'empty_zero' => 0,
    'set_precision' => FALSE,
    'precision' => 0,
    'decimal' => '.',
    'separator' => ',',
    'prefix' => '',
    'suffix' => '',
    'exclude' => 0,
    'id' => 'delta',
    'table' => 'node_data_field_node_ref',
    'field' => 'delta',
    'relationship' => 'none',
  ),
));
$handler->override_option('sorts', array(
  'delta' => array(
    'order' => 'ASC',
    'id' => 'delta',
    'table' => 'node_data_field_node_ref',
    'field' => 'delta',
    'relationship' => 'none',
  ),
));
$handler->override_option('arguments', array(
  'null' => array(
    'default_action' => 'ignore',
    'style_plugin' => 'default_summary',
    'style_options' => array(),
    'wildcard' => 'all',
    'wildcard_substitution' => 'All',
    'title' => '',
    'breadcrumb' => '',
    'default_argument_type' => 'fixed',
    'default_argument' => '',
    'validate_type' => 'none',
    'validate_fail' => 'not found',
    'must_not_be' => 0,
    'id' => 'null',
    'table' => 'views',
    'field' => 'null',
    'validate_user_argument_type' => 'uid',
    'validate_user_roles' => array(
      '2' => 0,
    ),
    'relationship' => 'none',
    'default_options_div_prefix' => '',
    'default_argument_user' => 0,
    'default_argument_fixed' => '',
    'default_argument_php' => '',
    'validate_argument_node_type' => array(
      'page' => 0,
      'story' => 0,
    ),
    'validate_argument_node_access' => 0,
    'validate_argument_nid_type' => 'nid',
    'validate_argument_vocabulary' => array(),
    'validate_argument_type' => 'tid',
    'validate_argument_transform' => 0,
    'validate_user_restrict_roles' => 0,
    'validate_argument_php' => '',
  ),
  'nid' => array(
    'default_action' => 'ignore',
    'style_plugin' => 'default_summary',
    'style_options' => array(),
    'wildcard' => 'all',
    'wildcard_substitution' => 'All',
    'title' => '',
    'breadcrumb' => '',
    'default_argument_type' => 'fixed',
    'default_argument' => '',
    'validate_type' => 'none',
    'validate_fail' => 'not found',
    'break_phrase' => 0,
    'not' => 0,
    'id' => 'nid',
    'table' => 'node',
    'field' => 'nid',
    'validate_user_argument_type' => 'uid',
    'validate_user_roles' => array(
      '2' => 0,
    ),
    'relationship' => 'none',
    'default_options_div_prefix' => '',
    'default_argument_user' => 0,
    'default_argument_fixed' => '',
    'default_argument_php' => '',
    'validate_argument_node_type' => array(
      'page' => 0,
      'story' => 0,
    ),
    'validate_argument_node_access' => 0,
    'validate_argument_nid_type' => 'nid',
    'validate_argument_vocabulary' => array(),
    'validate_argument_type' => 'tid',
    'validate_argument_transform' => 0,
    'validate_user_restrict_roles' => 0,
    'validate_argument_php' => '',
  ),
));
$handler->override_option('access', array(
  'type' => 'none',
));
$handler->override_option('cache', array(
  'type' => 'none',
));
$handler->override_option('items_per_page', 0);
$handler->override_option('style_plugin', 'list');
$handler->override_option('style_options', array(
  'grouping' => '',
  'type' => 'ul',
));

Cool!

This seems to depend on a recent version of CCK, as with whatever version I initially had on my test site I got an error.

Furthermore, I can't add this to the default example view, as the sort handler's table is named after the CCK nodeference field. So it's going to have to be an extra note in the documentation.

This view has a different approach than the current default view. The first argument (all referenced nids are completely ignored). This views is build on the second argument (the source nid). Than we use a relationshop to get all referenced nodes and order these nodes by the fields-delta.

(sry for my bad english)

If you read the source code of the module, you'll see I tried this approach and discarded it:

// This is an alternative approach: send just the nid and requery.
// this requires a view with:
// - a relationship on the CCK noderef field,
// - an argument of node ID
// - fields for actual display set on the noderef relationship
// It's more complex to set up, seems wasteful as CCK has given us the nids already
// and in testing (admittedly with a tiny data set)
// was about the same speed, marginally slower in fact.

Your sort works on the existing view -- but in both cases, it can't be provided in the default example view because it depends on the name of the user-created field.

Yes i know, i read the source code. But i think there is no way to use the referenced nids and order these by field delta ...

Oh, you're right. Sorry -- I thought it was working with the current view and it's not.

The really cool and awesome thing would be to write a smart relationship handler that depends on the name of the view... which I don't have time to do.

In the meantime, we can add the details of how to do it with the relationship to the documentation.

@webflo
fantastic.
the view wouldnt import until i did a find-and-replace from field_node_ref to field_my_field. it kept saying handler for field_node_ref not found.
thanks

the view works very well, thanks

I ran into this issue as well, and it's a real showstopper in some use cases; if there's no "logical" sorting order, this is a real problem; if the 'Node reference views' view can be given a sorting order, that's a workaround in other cases since 'Node reference views' honors the view's sorting order.

Confirming that the exported view from #15 can not be imported if not manually altered (#21). Error message (sorry, localized Drupal):

Die Feld-Behandlungsroutine node_data_field_node_ref.delta ist nicht verfügbar.
Die Ansicht konnte nicht importiert werden.

This message complains that 'node_data_field_node_ref.delta' does not exist.

Used versions:

• Views 6.x-2.10
• Node reference views 6.x-1.2

Doing a S&R on 'field_node_ref' with the actual field name replaces 9 strings and produces an export that is valid (#21) and works as advertised.

Does anyone volunteer to write a how to for the documentation (#20)?

Greetings, -asb

hi everyone

i imported your view and worked great until i referenced one node twice from different parent nodes. the results are duplicate results.

any ideas?

Thank you for this excellent solution!

Subscribing. Thanks much to webflo and asb. An excellent solution!

I dug into this. What happens is that Views gets passed the arguments, which runs a query like this:

SELECT
  [fields]
FROM
  [tables]
WHERE
  uid IN (uid1, uid2, uid3)

The difficulty is telling it how to order those results.

Luckily there are two modules worth trying:

• Views Argument Sort which has been discontinued in favor of..
• Views Arguments Extra, which only has an alpha release so far.

FYI, lots of good suggestions, if you want to work on it some more: http://stackoverflow.com/questions/866465/sql-order-by-the-in-value-list

Thanks for the initial snippet! It solved both the order problem AND some strange caching problem. If I made changes to the parent node, they weren't immediately visible when the page was refreshed. This was in dev mode with caching disabled globally. Thanks for the "enhancement"!

Closing, as this module is now deprecated.

See #1257780: Sort Order Based on Delta for the issue on the replacement module.