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
Glad it works for you! Regarding selecting options, I've just tested the Views Autocomplete Filters module and got it working after I had a look at the README and made sure to use the same...
Can't filter content in a View
You are right, that was it... Now my problem is I would like users being able to select from pre-established options, like a drop down or maybe an autocomplete. For that I would the Autocomplete...
Can't filter content in a View
Here goes the screenshot for the exposed filter config I will try the module you are telling me about. thanks again!
Can't filter content in a View