Multiselect is wonderful, and I can't wait to use it with Drupal 7. =)

When editing a node using multiselect with node references in Drupal 7, I get this error:

Warning: array_key_exists() [function.array-key-exists]: The first argument should be either a string or an integer in _multiselect_build_widget_code() (line 181 of ... modules/contrib/multiselect/multiselect.module).

I checked the development version and this was still broken, so I thought you might want to know about it.

The fix is straightforward - add the same kind of processing used for CCK taxonomies or values to process nids, too. (User references are probably not supported, too, and can be fixed the same way.)

Sorry I can't add a patch!

Comments

mikeprinsloo’s picture

mikeprinsloo commented
Version: 7.x-1.8 » 7.x-1.x-dev

I've tried both Multiselect 7.x-1.8 and the lates dev version (25 Feb 2011) with node references (references module). With both modules I can successfully select node references and they are saved correctly however when I edit existing content the selected nodes are not loaded into the multiselect field. I have to select all references again.

mikeprinsloo’s picture

mikeprinsloo commented
Title: Multiselect 7.x-1.8 does not support node references » Multiselect does not support node references

Changing title to be more descriptive.

greenbug’s picture

greenbug commented

Got the same result using Multiselect with References module - nodes are not loaded then editing existing content.

attheshow’s picture

attheshow commented
Assigned: Unassigned » attheshow

Yes, I had this working during one of the D7 release candidates, but I think some changes were made to the Field API at the launch that broke the Node References integration. I'll try to get it figured out soon.

attheshow’s picture

attheshow commented
Status: Active » Fixed

Just pushed a change to dev version for this to support new References module. Hopefully I did my first Git commit correctly and the dev version will be updated soon!

ndvo’s picture

ndvo commented

I was having this problem (with postgre) and installing the dev version fixed the bug.
Thanks.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.