In #803 we've added information to explain why some modules cannot be disabled when fields provided by these modules are in use in certain content types. This is a big UX+, but...
The "Required by: Field type(s) in use..." seems a bit "cryptic" to me and the "...see Field list" link that follows leads to a list of all fields instead of a filtered list of only the fields provided by the specific module. This feature can be further improved in various ways:
1. Instead of the generic "Required by: Field type(s) in use...", we could be more specific and have it for example like so: "Required by the Tags field used in the Article content type".
2. The part of this text that is the actual name(s) of the content type(s) would be links to the respective content type field edit page. Same as the links in the "Used in" column at the "Field list" page (/admin/reports/fields).
This way, an admin seeking to disable certain modules will not have to continuously hop from the modules list to the fields list and finally to the specific content types that hold the fields in question and then back to the modules list.
Related: #849
Recent comments
Welcome to the Backdrop CMS community! For me, Backdrop CMS came to deliver exactly what I had wished for in Drupal 7 — especially its low resource consumption and its ability to run on...
BFT Tool v1.8 by BossV For All Android Devices Latest (2027)
Here's a fun hack: You can remove any css file in a custom theme by defining a file with the same name in the theme's info file, but not actually having a file with that name in the theme...
How to get rid of grid-flexbox.css
What is demoralizing for the maintaineers when someone mentions the flaw of a useless buggy feature? A different opinion should always be a motivation not otherwise. I will mark this one...
Files uploaded using add file