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

Visibility save attribute error #8271

Closed
piuga opened this issue Jan 25, 2017 · 4 comments
Closed

Visibility save attribute error #8271

piuga opened this issue Jan 25, 2017 · 4 comments
Labels
bug report Component: Catalog Issue: Cannot Reproduce Cannot reproduce the issue on the latest `2.4-develop` branch Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed 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

Comments

@piuga
Copy link

piuga commented Jan 25, 2017

Preconditions

  1. Magento 2.1.3

Steps to reproduce

  1. Open 'visibility' attribute and save it will show the load icon because of error: "Notice: Undefined index: value in ...\vendor\magento\module-catalog\Controller\Adminhtml\Product\Attribute\Validate.php on line 155";i:1;s:5369:"#0 ...\vendor\magento\module-catalog\Controller\Adminhtml\Product\Attribute\Validate.php(155): Magento\Framework\App\ErrorHandler->handler(8, 'Undefined index...'"

Expected result

  1. Attribute should save with success message

Actual result

  1. [Screenshot, logs] https://cl.ly/1L3j350V1M3N

The issue is inside Magento\Catalog\Controller\Adminhtml\Product\Attribute\Validate class, checkUniqueOption() function. Because 'visibility' is a dropdown attribute, the unique values validation is run, but this doesn't have any 'value' inside $options array.

@bassplayer7
Copy link

This also occurs on multiselect attribute types.

@miakusha miakusha self-assigned this Jan 31, 2017
@miakusha miakusha added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Jan 31, 2017
@miakusha
Copy link
Contributor

hi @piuga, thanks for report
I've linked this GitHub issue to internal ticket MAGETWO-63655

@miakusha miakusha removed their assignment Feb 8, 2017
@pooshok
Copy link

pooshok commented Mar 17, 2017

A similar problem here #8202. @cih997 posted temporary workaround

@magento-engcom-team magento-engcom-team added 2.1.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development bug report Component: Catalog Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed and removed G1 Passed labels Sep 5, 2017
@magento-engcom-team magento-engcom-team added the Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed label Sep 28, 2017
@magento-engcom-team
Copy link
Contributor

@piuga, thank you for your report.
We were not able to reproduce this issue by following the steps you provided. If you'd like to update it, please reopen the issue.

@magento-engcom-team magento-engcom-team added the Issue: Cannot Reproduce Cannot reproduce the issue on the latest `2.4-develop` branch label Sep 28, 2017
magento-devops-reposync-svc pushed a commit that referenced this issue Jun 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Component: Catalog Issue: Cannot Reproduce Cannot reproduce the issue on the latest `2.4-develop` branch Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed 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
Projects
None yet
Development

No branches or pull requests

6 participants