Empty subfields not hidden in (flipped) table display format

Created on 11 July 2025, 23 days ago

Problem/Motivation

I wonder why subfields with no values are not hidden in table or flipped table display format (in single value custom field with multiple subfields)?

I have found only a single hint at this phenomenon here Don't output table display view mode if all sub-fields are empty Fixed , but no explanation whether this is expected behavior or not.

Hiding empty fields works okay with default or html list display mode.

Steps to reproduce

Html list

Default

Table

Flipped table

💬 Support request
Status

Active

Version

3.1

Component

Miscellaneous

Created by

🇮🇪Ireland marksmith

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

Comments & Activities

  • Issue created by @marksmith
  • 🇺🇸United States apmsooner

    I suppose we didn't account for that but it might require a formatter settings as some people may want to show the empty cells at least in a regular table. Honestly I think I may have left it open for something more advanced (like optional fallback value). I'll come up with something for the next release and perhaps a patch soon when i get a chance.

  • @apmsooner opened merge request.
  • 🇺🇸United States apmsooner

    Added a setting to both table/flipped (table) formatters that allows you to hide empty rows or columns (based on the formatter). Please test the patch out and update the ticket if it works for you as expected.

    • apmsooner committed 86292e98 on 3.1.x
      Issue #3535577 by apmsooner: Option to hide empty columns/rows for table...
  • 🇺🇸United States apmsooner

    No review response which is unfortunate. Help me... Help you...

    Calling it good and merging.

  • 🇺🇸United States drumm NY, US

    (Updating to resolve Drupal.org issue index issue, please disregard)

  • 🇩🇰Denmark ressa Copenhagen

    I found this issue by chance, after checking the issues fixed in the recent releases (great job, both fixing and documenting issues and changes @apmsooner!) and thanks for fixing this @apmsooner, and @marksmith for a great and clear issue, with enough detail, that it was clear what needed to be done.

    Just an observation, that perhaps @marksmith could get credited, for the great issue report? Because that's also credit-worthy:

    Contributions to credit

    The following are examples of types of contributions that should be recognized:

    1. Creating a well-written issue that describes a problem
    2. [ ...]

    https://www.drupal.org/docs/develop/issues/issue-procedures-and-etiquett...

    It's as easy as checking the box next to the user name in this issue, and hitting "Save" :)
    (I verified this in 📌 Embed fonts to comply with EU GDPR Active , and subsequently updated the documentation.)

    PS. I empathize with module maintainers, there are a LOT of tasks to juggle!

  • 🇺🇸United States apmsooner

    Added credit. @ressa, the best way to support my efforts is to help test issues. Theres a few that I could use some help testing out that will really benefit the next release if you can assist:

    https://www.drupal.org/project/custom_field/issues/3530753 Add ability to ignore timezone for a date subfield Active
    https://www.drupal.org/project/custom_field/issues/3539115 Provide support for Views Entity Reference Filter (VERF) Active

  • 🇩🇰Denmark ressa Copenhagen

    Thanks for a fast reply as always @apmsooner. I had a look at those two issues, and sadly I don't have time right now to take a closer look at them ...

    But Admin Toolbar uses a Meta issue to track issues for the next release, which can help interested users to see where they can help out, 🌱 [Meta] Roadplan for Admin Toolbar 3.7 Active .

    I would totally subscribe to it, and jump in if I felt I could help out, if you similarly created a "[Meta] Roadplan for Custom Field 3.2" Meta issue, with issues grouped according to importance, to let the community know which issues to look at first.

Production build 0.71.5 2024