Closed (cannot reproduce)
Project:
Drupal core
Version:
10.4.x-dev
Component:
field_layout.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
18 Mar 2025 at 23:18 UTC
Updated:
17 Feb 2026 at 20:54 UTC
Jump to comment: Most recent
Comments
Comment #2
cilefen commentedIs this with the experimental "Field Layout" module? In that case be aware of #3370887: Inform users that Field Layout is deprecated.
Please add clear steps to reproduce in any case.
Comment #3
tetatu commentedI looked through the list to see which component this could be, this is the core state, so the separate Field Layout module is not enabled, so this is the default state after installation.
I attached the screenshot earlier in case it helps.
Comment #4
cilefen commentedI can't reproduce this.
I did the following:
Because of that, we need additional reproduction steps from you and perhaps error logging (including browser console errors, if any), to proceed here.
Comment #5
tetatu commentedBut I specified Drupal 10.4, that's where the problem occurs. I haven't tried Drupal 11, as I don't use that.
Comment #6
cilefen commentedThanks for that update. I repeated the steps in I outlined in comment #4, in Drupal 10.4.4, which as I write this is the latest release, and I could not reproduce the bug.
Comment #7
tetatu commentedI've taken note. I'm at a loss as to how to prove it.
Comment #8
cilefen commentedCan you confirm that there are no browser console errors or Drupal log errors whatsoever?
Comment #9
tetatu commentedI tried it in Firefox and Chrome, it didn't work.
I just checked the Drupal error log, there is no entry.
I checked the Browser error messages, there is 1 entry:
Comment #10
cilefen commentedIt would be possible to do something with that if you disable JavaScript aggregation, rebuild caches, then get that error with its stack trace for us.
Additionally, any information about what makes the affected Drupal site different from a newly-installed Drupal site will tend to help lead toward a resolution. Otherwise, we can only guess.
Comment #11
tetatu commentedLet's put this bug report aside then, as soon as I get a chance I'll install a fresh Drupal and if there's still an error then it will bring me closer to solving it.
Comment #12
tetatu commentedI installed a fresh Drupal 10 and there is no problem, hiding the fields work.
Comment #13
cilefen commentedComment #14
4aficiona2 commentedI have the same problem. Tried to hide fields for "Full content" display mode. After saving I get the message "Status message Your settings have been saved." but the fields are still listed in the "Content" section instead of the "Disabled" section. This used work until last week.
I use/run Drupal 11.1.5, once based/built on a Drupal CMS RC2 installation. Then always updated through Composer.
I use Display Suite (ds, 8.x-3.28) with the "1 col layout", have 2 field groups (field_group, 8.x-3.6) and Gin as a admin theme.
I tried it with switching/using a different admin theme (Claro, but the the saving still would not work) and switched Display Suite layouts (to 1-col with wrapper) but no difference here too.
This error shows up in my Firefox console. Tested it with Safari and Chrome too, same results there.
It still works for "Form display". There I can hide the fields but the same JS error pops up.
Comment #15
captain_canuck commentedHello,
Ran into the same issue, as a temporary workaround, you can click on "Show row weights" and use the dropdown to disable the field.
That worked for me at least.
Cheers
Comment #16
vladimir ms commentedExperienced the same annoying bug. Drupal 10.5.2.
The workaround which worked was based on captain_canuck's hint. Show row weights by itself did not solve the issue. But once set to 0, I could hide weights and drag the unorderly field down.
"Great success!"
Thanks
Comment #17
baysaa commentedSame bug on Drupal 11.2.
In my experience, it happened on a custom form mode, plus I have field_group module enabled.
Workaround in #15 still works on Drupal 11.2
Comment #18
alexander tallqvist commentedI'm experiencing the same issue on Drupal 11.2.10 with field_group and gin installed.
Comment #19
seattlehimay commentedJust to add to the datapoints, experiencing the problem with D10.6.3, field_group and claro. I think field_group is the likely culprit here.
Similar errors to #14: Uncaught TypeError: rowHandlers[data.rowHandler] is not a constructor