Problem/Motivation
When using a plain text field and inputting a string value of "0", the table does not render the value in the display. Instead it renders empty <td> </td> tags.
Steps to reproduce
- Create a new datafield field
- Create a new plain text field / column in the datafield field
- Enter the value of "0" in the input field when editing the entity
- View the entity
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | Capture d'écran 2025-02-16 085357.png | 13.24 KB | lazzyvn |
| #6 | Capture d'écran 2025-02-16 085224.png | 37.03 KB | lazzyvn |
| #5 | eca-plain-text-zero-issue.png | 13.41 KB | chrisck |
Comments
Comment #2
chrisckComment #4
lazzyvn commentedComment #5
chrisck@lazzyvn I don't think this issue is fixed. I've just tested this on the latest 2.0.9 release that has your latest commit in it.
Comment #6
lazzyvn commentedClear cache maybe?

tested on my drupal it works fine
Comment #7
chrisckClearing cache did not fix it. However, going to Manage display and changing the Format from Table to something else, and then back to Table fixed it. I think it required a saving of the Manage display.
Edit: This is definitely a bug and seems to happen when an entity reference field is included, and the display is set to Label (term name), rather the the term ID. See steps to reproduce below.
Comment #8
lazzyvn commentedyou didn't read the module instructions step 3?
Comment #9
chrisckPlease follow these steps to reproduce:
valuewith Type: Text (plain)alphabetwith Type: Entity referenceComment #10
lazzyvn commentedyou didn't read the module instructions step 4? It must config field settings, widget, formatter before use. If you can't, you can hire an drupal expert who can find the error in your case and send a patch to fix.
Comment #11
chrisckI have read all instructions included with the module and have set the field widget and field display. I'm reporting a bug. If you follow steps to reproduce you will see.
Comment #13
lazzyvn commentedYou can change annother formatter type it wil show 0. btw it fixed in dev version for default string formatter
Comment #14
chrisck@lazzyvn Tested the latest release 2.0.10 and this is fixed, thank you!