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

Can not save attribute #5907

Closed
cizgidekiadam opened this issue Jul 30, 2016 · 12 comments
Closed

Can not save attribute #5907

cizgidekiadam opened this issue Jul 30, 2016 · 12 comments
Labels
bug report Component: Catalog 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.1.x The issue has been reproduced on latest 2.1 release 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

@cizgidekiadam
Copy link

Preconditions

  1. Magento v2.1
  2. PHP 5.6.14
  3. MySQL 5.6.31-77.0-log Percona Server

Steps to reproduce

  1. Add options an dropdown attribute which is used in configurable products or change any other storefront options
  2. Save
  3. It says saved.

Expected result

  1. Attribute options added

Actual result

  1. Nothing changed
@cizgidekiadam
Copy link
Author

An addition, trying save adding empty option rows. If i try three times save (even adding option or not) at last refresh, seems like here: http://prntscr.com/bzhgi0

@oserediuk oserediuk self-assigned this Aug 4, 2016
@oserediuk oserediuk removed their assignment Sep 2, 2016
@SerhiyShkolyarenko SerhiyShkolyarenko self-assigned this Sep 13, 2016
@SerhiyShkolyarenko
Copy link
Contributor

Hi @rbostan! Sorry, I cannot understand that steps to reproduce.
If you update attributes on backend, please, clarify the sequence of forms you fill and controls used.
If you send REST requests, please clarify the address and payload(data) utilized. Please look at #5963, it seems similar to yours issue.

@cizgidekiadam
Copy link
Author

I'm adding via backend. For example, create a 'dimension' attribute and add some options (about 800 :)

After a time, if you try adding new options or changing storefront options (ex. Use in layered nav) it says 'saved' but actually not. Also it reset storefront properties to default values.

@SerhiyShkolyarenko SerhiyShkolyarenko added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development and removed Progress: needs update labels Sep 26, 2016
@SerhiyShkolyarenko
Copy link
Contributor

Managed to reproduce with 248 options :)
Created internal issue MAGETWO-58966. Thank you for reporting!

@cizgidekiadam
Copy link
Author

No needs to thanks. That's what i do ;)

@magento-engcom-team magento-engcom-team added bug report Component: Catalog Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed labels Sep 11, 2017
@magento-engcom-team magento-engcom-team added the Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed label Oct 11, 2017
@magento-engcom-team magento-engcom-team added 2.1.x Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release 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 Oct 11, 2017
@magento-engcom-team
Copy link
Contributor

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

@chingulito
Copy link

Magento 2.2.2
I am facing same situation Added Attribute brand

  • Does not save the attributes
  • Does not index them
  • Does not save the Store Front conditions either like stated by OP
    SSH
    Cleaned, Flushed, forced permissions /var and /pub and ownership, aldo index them
    No luck

have anyone resolved this?
Thank you

@magento-engcom-team magento-engcom-team added the Event: distributed-cd Distributed Contribution Day label Mar 19, 2018
@magento-engcom-team magento-engcom-team removed the Event: distributed-cd Distributed Contribution Day label Apr 14, 2018
@rogan-son
Copy link

We experienced same error in v2.1.5. and had fixed this problem after updating a value in PHP configuration as below.

; How many GET/POST/COOKIE input variables may be accepted
max_input_vars = 10000

https://magento.stackexchange.com/questions/215308/php-max-input-vars-prevents-attribute-options-saving-in-m2?rq=1

@leoquijano
Copy link

I was having the same issue in v2.2.4, and the fix by @rogan-son fixed it for me.

This is more of a server configuration issue, but maybe Magento could present a warning to the admin. This is especially critical for those of us who are importing attribute option values from external data sources. If many values are configured, any administrator that goes in to update an attribute, could break the other options.

@aasim110
Copy link
Contributor

aasim110 commented Jun 12, 2018

Getting issue in Magento 2.2.3
facing same situation Added Attribute Size with 1300 options

Not able to save attributes
Also tried @rogan-son's fix but its not working for me.
Cleaned, Flushed, forced permissions /var and /pub and ownership, also index them
Still No luck

have anyone resolved this?
Thank you

magento-engcom-team pushed a commit that referenced this issue Jun 14, 2018
magento-engcom-team pushed a commit that referenced this issue Jun 14, 2018
magento-engcom-team pushed a commit that referenced this issue Jun 14, 2018
@lennartbee
Copy link

I had to use @rogan-son solution with a bigger number

PHP Warning: Unknown: Input variables exceeded 10000. To increase the limit change max_input_vars in php.ini. in Unknown on line 0

@magento-engcom-team
Copy link
Contributor

Hi @rbostan

Fix for this issue is expected to be delivered with the patch 2.2.6. Meanwhile this commit may be sued as a reference: 3845d9d

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Component: Catalog 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.1.x The issue has been reproduced on latest 2.1 release 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