Closed (duplicate)
Project:
Content Construction Kit (CCK)
Version:
4.7.x-1.x-dev
Component:
nodereference.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
8 Apr 2006 at 21:24 UTC
Updated:
11 Sep 2006 at 16:33 UTC
Comments
Comment #1
jonbob commentedMy plan for this is to have the user select a views.module view of the nodes they want to reference. There's no sense in reinventing the wheel when views.module can create node listings using virtually any set of criteria.
Comment #2
allie mickaFair enough - that occured to me as well, and is probably the best approach overall.
I dislike hard-coding the filters as much as the next guy, but right now there's nothing. And in the long term, limiting by uid and an "administer node references" priv will come in handy.
Because you're not enforcing relationship rules, the selection UI is a topical change - you can always back it out later without trauma to existing data. I hope you'll consider a patch like this as an interim solution.
Thanks!
Comment #3
moshe weitzman commentedOooh this would be quite nice. Anyoneup for it?
Comment #4
StevenSokulski commentedBy sending it through views we would be able to use the infinite power of that to do whatever is desired including (but not limited to) watch this patch allows. I would prefer this patch go away so that in the future we are not patching ontop of this patch to get rid of it. Is any work being done on using views to determine what nodes are able to be referenced?
Comment #5
yched commentedI implemented (and extended) JonBob's idea in comment #1.
The patch is here : http://drupal.org/node/78825
(I put that in a new thread, because it does a little more...)
Comment #6
moshe weitzman commentedlets use yched's patch for this. is nearly ready. see last post.