Hiding the field in the "Manage Form Display" editing interface does not work. Dragging the field to the hidden section and saving the form is useless.

CommentFileSizeAuthor
Manage form display.png5.7 KBtetatu

Comments

tetatu created an issue. See original summary.

cilefen’s picture

Status: Active » Postponed (maintainer needs more info)
Issue tags: +Needs steps to reproduce

Is 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.

tetatu’s picture

I 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.

cilefen’s picture

I can't reproduce this.

I did the following:

  1. I installed a new Drupal site from the 11.x branch, which is at commit 501bbdbe21c257fc
  2. I browsed to /admin/structure/types/manage/article/form-display.
  3. I moved field Image to the Disabled section and saved the form.
  4. Image remains in the disabled section.
  5. I checked at /node/add/article that Image is in fact disabled.

Because of that, we need additional reproduction steps from you and perhaps error logging (including browser console errors, if any), to proceed here.

tetatu’s picture

But I specified Drupal 10.4, that's where the problem occurs. I haven't tried Drupal 11, as I don't use that.

cilefen’s picture

Thanks 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.

tetatu’s picture

I've taken note. I'm at a loss as to how to prove it.

cilefen’s picture

Can you confirm that there are no browser console errors or Drupal log errors whatsoever?

tetatu’s picture

I 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:

Uncaught TypeError: rowHandlers[data.rowHandler] is not a constructor

cilefen’s picture

It 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.

tetatu’s picture

Let'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.

tetatu’s picture

I installed a fresh Drupal 10 and there is no problem, hiding the fields work.

cilefen’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)
4aficiona2’s picture

I 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.

SES_UNCAUGHT_EXCEPTION: TypeError: rowHandlers[data.rowHandler] is not a constructor
    attach https://local-project.site/core/modules/field_ui/js/field_ui.js?v=11.1.5:125
    jQuery 2
        each
        each
    attach https://local-project.ddev.site/core/modules/field_ui/js/field_ui.js?v=11.1.5:116
    attach https://local-project.ddev.site/core/modules/field_ui/js/field_ui.js?v=11.1.5:55
    attach https://local-project.ddev.site/core/modules/field_ui/js/field_ui.js?v=11.1.5:54
    attachBehaviors https://local-project.ddev.site/core/misc/drupal.js?v=11.1.5:166
    attachBehaviors https://local-project.ddev.site/core/misc/drupal.js?v=11.1.5:162
    <anonymous> https://local-project.ddev.site/core/misc/drupal.init.js?v=11.1.5:32
    listener https://local-project.ddev.site/core/misc/drupal.init.js?v=11.1.5:20
    domReady https://local-project.ddev.site/core/misc/drupal.init.js?v=11.1.5:26
    <anonymous> https://local-project.ddev.site/core/misc/drupal.init.js?v=11.1.5:31
    <anonymous> https://local-project.ddev.site/core/misc/drupal.init.js?v=11.1.5:34


lockdown-install.js:1:135422

It still works for "Form display". There I can hide the fields but the same JS error pops up.

captain_canuck’s picture

Hello,

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

vladimir ms’s picture

Experienced 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

baysaa’s picture

Same 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

alexander tallqvist’s picture

I'm experiencing the same issue on Drupal 11.2.10 with field_group and gin installed.

seattlehimay’s picture

Just 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