Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Adding Custom Attribute - The value of Admin scope can't be empty #12294

Closed
webscot opened this issue Nov 15, 2017 · 4 comments
Closed

Bug: Adding Custom Attribute - The value of Admin scope can't be empty #12294

webscot opened this issue Nov 15, 2017 · 4 comments
Assignees
Labels
Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@webscot
Copy link

webscot commented Nov 15, 2017

Preconditions

  1. v2.2.1
  2. php7

Steps to reproduce

  1. Add customer Product Attribute
  2. Choose Dropdown
  3. Under Manage Attributes, click "Add Option" and then "Delete" empty boxes
  4. Attempt to save. Error produced, "The value of Admin scope can't be empty."

Expected result

  1. Attribute should save rather than trying to collect data that can no longer be entered.

Actual result

  1. [Screenshot, logs]
@magento-engcom-team magento-engcom-team added Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed 2.2.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release labels Nov 15, 2017
@magento-engcom-team
Copy link
Contributor

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

@virtual97 virtual97 self-assigned this Dec 15, 2017
@virtual97
Copy link

#mageconf

virtual97 added a commit to virtual97/magento2-1 that referenced this issue Dec 15, 2017
…e can't be empty- Made hidden fields disabled.
omiroshnichenko added a commit to virtual97/magento2-1 that referenced this issue Jan 2, 2018
@magento-team magento-team added the Fixed in 2.2.x The issue has been fixed in 2.2 release line label Jan 3, 2018
@magento-team
Copy link
Contributor

Hi @webscot. Thank you for your report.
The issue has been fixed in #12755 by @virtual97 in 2.2-develop branch
Related commit(s):

The fix will be available with the upcoming patch release.

codekipple pushed a commit to codekipple/magento2 that referenced this issue Jan 8, 2018
…e can't be empty- Made hidden fields disabled.
codekipple pushed a commit to codekipple/magento2 that referenced this issue Jan 8, 2018
@magento-engcom-team
Copy link
Contributor

Hi @webscot. Thank you for your report.
The issue has been fixed in magento-engcom/magento2ce#1299 by @magento-engcom-team in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming patch release.

@magento-engcom-team magento-engcom-team added the Fixed in 2.3.x The issue has been fixed in 2.3 release line label Jan 29, 2018
coderimus pushed a commit to coderimus/magento2 that referenced this issue Jan 29, 2018
Applied pull request patch https://github.com/magento/magento2/pull/12755.patch (created by @virtual97) based on commit(s):
  1. 2ccb374
  2. 288d0d4
  3. e78ea61

Fixed GitHub Issues in 2.3-develop branch:
  - magento#12294: Bug: Adding Custom Attribute - The value of Admin scope can't be empty (reported by @webscot)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

No branches or pull requests

5 participants