- Issue created by @pasan.gamage
- last update
over 1 year ago 32 pass - Status changed to Needs review
over 1 year ago 2:52am 2 November 2023 - Status changed to Postponed: needs info
over 1 year ago 7:00am 2 November 2023 - 🇩🇪Germany gbyte Berlin
The question is rather why doesn't your sitemap type entity have a label?
If you don't provide it while creating the entity, it should be creates automatically from the machine name.
Please provide a reproducible way of getting this warning.
- 🇦🇺Australia pasan.gamage
Hi @gbyte
The issue was caused when updating the module from D9 simple_sitemap 3.5, to D10 4.1.7.
I also noticed that the variants related configs gets deleted because there's no update path to migrate those configs.
Thanks - Status changed to Fixed
over 1 year ago 11:28am 3 November 2023 - 🇩🇪Germany gbyte Berlin
The issue was caused when updating the module from D9 simple_sitemap 3.5, to D10 4.1.7.
This may be specific to your instance as I have never heard of this problem before and we have tens of thousands of sites migrating from 2.x/3.x to 4.x.
I also noticed that the variants related configs gets deleted because there's no update path to migrate those configs.
You got it backwards. The configs get deleted because there *is* an upgrade path. Variants are now Drupal entities and have a different storage. Your variants got migrated.
In any case, just go to the variant edit form and create a label or alternatively just klick save.
- 🇦🇺Australia pasan.gamage
Hi @gbyte
Thank you very much for the explanations and helping me understand.
You mentioned the the varients were migrated. Which path in admin can I navigate to view them because I couldn't find any varient configuration from admin/config/search/simplesitemap. Automatically closed - issue fixed for 2 weeks with no activity.