Single Store Mode Not Working as it Should

[ladle3000]

Preconditions (*)

1. Magento 2.3

Steps to reproduce (*)

1. If store was previously in multi store mode and attribute values exist are still set at the store view level, they are still displayed on the frontend after switching to single store mode and filling out the description for example. If a store view had a different description it will still show on frontend.

Expected result (*)

1. In single store mode only the default view attribute values should be used for products, as there is no way except to switch modes and go clear a a store view value and then switch back to regular mode.
2. If switching to single store mode, only default view entries should be honored.

Actual result (*)

1. Out of date descriptions and values will show on frontend if merchant toggles to single store mode and forgets about old entries made at store view.
2. Since this is not accessible there needs to be clarity, if you are going to use the way you have it programmed now. "There is a value of the attribute at a store level, please confirm it will be cleared on save"

[m2-assistant]

Hi @snoroozi. 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-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

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

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

• yes
• no

[orlangur]

@snoroozi Single Store Mode works as expected, please read description near corresponding switch more carefully.

[ladle3000]

You guys are terrible about closing tickets. I take the time to report an obvious issue, and you act like apes. @orlangur

[ladle3000]

If it worked as expected, since I'm your user, then I would expect this. So it does not work as expected. It works as programmed, which is not well enough.

[orlangur]

@snoroozi please take a look on the message I'm referring to and then I can explain you what's wrong with your understanding.

[ladle3000]

@orlangur This setting will not be taken into account if system has more than one store view you mean? My store ONLY HAS ONE STORE VIEW. You might be missing the point. In the past I had multiple store views, but all have since been deleted, and magento still serves the info saved at the store view level. This is not correct behavior. The code should check and use the default scope only if there is only one store.

…

On Mon, Apr 15, 2019 at 11:05 AM Vlad Veselov ***@***.***> wrote: @snoroozi <https://github.com/snoroozi> please take a look on the message I'm referring to and then I can explain you what's wrong with your understanding. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#22344 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACQbJT2XwXyMjrG6pjH29m1_6-CH3iAnks5vhJVWgaJpZM4cvvPT> .

[orlangur]

Hm, I didn't expect values are not removed when you remove the store view. Please add steps regarding store view removal into description.

[maxxeh1]

I'd also like to add that even if you never had other store views, or you migrate from a Magento 1 then attribute values are saved on store views that Magento shouldn't care about. I don't believe the issue really lies in the fact that enabling single store mode should delete all store view values. I think the issue is that the admin panel clearly only pulls values from store id 0 when it's single store mode but the frontend doesn't. The frontend pulls from the lowest scope store value of it's current website if it's single store view for some reason.

This is something I've had to continuously deal with on my single store magentos since attribute values just save randomly at times and I have to go into the database to fix an issue a client shouldn't be having.

[ladle3000]

@maxxeh1 We are on the same page here. And I have also migrated from M1 last year and consistently face issues of wrong store scope attribute values displayed on frontend.

There also needs to be a way to 'reset' the values back to using default scope if merchant chooses.

At @orlangur steps for removal I can't say exactly as it's been over a year, but it was simply delete stores and websites from Magento admin panel.

[m2-assistant]

Hi @engcom-backlog-nazar. 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-engcom-team 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-engcom-team 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.