Reviewed & tested by the community
Project:
Field Config Cardinality
Version:
4.0.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 Aug 2025 at 13:45 UTC
Updated:
7 May 2026 at 01:58 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
michaelsoetaertComment #3
michaelsoetaertComment #4
bvoynickWhat version of Drupal core? That might be helpful to know. I believe this change was added to support newer versions of core.
Comment #5
michaelsoetaertWe're currently on
drupal/core:10.3.10. We noticed the issue while preparing our upgrade todrupal/core:^11. It could indeed be this patch is not needed anymore once we've completed our upgrade.Comment #6
stefan.kornComment #8
stefan.kornMR using solution from @abramm to hopefully provide a D10/D11 compatible solution:
https://www.drupal.org/project/field_config_cardinality/issues/3454609#c...
Comment #9
dzinkevich commentedI tested this patch with Drupal 10.5.4 and 10.5.6 and it works with both.
For the record, this patch ALSO fixes the issue on the same where the weight handles didn't appear, which makes sense looking at the issue and tracking down how tabledrag.js works.
For testing, we were able to reproduce this by testing with fields that were paragraphs; for these, the table name is not the same as the field name that core uses.
Thanks so much everyone!
Comment #10
natemow commentedI think this patch is much more critical than what's been described to date...without it, tabledrag was completely broken for me, whether using Claro or Gin (which has tabledrag.js overrides). My stack is core 10.6.3, paragraphs_browser 1.3 (using the "experimental" widget...though "classic" yielded the same error).
Pre-patch, I was getting this in the console:
I eventually wound up at this issue because I realized that the "field_name-delta-order" class was not being added to the last table cell (@see template_preprocess_field_multiple_value_form(), Drupal.tableDrag.prototype.rowSettings) -- the class gets removed after tabledrag.js processing has run, but without its presence initially, the drag target can't be found.
Comment #11
halthHeads-up: if patch application fails with “malformed patch”, check the line endings on the downloaded
.patchfile. If it was saved or edited on Windows (or a tool rewrote it), it may have CRLF (\r\n) instead of Unix LF. BSD/macOS patch is picky about that and can report a malformed hunk even when the diff content is fine.Comment #12
steinmb commentedTrying to improve the title
Comment #13
caesius commentedNeither the patch file in #2 nor the MR fix the issue for me.
Also, #11 set this issue to RTBC but described issues applying a .patch file; if the MR had been used it would've been a .diff file. The patch and the MR seem to take different approaches to resolving this bug, but to me it doesn't seem fixed anyway. I'll see if I can replicate on a fresh sandbox environment.
Comment #14
caesius commentedNevermind; PEBKAC -- I had an extra trailing slash in my composer.patches.json file.
I've confirmed both the patch and MR resolve the issue, though the MR seems to be more thorough.