Buildmodes not updated when nodes are displayed more than 1 time on the same page

No, no fix yet. I had identified this issue on a production site that I'm working on, but hadn't got around to debugging it yet, as I wasn't sure if it was a localised bug or not. Clearly it isn't, so I'll add it to the queue. Expect a fix at some point...

Correct! and also in Display Suite itself somewhere else. I should have patch for this today which fixes it and preserves caching.

Just thought I would post my effort in debugging:

$node = node_load(array('nid' => 11384), NULL, TRUE);
$node->build_mode = 'teaser';

$teaser = ($node->build_mode != 'full') ? TRUE : FALSE;
$show_links = ds_show_field('nd', $node->type, $node->build_mode, 'links');

$node = node_view($node, $teaser, FALSE, $show_links);
dpm($node);

$node = node_load(array('nid' => 11384), NULL, TRUE);
$node->build_mode = 'featured_article';

$teaser = ($node->build_mode != 'full') ? TRUE : FALSE;
$show_links = ds_show_field('nd', $node->type, $node->build_mode, 'links');

$node = node_view($node, $teaser, FALSE, $show_links);
dpm($node);

The output rendered the exact same teaser node each time. Not really sure what is going on here.

Display Suite & Node Displays are caching the Display by node ID, not by build mode. Hence, you get the same result every time. Patch coming...

I see, yes the following bypasses the issue although I am sure it has some caching ramifications:

/**
 * Statically cached version of ds_build_fields and regions
 */
function nd_build_fields_and_regions(&$node) {
//  static $displays = array();
//
//  if (isset($displays[$node->nid])) {
//    $node = $displays[$node->nid];
//  }
//  else {
    ds_build_fields_and_regions($node, 'nd');
    $displays[$node->nid] = $node;
//  }
}

I will wait for the fix. Thanks for looking at the issue.

The only issue is you lose static caching, which is really only a problem if you reload the node with the same display in two places.

I've committed a fix to dev. If it passes tests tomorrow I'll do a release.

Thanks, it seems to work for me. Good work and nice and simple solution you implemented.

No problem. Thank you.

I updated drupal core to 6.26 and the problem came again :(

@ArielCamino

This issue is fixed and committed, so it is unlikely to be caused by the same issue. Please open a new ticket, with a full description of how to replicate the issue. Thanks.