Magento2: Unable to change country of manufacture default label value

Created on 5 Oct 2016  路  14Comments  路  Source: magento/magento2

Preconditions

  1. Magento 2.1.1 fresh install.

    Steps to reproduce

  2. Navigate to product attributes in admin panel

  3. Edit country of manufacture attribute
  4. Try to change default label
  5. Hit save

    Expected result

Attribute is saved

Actual result

attribute rename error

Catalog distributed-cd Fixed in 2.2.x Fixed in 2.3.x Clear Description Confirmed Format is valid Ready for Work Reproduced on 2.1.x Reproduced on 2.2.x Reproduced on 2.3.x bug report

All 14 comments

Same problem.

Even no such option value saved in table 'eav_attribute_option' for attribute 'country_of_manufacture'. and Manage Options grid showing the options as disabled. Really this renders magical. Can anybody tell how such attribute value is saving in product save ?

I created same king of attribute. Added Source module (Country), option are showing up in product form. but not saving value anywhere. Please keep hope for help from you...

Created an internal jira ticket for this issue ->MAGETWO-59882

Would love an update

Same problem with Magento ver. 2.1.3.
I can't save labels for county_of_manufacture, status, tax_class_id, and so on..
For new custom created attributes , It is working fine.

Hello. What about this issue? Was it fixed already? Have the same problem.
Maybe someone know where to find values of this attribute in DB? I suppose this error is displaying because the first value is empty. Maybe try to set it's value to one of the folloving "No", "Empty".

Issue still present in 2.1.7... Please provide urgent update or work around
thanks

@wujashek, thank you for your report.
We've created internal ticket(s) MAGETWO-59882 to track progress on the issue.

Same situation with Magento 2.2.0

I'm working on it for #SQUASHTOBERFEST 2017, I'll make the PR in a few minutes.

distributed-cd

@MateuszChrapek thank you for joining. Please accept team invitation here and self-assign the issue.

I've made pull request #14319 fixing this issue.

Hi @wujashek. Thank you for your report.
The issue has been fixed in magento/magento2#14319 by @MateuszChrapek in 2.2-develop branch
Related commit(s):

The fix will be available with the upcoming 2.2.5 release.

Hi @wujashek. Thank you for your report.
The issue has been fixed in magento/magento2#14714 by @rostyslav-hymon in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming 2.3.0 release.

Was this page helpful?
0 / 5 - 0 ratings