I use a nodetype filtered by categroy as view as source for a CCK node reference field. This doesn't work (i think) after the update from 2.6 to 2.7 anymore.

For better understanding:
I have an content type "Object" and a content type "Contact". "Contact" is associated with a taxonomy (e.g. "Owner", "User", "Maintainer". In the Object type there is a reference field owner and I used to show only "Contact" items with taxonomy category "Owner". Hope this helps.

I'm not sure if I could re-install the old version of views to test this. May I simply copy the old module files? There were some database updates after running update.php.

Kind regards
Thomas

Comments

the_spy’s picture

the_spy commented

Exactly the same thing is happening for us - this affects node reference fields on forms: drop-downs, AJAX lookups, etc. The funny thing is that there are <option> tags in the <select> lists, and the value attributes are correct, however the names are all blank so you see a list of empty items.

The data itself doesn't seem to have been affected - normal users on the site aren't seeing anything weird.

Also: rolling back the files to the previous version seems to work. I don't think the DB update actually did anything!

Hope this helps...

Mani

DeFr’s picture

DeFr commented

Related bug in the CCK queue: #614292: CCK Reference fields based on views broken by recent change in views_plugin_style Views 2.7 (#502348).

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Closed (duplicate)

Geez, does anyone read the release notes. The 'related' bug fixes this in CCK.

the_spy’s picture

the_spy commented

Sure I read the release notes, though it wasn't that easy to spot that in there!

Either way, not sure how much of a good idea it is to upgrade to the dev branch of CCK on a production server? Personally I'm going to hold off upgrading Views until the fix is in the release version of CCK...

Unless you have a better idea, or I've missed something!

Mani

t.lan’s picture

t.lan commented

Thanks, I got it running with the patch - Just after learning how to read the Drupal developers jargon, how to patch files, understand if I should really do it, finding the essential patch, searching for the file to be patched...

It's good to see the whole micro cosmos here is working. But don't forget us as users of this complex system. To find the functionality I need, I have uploaded 59 modules to my server, 2/3+ of them active. And each day I get more afraid of the interdependencies.

But on the other hand its all great and its all working! So most of all thank you all for your tough work!

Regards,
Thomas

#3: I didn't got your message.