[Issue] Prevent Category URL Rewrites generation when no Store Group assigned

[m2-assistant]

This issue is automatically created based on existing pull request: #32790: Prevent Category URL Rewrites generation when no Store Group assigned

---

Description (*)

During creating new website, Store Group and Store view using php bin/magento setup:upgrade - we got the following issue:
exception was thrown while it was trying to create a new store view that later on will be assigned to Store group, and as result - later on we should generate URLs for this specific store.

This issue happened because, for some reason, we $rootCategoryId as 0 because we don't have any assigned Store Group:

magento2/app/code/Magento/Store/Model/Store.php

Lines 1023 to 1029 in 95819f2

	public function getRootCategoryId()
	{
	if (!$this->getGroup()) {
	return Category::ROOT_CATEGORY_ID;
	}
	return $this->getGroup()->getRootCategoryId();
	}

In this case, it was generating URL rewrites for Root categories, that the same URL keys.
Example:

-- Root Category 1 (used on Website 1)
---- Best Sellers (URL key is `best-sellers`)
---- ...
-- Root Category 2 (used on Website 2)
---- ...
---- Best Sellers (URL key is `best-sellers`)
---- ...

In this case, it will try to generate URL rewrites for Root Category 1 and all their children categories + URL rewrites for Root Category 2 and all it's children and will have a conflict due to the same URL key

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes magento/magento2#<issue_number>

Manual testing scenarios (*)

1. Create 2 websites, category structure like this:

-- Root Category 1 (used on Website 1)
---- Best Sellers (URL key is `best-sellers`)
---- ...
-- Root Category 2 (used on Website 2)
---- ...
---- Best Sellers (URL key is `best-sellers`)
---- ...

2. Dump websites/store groups/stores data to the config.php file using php bin/magento app:config:dump scopes command
3. Create DB dump
4. Create from the admin a new website, store group, store view, use Root Category 1 for it
5. Dump websites/store groups/stores data to the config.php file using php bin/magento app:config:dump scopes command
6. Apply dump from step 3
7. run php bin/magento setup:upgrade

Expected result:
✔ 3rd website, store group, store view should be created

Actual result:
❌ We have an exception Import failed: URL key for specified store already exists.

Questions or comments

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)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[gabrieldagama]

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

• bac82cc344d01f369c3415cdb7ff308971da3bf3
• 6817e68d6ea4cd4a133720793bb580d1f8a8e477

The fix will be available with the upcoming 2.4.3 release.