- Issue created by @Kristen Pol
- 🇦🇺Australia pameeela
AFAIK you can't hide a field on the node form for only certain instances of a node? I have no problem with the tags field appearing, I actually didn't intentionally remove it. So I think the fix is to add it back to the displays.
- First commit to issue fork.
- 🇮🇳India diwakar07
Reviewed MR !442, @anjaliprasannan added few comments for you.
The changes look good for the Person Profile content type (/people) page.
Attached is the SS for reference.I think we need to implement the same for all the content types having a listing page.
Please update the MR accordingly.
Moving for NW. - 🇦🇺Australia pameeela
I realised the field is missing from the default display, that's why it's not there on listing pages either. So we need to fix both.
- First commit to issue fork.
- 🇺🇸United States phenaproxima Massachusetts
Worked with @pameeela on this and added test coverage to ensure that the expected fields are visible, in the expected order. (We had some errant configuration.)
Pam told me on Slack she's happy with this, and I'm always happy with more test coverage, especially for fiddly display configuration.
-
phenaproxima →
committed 2bf09f1f on 1.x authored by
pameeela →
Issue #3498848 by pameeela, phenaproxima, anjaliprasannan, diwakar07,...
-
phenaproxima →
committed 2bf09f1f on 1.x authored by
pameeela →
-
phenaproxima →
committed fb528c21 on 1.0.x authored by
pameeela →
Issue #3498848 by pameeela, phenaproxima, anjaliprasannan, diwakar07,...
-
phenaproxima →
committed fb528c21 on 1.0.x authored by
pameeela →
- 🇺🇸United States phenaproxima Massachusetts
Merged into 1.x and cherry-picked to 1.0.x. Thanks all! You have the distinct honor of being the final commit before our pre-release total commit freeze, which means this stands a good chance of being the commit that becomes Drupal CMS 1.0.0. Nice work!
Automatically closed - issue fixed for 2 weeks with no activity.
