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
Funnily we launched a new Dutch website this very week, milieucafe.nl It is not a 'news' website but operates in the context of local government. The layout focuses on content instead of...
Looking for examples of (local) news websites running on BackdropCMS
The answer is off topic, but I'll add a little. 1. Backend. Why you don't need links to other websites: Since you know the structure of your site and content, you can decide for...
Looking for examples of (local) news websites running on BackdropCMS
Hi Chrys, AI isn't always your best friend. A form alter hook is correct, but hiding by CSS isn't ideal. You could look at how the TinyMCE integration does it, which provides hiding...
CKEditor5: Here's how to prevent "Select Image from Library" from appearing