[Issue] Fix URL generation for new store when it created with setup:config:import

[m2-assistant]

This issue is automatically created based on existing pull request: #30023: Fix URL generation for new store when it created with setup:config:import

---

Preconditions (*)

Magento 2.4-develop

Emulate adminhtml area where url rewrites are created

Related Pull Requests

Fixed Issues (if relevant)

1. N/A

Steps to reproduce: (*)

1. On Dev. env setup only one store view with few categories and products
2. dump stores info to config.php with php bin/magento app:config:dump and commit it

3. Deploy to production (run php bin/magento setup:upgrade --keep-generated on production env)
4. On dev. env create second store view in the same Store Group and Website in config.php file

5. Deploy to production (run php bin/magento setup:upgrade --keep-generated on production env)
6. Go to Admin- > Marketing -> URL Rewrites;

Actual Result: ✖️ On second store view URL rewrites were generated only on dev env (it was created via admin), but they weren't generated on production env.

Expected Result: ✔️ On second store view on dev and production environments were generated URL rewrites for categories and products.

Questions or comments

My investigation shown that only in adminhtml area URL rewrites are generated when store view is created:

magento2/app/code/Magento/CatalogUrlRewrite/etc/adminhtml/di.xml

Lines 9 to 14 in a31f4a3

	<type name="Magento\Store\Model\ResourceModel\Store">
	<plugin name="store_plugin" type="Magento\CatalogUrlRewrite\Model\Category\Plugin\Store\View"/>
	</type>
	<type name="Magento\Store\Model\ResourceModel\Group">
	<plugin name="group_plugin" type="Magento\CatalogUrlRewrite\Model\Category\Plugin\Store\Group"/>
	</type>

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

[magento-engcom-team]

✅ Confirmed by @engcom-Alfa
Thank you for verifying the issue. Based on the provided information internal tickets MC-38327 were created

Issue Available: @engcom-Alfa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[magento-engcom-team]

Hi @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #30023 by @ihor-sviziev in 2.4-develop branch
Related commit(s):

• 075ddb4b76367df4e123ab71e2d1fb37e821160e

The fix will be available with the upcoming 2.4.2 release.