The current workaround for the replacement of the core provider inside the Data Source Manager doesn't work. Even worse it scrambles the connection between the data source selectors and the widget window for any data source item added below the GeoNode core provider.
The problem is due to the explicit removal of the selector from the list (first) and then the removal of the widget. Widgets remove their own selectors automatically when they are taken from the widgets stack (including the core provider). When GeoNode plugin forces the removal of the widget for the core provider, it tries to remove its selector from the list, but it removes the wrong one, since the selector had already been removed from the GeoNode plugin.
We should just remove the widget and let the selector go with it.
The current workaround for the replacement of the core provider inside the Data Source Manager doesn't work. Even worse it scrambles the connection between the data source selectors and the widget window for any data source item added below the GeoNode core provider.
The problem is due to the explicit removal of the selector from the list (first) and then the removal of the widget. Widgets remove their own selectors automatically when they are taken from the widgets stack (including the core provider). When GeoNode plugin forces the removal of the widget for the core provider, it tries to remove its selector from the list, but it removes the wrong one, since the selector had already been removed from the GeoNode plugin.
We should just remove the widget and let the selector go with it.