The bug is in the "search meta resource_provider". It loads its searchers at initialize time so if a plugin is enabled *after* moovida startup, the resource_provider won't know about it.
The proposed fix is to monitor the message bus for the PluginStatusMessage and when a plugin is enabled: load its searchers (if it has the searchers entry point in its egg-info). When a plugin is disabled, cleanup its searcher(s) if it has any. The meta_resource provider should also be notified at moovida startup (ComponentsLoadedMessage) and scan all the enabled plugins at that moment.
The bug is in the "search meta resource_provider". It loads its searchers at initialize time so if a plugin is enabled *after* moovida startup, the resource_provider won't know about it.
The proposed fix is to monitor the message bus for the PluginStatusMessage and when a plugin is enabled: load its searchers (if it has the searchers entry point in its egg-info). When a plugin is disabled, cleanup its searcher(s) if it has any. The meta_resource provider should also be notified at moovida startup (ComponentsLoad edMessage) and scan all the enabled plugins at that moment.