- Issue created by @kenorb
- 🇳🇱Netherlands eelkeblok Netherlands 🇳🇱
I ran into what appears to be the same issue and I think it is mostly unrelated to migration. There is an easy workaround, which is to remove the plugin reference from the configuration. Nevertheless, it can give some nasty effects when disabling a module that contains UrlGenerator plugins that are in use. I added some steps to reproduce.
I *assume* the OP was having this situation too. If not, my apologies. Let me know, than I'll create a different issue. Of course, the same could happen if the "custom" plugin got its plugin ID changed, which is basically the same thing; the configured plugin is no longer available.
- 🇩🇪Germany gbyte Berlin
Shouldn't the module that implements the custom generator plugin also make sure its plugins are not being used during uninstall? I don't think it's something we should address here.
- 🇳🇱Netherlands eelkeblok Netherlands 🇳🇱
Correct me if I'm wrong, but shouldn't Simple XML Sitemap keep track of dependencies to other modules when a plugin is added to its configuration?
- 🇩🇪Germany gbyte Berlin
Correct me if I'm wrong, but shouldn't Simple XML Sitemap keep track of dependencies to other modules when a plugin is added to its configuration?
What would that tracking look like exactly? Any examples in the wild?
- 🇳🇱Netherlands eelkeblok Netherlands 🇳🇱
I would say this should be a config dependency: https://www.drupal.org/docs/drupal-apis/configuration-api/configuration-... →