This should be in core

Created on 6 November 2019, over 5 years ago
Updated 24 January 2024, about 1 year ago

That is all

Feature request
Status

Active

Component

Code

Created by

🇬🇧United Kingdom mrpauldriver

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

Merge Requests

Comments & Activities

Not all content is available!

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

  • 🇮🇹Italy kopeboy Milan

    Isn't this already in core?!
    Working both for Entity Reference w/ Autocomplete & Plain text fields..

  • 🇺🇸United States jrockowitz Brooklyn, NY

    Yep, this made it into Drupal core via 📌 Allow for deletion of a single value of a multiple value field Fixed

    Based on the commit this feature made it into Drupal 10.2.1+

    We could limit this module to Drupal < 10.2.1 so that people know to uninstall it when updating to Drupal 10.2.2.

  • First commit to issue fork.
  • Merge request !8This should be in core → (Open) created by voleger
  • Status changed to Needs review about 1 year ago
  • 🇺🇦Ukraine voleger Ukraine, Rivne

    I added MR with changes in the info file.

  • 🇦🇺Australia pameeela

    It would be great to update the module page with this info as well, suggest something like:

    This module is no longer required as of 10.2.1, as the issue was resolved in Drupal core in

  • 🇺🇸United States daddison

    Somebody please correct me if I'm wrong - My testing of this module with/alongside the core functionality in >10.2 has led me to believe that the core functionality only works when the cardinality of a multiple value field is unlimited (-1).

    In the screenshot below, the "Related stories" field is unlimited and shows both this module's "x" removal widget and the core "Remove" button. The "Related events" field is limited to three values and shows only this module's "x" removal widget. Confusing!

    The comment history in #1038316-74: Allow for deletion of a single value of a multiple value field seems to indicate this is a feature not a bug. In my use case, fields with limited and >1 values need a remove option as well.

    Anyway, I think this module still has utility with >10.2 and that should be stated on the module info page.

Production build 0.71.5 2024