- Issue created by @nicxvan
- First commit to issue fork.
- 🇩🇪Germany onfire84
Hi, i ran into the same issue this week and will try to write a patch for that.
- Status changed to Fixed
about 1 year ago 1:49pm 13 December 2023 - 🇨🇭Switzerland berdir Switzerland
pathauto_update_8108() exists to fix that.
If you still have this issue then you either have/had default config that you hadn't updated that was installed after that update did run or re-imported fixed configuration after running updates.
I don't think it's necessary or useful to include that again.
- 🇩🇪Germany onfire84
I did rerun the hook and exportet the config changes again. Seams to be fixed.
- Status changed to Needs review
about 1 year ago 3:04pm 13 December 2023 - 🇺🇸United States nicxvan
I think it might be useful to include again since I've had four or five projects that ran into it. There is also a core issue that people respond to needing to fix it manually fairly often:
https://www.drupal.org/project/drupal/issues/3356728 💬 The "node_type" plugin does not exist - upgrade from D9 to D10 Closed: cannot reproduce
In my case for all sites it's always pathauto with the error so addressing that at the root would be nice.
- Status changed to Active
about 1 year ago 9:51am 14 December 2023 - 🇨🇭Switzerland berdir Switzerland
If someone writes a patch/MR for that then fine, the main issue here is that we need to educate, or better enforce, correct handling of config after updates, which is that config must always be exported after running updates. The second reason this happens is default config in modules and install profiles on sites that were installed after the previous update did run.