This idea started as a suggestion for a contrib module, but it seems it'll only work if it's a core feature...
The above linked issue has more details, but the summary is that we could create a new hook that modules implement in order to determine whether they're in use or not. This would then allow a report of modules that are enabled on a site, but aren't being used (and so can be safely uninstalled, or configured so they're actually used).
For example, the core Contact module would implement this hook and return TRUE if there are no contact categories. The Taxonomy module would return TRUE when there are no vocabularies. The Link module would return TRUE when there are no Link fields.
The hard part will be getting contrib modules to implement this hook, but if/once they do, I think this'll be a really handy feature to help clean up sites.
Recent comments
Oh, that might be my problem! I've set the layout for taxonomy/term/1134 (the TID for the term in question), but the view is generating an entirely new page, not rebuilding that specific...
Adding a menu to a layout for certain taxonomy/view pages
I tried something similar with a Custom Block (instead of a menu). It did work for me. I enabled the Taxonomy Term view I created a layout for path taxonomy/...
Adding a menu to a layout for certain taxonomy/view pages
Hi Martin, Thanks for the quick reply. Depending on whether I receive an invoice, I could spend 300-400 euros on it. For the first one I don't need the submodules Kind...
Porting of module "Entity reference autofill"