hissy / addon_multiple_express_entry_selector Goto Github PK

When I try to Delete a Multiple Express Entry Attribute I get:

An exception occurred while executing 'DELETE FROM AttributeKeys WHERE akID = ?' with params [99]: SQLSTATE[23000]: Integrity constraint violation: 1451 Cannot delete or update a parent row: a foreign key constraint fails (concrete5.atExpressSelectedEntries, CONSTRAINT FK_C9D404BBA2A82A5D FOREIGN KEY (avID) REFERENCES atExpress (avID))

And I really see no way to fix this for myself so far... :/ this is seriously breaking

This is effectively a bug report for -> concretecms/concretecms#5718 (comment)

Copied text from that:

So I've tried using the Express Multi-Select, and in my dev testing (concrete5 8.5.4) When I add the multi-select addon manually that @hissy developed, I cannot use Single and Multi-Select attributes on the same Express Object, which is a problem for me.

Example scenario:

First Object, is an Event Location (hotel)

Second Object is an Event Location set of Sub-Sections (multiple meeting rooms, halls, etc)

Second Object is Events

Naturally, the Event Location associates with multiple Sub-Locations in a One-to-Many relationship. That works.

Then I create an Event Location, and two Event Location Sub-Sections. Associate the two Sub-Sections with the test Event Location, and that works.

Then I create the Event Object in such a way that it has two associations:
-Event Object associated with Event Location Object, in (Event) Many-To-One (Location) relationship
-Event Object associated with Event Location Sub-Sections (Event) Many-To-Many (Location Sub-Sections) relationship

Then when I define the Event Object I have Name Attribute, Single Express Select (Location) and Multi Express Select (Location Sub-Sections).

I then make a form with Name Attribute, Single Express Select, and Multi-Express Select.

I can enter the Name for the event, but Single Express Select presents NO options (when I know a location exists) BUT Multi-Express Select does work.

I think the issue is when using a Single Express Select AND Multi-Express Select on the same object, disabling the Single Express Select (and I really do need both to work for many reasons!).

Sorry, bit of a word-ful explanation :/

Normal attributes can be set using setAttribute('attribute_handle', attribute_value). However trying to set an attribute using a multi - select express attribute does not work as desired in this way. For example I have a user attribute which is an express multi select which holds a list of facilities a user is assigned to manage. I want to import a csv containing new users and assign their facilities based on an array in one field of the csv. But using setAttribute() won't allow this with the express multi select addon.