Relation select field settings are field instance settings. It would be more appropriate to use field widget settings to store the view and relation that are being used.

This creates a problem when another module is using a different widget that works on the relation field type as defined by this module.

(The instance settings show up on the other widget's settings form, and have nothing to do with that widget)

See #1816830: Switching widget type does not remove field instance settings.

Comments

steveoliver’s picture

steveoliver commented

Copied from my comment in 1816830:

It seems the root of this problem is that some module needs to be responsible for **always** defining the base field type. 'relation'. That way, it's not the widget modules' "responsibility" (stepping on eachother's toes) to define the base field type.

Dummy field has so far been the one to define this, but I think it should be something like relation_base_field or some other small module in relation.module....

I'll follow up in the Relation module issue queue, too.

steveoliver’s picture

steveoliver commented
Category: bug » support
Status: Active » Postponed

see #1817002: Relation Dummy Field uses its own field type

steveoliver’s picture

steveoliver commented
Category: support » task

woops. this is a task.

steveoliver’s picture

steveoliver commented
Status: Postponed » Closed (fixed)

See #1753844: relation select field type collision with relation dummy field and #1817002: Relation Dummy Field uses its own field type.