I have created two entityforms and set them both as OG content through the OG field settings UI and OG adds an audience (entityreference) field to each of form.

Problem: For different target entity types, setting the target audience in one form is changing the target bundle in the other form's entityreference field! this doesn't affect the selection of different bundles for the same target entity type but makes the og audience ref field created by the OG field settings UI unusable in multiple entity references that target different entities.

i would greatly appreciate if someone else can confirm the following test:

1. create an entityform with target of type node. set it as OG Content. set the entityref target to an entity and set the bundle (or leave it unset).
2. create an entityform with target of type user. set it as OG Content. set the entityref target to user entity.
3. reload the 1st entityform. observe that the Node target's bundle options are changed to user.

a side effect of this is that it has corrupted my views by updating contextual relationships to the last saved entitytype erasing relationships i had previously set up.

Comments

laurencefass created an issue. See original summary.

Syntapse’s picture

Issue summary: View changes
Syntapse’s picture

Issue summary: View changes
Syntapse’s picture

further tests confirm a problem with og, and not entityreference or entityform.

1. i set up a couple more forms and manually and added entityreferences using the OG widget and i failed to reproduce the problem. i.e. the two entity references remained independent.

2. i deleted the entity references created in (1) and re-added them via the OG field settings UI and the problem returned.

There is erroneous coupling between audience fields when added by the OG field settings UI.

Syntapse’s picture

Priority: Critical » Normal

problem due to the entityreference field's machine name being the same across types. i had to change it to remove the dependency. giving the different audience fields different machine names solved the problem.

ive reduced status to criticial but wont close because i dont know if this is a programming/scope issue. i.e. should variable names inside different entities have co-dependencies?