- 🇬🇧United Kingdom catch
Tagging this with Field UX - while it's not a generic issue with the field UI, it is extremely confusing that you can control some things with field UI and some not, forces people back into templates and or looking around in content types settings forms or theme settings etc.
- 🇦🇹Austria maxilein
Take a look at https://www.drupal.org/project/base_field_override_ui →
- Status changed to Needs work
almost 2 years ago 5:45pm 11 July 2023 - 🇩🇪Germany Anybody Porta Westfalica
As @AdamPS wrote in 🐛 Book printer-friendly version should respect configurable title display Needs work , that's no blocker.
So the (blocking) obstacles are now all solved and we can proceed with the further steps! Yay! :)
- Status changed to Active
over 1 year ago 12:33pm 18 August 2023 - 🇬🇧United Kingdom adamps
I added two issues to the list of phase A. 🐛 Wrong comment display for sites configuring base field display in the UI Fixed is "needs review"
- 🇫🇷France andypost
Only one blocker left 📌 Reinstate important testing NodeDisplayConfigurableTest Active
- 🇬🇧United Kingdom adamps
Great so phase A is now complete.
I suggest that a good next step would be ✨ Add a tag select list in string Formatter Needs review . The code already exists in Manage Display module, so it just needs someone to write a test. I've moved on to other things now so hopefully some others have enthusiasm for the next phase.
- 🇬🇧United Kingdom adamps
I added two new issues to part A and any comments/work to help solving these would be appreciated.
These are not blockers so we can continue with part B in the meantime.
- 🇩🇰Denmark ressa Copenhagen
This would have been a great feature to have in Drupal CMS, but hopefully in 2025 it can reach completion?
- 🇩🇰Denmark ressa Copenhagen
By the way, the heading is "A Fix obstacles to manage display in contrib" which I understand as "semi-blockers", but they seem to not be?
@adamps:
I added two new issues to part A and any comments/work to help solving these would be appreciated.
These are not blockers so we can continue with part B in the meantime.
Perhaps move these two issues below "C" under a "Nice to have" header to prevent users skimming the Issue Summary from concluding "Oh, A is still not done ..." and don't look at issues under "B", thereby stalling progress?