Show a warning when configuring form displays when a field is hidden and has no default value.

Created on 14 October 2013, about 11 years ago
Updated 11 April 2024, 9 months ago

At admin/structure/types/manage/{content_type}/form-display you can set the Title field to be hidden in your form display. Great.

Now, if you create new content and don't have the Title field available (since it's hidden), you're not given the opportunity to a) give it a title, still (it's hidden, not disabled/deleted) and/or b) automatically generate one with, say, tokens, a bit like the Automatic Nodetitles module would do.

But besides that, I think it's prone to confusion for site builders as you cannot click on any piece of content without title at admin/content. You're thus left with a broken user experience in which a few options to see your nodes are to either edit the node or find the internal path. Not so much of a problem for advanced site builders, but it can really be challenging for new users (especially the latter).

Attached is a screenshot showing the problem:

We could mimic the Automatic Nodetitles features in Core, or enforce users they add a title even when the Title field is hidden. Alternatively, we should at least display the internal path as a fallback when listing content at admin/content

🐛 Bug report
Status

Postponed: needs info

Version

11.0 🔥

Component
Field 

Last updated 1 day ago

Created by

🇫🇷France anavarre 🇪🇺

Live updates comments and jobs are added and updated live.
  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

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.

  • 🇳🇿New Zealand quietone

    It has been 8 years since there was discussion on this issue.

    Is this still relevant to Drupal 10?

    Since we need more information to move forward with this issue, I am setting the status to Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

Production build 0.71.5 2024