Product Repository saves attribute values for existing product always on "Default Store Level"

[itaymesh]

Preconditions

1. Magento 2.1.2
2. PHP 7
3. Mysql 5.6

Steps to reproduce

1. Create a CLI command to create/update a production
2. Execute the comment (new product)
3. Execute the comment (update product)

Expected result

1. New Product: values are saved on "All Store Views"
2. Update Product: values are saved on "All Store Views"

Actual result

1. New Product: values are saved on "All Store Views"
2. Update Product: values are saved on "Default Store View"

Seems like the product repository class overrides the product store id and always assign default store id

app/code/Magento/Catalog/Model/ProductRepository.php#L530

$productDataArray['store_id'] = (int)$this->storeManager->getStore()->getId();

The only way to work around this issue is by getting the existing product with explicit parameter:
$product = $this->_productRepository->get($sku, true, 0);

and use the deprecated save method of Magento\Framework\Model\AbstractModel class at line 629.

[mattcoz]

This is driving me crazy. Updating a product in the backend always saves attributes with store_id of 0 and then on the frontend it looks up attributes using store_id of 1. So the only way to update anything is to do so directly in the database. This is with single store mode enabled, which should mean that there should only be ONE store not two.

[leitot]

I have this issue as well. I fixed it with a hack but is something going to be done about this?

[p3mbo]

I can confirm that this is an issue for me too still. Magento 2.1.6

[mattcoz]

What kind of hack did you use? This is really a debilitating issue and the developers don't seem to care at all. - Matt

…

On Mar 27, 2017 2:24 PM, "leitot" ***@***.***> wrote: I have this issue as well. I fixed it with a hack but is something going to be done about this? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#7720 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAUf75koyoYhVYhjfucIs3xidcrCeJxHks5rp_uNgaJpZM4LHJ7x> .

[leitot]

I wrote a before plugin for the save() method for the type Magento\Catalog\Model\ResourceModel\Product. Inside beforeSave() I set the store ID correctly on the product (after the ProductRepository's save() method messes it up)

[mattcoz]

Thanks, I'll give that a shot. I have the same problem with the category repository too. - Matt On May 22, 2017 9:03 PM, "leitot" <notifications@github.com> wrote: I wrote a before plugin for the save() method for the type Magento\Catalog\Model\ResourceModel\Product. Inside beforeSave() I set the store ID correctly on the product (after the ProductRepository's save() method messes it up) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#7720 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAUf75oBD3hoHTgjSLK6Qrr9hU7PmiZoks5r8j5bgaJpZM4LHJ7x> .

[cherreman]

I have this issue in CE 2.1.7.

The save method in the ProductRepository is incorrectly setting the store_id property on the product.

The fix is to check if the store_id is already set on the product, and if not, set it. Add the if-statement around the line below:

if (!isset($productDataArray['store_id'])) {
    $productDataArray['store_id'] = (int)$this->storeManager->getStore()->getId();
}