Due to the current status of a nodequeue not being a proper node, it can't be used with the nodereference module. I needed cck to support nodequeue references, so I made one, pretty much copied from the nodereference.module. It's fairly clean, and supports both the select list and the autocomplete lookups widgets. Use at your own risk!

This is for cvs cck (I pulled today).

BTW this is pretty useless unless you theme the nodequeuereference field. I didn't realize that for a bit :)

cheers,
-o

CommentFileSizeAuthor
nodequeuereference.module7.89 KBoliver soell

Comments

oliver soell’s picture

oliver soell commented

okay there's still something slightly funky with the preview step in the autocomplete widget, but it goes through and saves in any case. Here's the code if someone feels like tracking it down. I am using drupal 4.7.0 and a db prefix.

<ul>
<li>user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ORDER BY nn.position DESC' at line 1 query: SELECT n.nid, n.title FROM drmods_node n LEFT JOIN drmods_nodequeue_nodes nn ON n.nid = nn.nid WHERE nn.qid = ORDER BY nn.position DESC in /var/www/drupal-dev/htdocs/drupal/includes/database.mysql.inc on line 120.
<li>user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'ORDER BY nn.position DESC' at line 1 query: SELECT n.nid, n.title FROM drmods_node n LEFT JOIN drmods_nodequeue_nodes nn ON n.nid = nn.nid WHERE nn.qid = ORDER BY nn.position DESC in /var/www/drupal-dev/htdocs/drupal/includes/database.mysql.inc on line 120.
</ul>
oliver soell’s picture

oliver soell commented

sheesh.. i take it back. it was my themed field trying to use the queue's qid which doesn't exist at that point seemingly. I suppose that is a bug in its own right..

jonbob’s picture

jonbob commented
Project: Content Construction Kit (CCK) » Nodequeue
Version: 6.x-1.x-dev » 7.x-2.x-dev
Component: General » Code

CCK won't add direct support for modules unless they are almost ubiquitously used (like Views). This should either be part of the Node Queue project or a brand new project all by itself. Looks like a useful feature to those who need it, though.

merlinofchaos’s picture

merlinofchaos commented

Tell you what. I can commit this module as part of the nodequeue project, but it's more than I can maintain.
This means that I'll probably not be able to address bugs in the module; and before I'm willing to commit it, I'd like to see both Drupal 5 and Drupal 4.7 versions of the module. If you're willing to do that, at least, I'll drop it in both version.

dww’s picture

dww
we/he/they
commented
Status: Active » Closed (won't fix)

@merlin: if you don't have the time to maintain it yourself, i highly recommend that oliver soell puts it in a separate project and maintains/manages it directly. it's just easier this way, from CVS access to release management. sure, it's an extra step for someone to download and enable if they want it, but that's not the end of the world.

merlinofchaos’s picture

merlinofchaos commented

That's fair, dww, but what if the author doesn't have time to maintain it either?

Though none of my needs were met, either, so clearly this isn't going to be committed here.

dww’s picture

dww
we/he/they
commented

what if the author doesn't have time to maintain it either?

Then they can commit it to their own abandoned project. ;) If you're not going to maintain it, it doesn't do anyone any good to put it in the nodequeue project... If they're not going to maintain it either, it's only useful if someone else finds it and decides to adopt it. Putting it in its own project, clearly marked as "unmaintained" makes it more likely that someone who cares about it can find it and take it over.