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

Option Sets do not work correctly when using 6.0.11 #1060

Closed
Noodleyman opened this issue Mar 18, 2016 · 2 comments
Closed

Option Sets do not work correctly when using 6.0.11 #1060

Noodleyman opened this issue Mar 18, 2016 · 2 comments
Assignees
Labels
Milestone

Comments

@Noodleyman
Copy link

Stumbled across this whilst playing around with the latest version.

option sets are not working correctly.

Steps to reproduce:

  1. Clean install of CC6.0.11
  2. Build some options (I added 3 options groups)
  3. Add options to the options groups
  4. Build an option set, I added all options avaialble
  5. From products -> Assign option sets add the option set to "test product".
  6. Verify that the options are added when editing the product.

All options default to status disabled, but you can't enable them. If you check the box and save the setting is not stored.

You also can't add these options to the option matrix, it doesn't respect the checkbox when saving.

If you manually add the options to the product it works correctly, so it's an issue with option sets.

abrookbanks added a commit that referenced this issue Feb 9, 2017
@abrookbanks abrookbanks self-assigned this Feb 9, 2017
@abrookbanks abrookbanks added the bug label Feb 9, 2017
@abrookbanks abrookbanks added this to the 6.1.5 milestone Feb 9, 2017
abrookbanks added a commit that referenced this issue Feb 9, 2017
abrookbanks added a commit that referenced this issue Feb 9, 2017
It no longer converts custom ones to normal options. Why would it!?
abrookbanks added a commit that referenced this issue Feb 9, 2017
abrookbanks added a commit that referenced this issue Feb 9, 2017
abrookbanks added a commit that referenced this issue Feb 9, 2017
@abrookbanks
Copy link
Member

All good. This wasn't as monstrous as I expected.

@Dirty-Butter
Copy link

Is there anything in these code changes that might cause a Save of an edit of an existing product to show the Product not updated message when the product edit actually did save? I do not use Options.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants