- Issue created by @chrisck
- 🇨🇦Canada chrisck BC, Canada
@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.
- 🇫🇷France lazzyvn paris
Clear cache maybe?
tested on my drupal it works fine
- 🇨🇦Canada chrisck BC, Canada
Clearing 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.
- 🇨🇦Canada chrisck BC, Canada
Please follow these steps to reproduce:
- Create taxonomy vocabulary Alphabet
- Create three taxonomy terms in Alphabet: "A", "B", "C"
- Add a new data field to Basic page content type
- Leave the first data row as machine name
value
with Type: Text (plain) - Add another data row as machine name
alphabet
with Type: Entity reference - Configure Alphabet data row Entity reference type: Taxonomy term and Vocabulary: Alphabet
- Save settings
- Create new Basic page with "0" value in plain text and select a taxonomy term for Alphabet
- By default, "0" value will display in plain text, but the taxonomy term will show the term ID
- Go to Manage display for Basic page and click on the "cog wheel" to open up field formatter settings for Table, change nothing and "Update" field formatter Table
- Save the Manage display page
- View your Basic page and see the "0" value is missing, but now the taxonomy term name is showing.
- 🇫🇷France lazzyvn paris
you 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.
- 🇨🇦Canada chrisck BC, Canada
I 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.
- 🇫🇷France lazzyvn paris
You can change annother formatter type it wil show 0. btw it fixed in dev version for default string formatter
- 🇨🇦Canada chrisck BC, Canada
@lazzyvn Tested the latest release 2.0.10 and this is fixed, thank you!
Automatically closed - issue fixed for 2 weeks with no activity.