A default value is always set on unlimited fields on node edit form

Created on 22 October 2018, about 6 years ago
Updated 28 March 2024, 9 months ago

Conditions:

Drupal core with Client-side Hierarchical Select

1. Taxonomy vocabulary with 2 depths.
2. Node type with taxonomy term reference field.
2.1 Set to unlimited. NO default value.
2.2 On form display settings, check "Force selection of deepest level"

Actions

1. Create a new node, the field works correct, no default value is set.
2. Select a taxonomy term from the deepest value and save (testterm AND testterm 2).
3. Edit the created node: Now a default value is set:

This is wrong and it's tedious because you always have to deselect it when saving.

🐛 Bug report
Status

Closed: cannot reproduce

Version

11.0 🔥

Component
Field 

Last updated 1 day ago

Created by

🇨🇭Switzerland handkerchief

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇦🇺Australia pameeela

    Updated IS to clarify that this requires Simple hierarchical select module. Not able to try to reproduce at this time, may try later.

  • Status changed to Closed: cannot reproduce 9 months ago
  • 🇦🇺Australia pameeela

    Can't reproduce this on 11.x. Screenshot showing what I see on edit:

    Not sure if it is missing some steps, but I tried a bunch of different variations of settings, including setting a parent as the default, but never hit the issue described.

    Please reopen with additional steps if anyone believes this is still occurring.

Production build 0.71.5 2024