Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Upgrading SilverStripe /

Ask questions about upgrading SilverStripe to the latest version.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

MultiSelectField isn't working after update to 2.4.1


Go to End


6 Posts   2035 Views

Avatar
theTigerDuck

Community Member, 20 Posts

10 September 2010 at 4:24am

Edited: 10/09/2010 4:37am

Hi All,

after I updated to 2.4.1 my MultiSelectFields aren't working anymore. I use them for many_many releationships.
In my error.log it say's:

Warning at \multiselectfield\code\MultiSelectField.php line 33: Invalid argument supplied for foreach() (http://www-lokal.XXXXXX.de/admin/statistik/ClubEditForm/field/teams/item/44/edit)
Warning at \multiselectfield\code\MultiSelectField.php line 33: Invalid argument supplied for foreach() (http://www-lokal.XXXXXX.de/admin/statistik/ClubEditForm/field/teams/item/44/edit)

I'm using multiselectfield-trunk-r56

Please help.

No Matter it's working with the latest Stable Version.

Avatar
Nicolaas

Forum Moderator, 224 Posts

13 October 2010 at 4:53pm

Edited: 13/10/2010 4:53pm

I am having a different issue with the same field. Has anyone used it on 2.4?

Avatar
swaiba

Forum Moderator, 1899 Posts

13 October 2010 at 9:09pm

I've rasied this on here... http://www.silverstripe.org/all-other-modules/show/280032#post280032

But in the mean time I am using CheckboxSetField instead :(

Avatar
jam13

121 Posts

13 October 2010 at 10:09pm

Looking at this today.

Avatar
jam13

121 Posts

14 October 2010 at 2:02am

Hi Nicolaas,

May I ask what problems you are seeing in 2.4? I made some changes when 2.4.1 was released to handle a js lib which was no longer used by default, but AFIAK it's working fine on 2.4.2.

Avatar
swaiba

Forum Moderator, 1899 Posts

14 October 2010 at 2:33am

My issue was the wrong name for the module folder - all working now.