Closed (fixed)
Project:
Content Construction Kit (CCK)
Version:
6.x-1.x-dev
Component:
Views Integration
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 May 2008 at 02:53 UTC
Updated:
11 Jun 2008 at 21:56 UTC
Jump to comment: Most recent file
Comments
Comment #1
andershal commentedAlso posted in views issue tracking: http://drupal.org/node/256441
--
Anders Hal
Comment #2
yelloroadie commentedthis still seems to be a problem, The views people say it is probably a CCK issue (above link).
Comment #3
jpetso commentedThis error occurs because Nodereference passes the complete $field array to Views, instead of the $field['handler'] object that Views expects. The attached patch fixes this problem, and makes views in nodereferences work again.
Please review and apply.
Comment #4
dropcube commentedI confirm the issue:
Fatal error: Call to a member function render() on a non-object in \wwwroot\drupal6-dev\sites\all\modules\views\theme\theme.inc on line 179Applying the patch at #3 remove the error, however the select box does not show the titles of the node to reference. Changing the widget to the field to autocomplete, neither works.
jpetso : Could you please review and confirm/fix this.
Comment #5
MartinSfromB commentedThe patch works fine at my site.
Comment #6
dropcube commentedTested again and yes, it works. I was using a 'Node' row style, and it does not display the title of the nodes, 'Fields' row style should be used.
Comment #7
karens commentedThe reason you had trouble is because we have to have the node title in the view and if you don't explicitly add it in, it isn't there. There is a line in the nodereference module a few lines above this line that was intended to ensure the title field got added, but that apparently didn't do the job. I'll play around and find a way to ensure the title gets into the view no matter what kind of view you link to.
Comment #8
karens commentedI just committed a fix. We were already adding the title field to the view, but Views processing jumps past that if the view is not configured to have fields, so I changed the processing a bit so the list of available view includes only views that have fields and added a note to the description saying that only views with fields can be used for this.
Comment #9
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.