Reference method of reference field switches to first available in list if previously set to default

Created on 18 October 2024, 10 months ago

Problem/Motivation

The reference type settings of a entity reference field are constantly changing from default to another option.

Steps to reproduce

See screencast from this ticker:

https://www.drupal.org/project/taxonomy_manager/issues/3480667 💬 Reference method switching: Default to other Active
https://www.drupal.org/files/issues/2024-10-15/Screencast.mp4

Proposed resolution

I guess this is an issue, where other reference methods get selected when the currently chosen reference method is "default" in the database. This seems to be a selection issue of the default value in the widget. Whatever method is sorted first in the selection list gets selected.

🐛 Bug report
Status

Active

Version

10.3

Component

forms system

Created by

🇦🇹Austria daniel.pernold

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @daniel.pernold
  • 🇳🇿New Zealand quietone

    Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to our policies.

  • 🇺🇸United States TolstoyDotCom L.A.

    I tried this on a version of D11 dev with 2.0.8 of ECA (I enabled its Content/Core/UI/Views submodules) and I don't see the same issue. In one of the other posts you said it was due to Taxonomy Manager, is that still the case?

    Can you start from a blank slate and give a text description of the steps to reproduce this?

    Have you tried with other browsers and disabling any extensions in those browsers?

  • 🇫🇮Finland anaconda777

    I am seeing this same exact error on Drupal 10.5.1 and with ECA 2.1.10 , the reference method in reference type goes always back to
    Event-Based selection with ECA even selecting the Default and a taxonomy term for it and saving.

    I have taxonomy manager installed and also drupal AI, which I was using and noticing this, but maybe not related.
    Is there a fix for Drupal 10 for this issue?

Production build 0.71.5 2024