Products which are not assigned to any store are automatically being force-assigned a store ID after being saved

[diamondavocado]

Preconditions (*)

1. Magento 2.3.1

Steps to reproduce (*)

1. Find a product in your store which is not currently assigned to any store/websites.

In my case, I achieved this by deleting several old websites (store views) which left a bunch of products "orphaned" without a store ID.

For testing purposes you could also un-tick all of the boxes under the "Product in websites" section in the Magento admin panel -> Manage products -> [your product] area.

You could probably also achieve this by deleting a product from the catalog_product_website database table.

I was able to find a list of all my "orphaned" products using the following query:

SELECT * FROM catalog_product_entity WHERE entity_id NOT IN (SELECT product_id FROM catalog_product_website);

2. Open the above product in Magento's admin panel (Manage products) section.

3. Don't make any changes (or you can change the product title etc. if you wish) but just hit the "Save" button to save the product.

Expected result (*)

1. Since you haven't touched the "Product in Websites" section, the product should remain orphaned (i.e. it should NOT have a store ID associated with it). The product should NOT appear in the catalog_product_website table.

Actual result (*)

1. The product is automatically assigned a store ID. If you expand the "Product in websites" section, the first website checkbox is automatically ticked. The product DOES appear in the catalog_product_website database table even though you have not chosen to assign this product to a store.

[m2-assistant]

Hi @diamondavocado. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@diamondavocado do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[diamondavocado]

@magento give me 2.3-develop instance

[magento-engcom-team]

Hi @diamondavocado. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

Hi @diamondavocado, here is your Magento instance.
Admin access: https://i-23383-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[diamondavocado]

I was able to reproduce this on 2.3-develop instance.

I created a product but made sure to assign it to no stores:

The products grid shows that no stores/websites have been associated with this product:

However, I then returned to the Edit Product page, and expanded the "Product in websites" section and it has automatically pre-checked the "Main Website" box:

At this point, if I were to Save this product, it would be associated with the Main Website.
I do not save the product at this stage.

I refresh the page and this time I do not expand the "Product in websites section":

I do not edit anything at all and I click the Save button to save the product.

Now I discover the product has forcibly been assigned to the Main Website store even though I did not even expand that section:

This is the bug.

[magento-engcom-team]

✅ Confirmed by @engcom-Bravo
Thank you for verifying the issue. Based on the provided information internal tickets MC-17780, MC-17781 were created

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