I realize that this has been discussed earlier (http://drupal.org/node/62720), but seemingly 'nodequeue as node' -feature didn't get into 2.0 release of Node Queue - am I right? I'm developing a site in which NodeQueue is used to make possible to editors collect arbitrary content to various collections. Now I'm seeking a way to be able to make a list of those collections eg. display their titles, possibly with some kind of teaser text, etc. much like in Nodequeue administration page. With Views this would be a piece of cake, but unless I have been understood something wrong, currently is it not possible to make a list of nodequeues with Views because nodequeues are not proper nodes. Is there any other way to do this, eg. make a list of nodequeues?

Comments

merlinofchaos’s picture

Status: Active » Closed (won't fix)

You are correct; this is currently not possible and the current design makes nodequeue-as-node unwieldy.

The best thing you could do would be to write a small wrapper module that associates a nodequeue with a node, and then you could use your Views. But this isn't something I am likely to work on.

yched’s picture

A nodequeue_reference field for CCK could have its uses - and would probably not be that hard to do (not that I'm volunteering for that, just throwing the idea in the air :-) )

mjlassila’s picture

Okay, thanks. I created an quick-and-dirty workaround using custom nodetype and a cck viewfield in it which references to matching nodequeue view.

internetdevels’s picture

subscribe

skitten’s picture

You want to make a view of subqueus?

This is possible by having your module alter the views data to make nodequeue_subqueue useable as a base table:

function mymodule_views_data_alter(&$data) {
  $data['nodequeue_subqueue']['table']['base'] = array(
    'field' => 'sqid',
    'title' => t('Queue'),
    'help' => t('Node queues'),
    'weight' => -10,
  );
  $data['nodequeue_subqueue']['sqid'] = array(
    'title' => t('Subqueue Id'),
    'help' => t('The subqueue Id'),
    'field' => array(
      'handler' => 'views_handler_field'
    ),
  );
}

Then you'll probably want to add some more fields/handlers/relationships to make it useful though.