Magento2: I can't edit Or save changes for products anymore after import cvs file

Created on 27 Jan 2017  路  6Comments  路  Source: magento/magento2

Tierprice.txt

Preconditions

I use Magento 2.1.3

Steps to reproduce

By using Magento 2.1.3 after importing tier price cvs file, I can't edit products in backend anymore.The error in backend is

Warning: Illegal string offset 'price_qty' in vendor/magento/module-catalog/Model/Product/Attribute/Backend/Tierprice.php on line 7

Expected result

Products can be modified in backend about images , or custom options

Actual result

I recieve always the red Warning

Warning: Illegal string offset 'price_qty' in vendor/magento/module-catalog/Model/Product/Attribute/Backend/Tierprice.php on line 7
And nothing from products was changed

Catalog ImportExport bug report

Most helpful comment

All 6 comments

I dont have this problem anymore, after deleting some per cvs imported products, whose sku not normal are ( that means their long sku consist of distance ).

Great, I am closing.
Thank you for report.

We also have the same issue. What is the workaround, how is the issue solved?
Can you translate the comment to better English? I cannot make sense out of it.

@kathytrac "I dont have this problem anymore, after deleting some per cvs imported products, whose sku not normal are ( that means their long sku consist of distance )."

You should check your imported products , if there are some special sku . For example, sku = abc 09 because there is a blank between abc and 09. That may cause error. Then you should delete all of these sku (manuel or with cvs ) . Then you will not have this error more . You should edit these sku to let them have no blank . Sorry for my english if you dont understand.

Thanks for reply @kathytrac . We dont have spaces between the SKU names. Also looking at the error, I dont think that should be causing the offset issue. I would want Magento team to look at it, but this ticket is closed even though others are still facing problem around it. I hope https://github.com/magento/magento2/issues/8426 will be addressed with bit more relevant solution.

Was this page helpful?
0 / 5 - 0 ratings