I am getting the following image when trying to create a new Field of type Node Reference-->Select List.
Fatal error: Call to a member function render() on a non-object in /home/content/s/h/a/shantijoonu/html/drupal_sandbox/sites/all/modules/views/theme/theme.inc on line 179
I am trying to define a Content Profile node and trying to create a field as a Node Reference using a View. The view has been created correctly and I can preview the results fine. It is a simple view which displays Published (or user=Admin) nodes of type Image, which were created by the current user and which have a particular Taxonomy:Vocabulary associated with them. The results are as expected. When I create a Node Reference field and use the Advanced section to select the View, and then save my changes, it saves successfully. But if I try to reopen the field (Configure) I get the error above. If I attempt to create a new node of this type I get the same error.
I really need the ability to have node reference fields for my site. I am hoping to go live with an alpha release of my site in the next 2 weeks. Please help!
Comments
Comment #1
merlinofchaos commentedComment #2
pauldawg commentedThanks merlin for recategorizing this. Does this imply that you've recreated the problem, since you've updated the version to "dev"? I was also able to reproduce it using the sample view created by walking through the Advanced Help, so I think this is a valid bug unless I am missing something (like a necessary component?)
It would be great to have a workaround to this. I am new to views and CCK, as well as to Drupal overall (been at it for about 2 months), and to PHP (about 6 months) but I am an experienced Java developer and would be comfortable with putting a hack in place if someone can lead me in the right direction. I haven't put any watches in place yet, but it seems like maybe the $field variable is null or it doesn't contain an object.
As far as CCK is concerned, I am wondering if the Views:Fields and Views:Displays settings are even relevant to a CCK node reference field? If so, is there a specific setting that I should use?
Comment #3
karens commentedMerlin just moved it here because it's a CCK issue. The first thing to do is to update to the very latest -dev version of CCK since there have been lots of changes to the nodereference module in the last few days that may have fixed this.
If you still have problems in the latest code, you can set this back to active and report back.
Comment #4
pauldawg commentedExcellent! You are correct, it has been fixed in the Dev build! Thank you so much Karen!!
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.