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

[Backport to 2.1-develop] Fix configurable attribute options not being sorted #12962

Merged

Conversation

wardcapp
Copy link
Contributor

@wardcapp wardcapp commented Jan 2, 2018

See github issue #7441, internal ticket MAGETWO-61484 and PR #12420.

Description

Resolves the issue documented in GitHub ticket #7441. A similar PR was opened before (#12420), which was now ported to Magento 2.1.x and required changes to the related unit tests were made as well.

Fixed Issues

  1. Configurable attribute options are not sorted #7441: Configurable attribute options are not sorted

Manual testing scenarios

(copied over from PR #12420, which is still valid)
Steps to reproduce
Create a configurable attribute and add two options at least.
Create a configurable product for these options.
Go to the product page and see the configurable attribute select (options).
Change attribute options sort order and flush all caches.
Go to the product page and see the configurable attribute select (options) looks like before.

Expected result:
Configurable options HAVE been reordered.

Contribution checklist

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests
  • All automated tests passed successfully (all builds on Travis CI are green)

See github issue magento#7441, internal ticket MAGETWO-61484 and PR magento#12420.
@magento-engcom-team magento-engcom-team added bugfix Component: Catalog 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 Jan 2, 2018
@wardcapp
Copy link
Contributor Author

wardcapp commented Jan 3, 2018

I noticed the PHP code sniffer failure and will address it one of the next coming days.

@ishakhsuvarov
Copy link
Contributor

Hi @wardcapp
#12420 seems to be closed without merging. Would be great if you could also fix the issue for 2.2-develop as we can not accept fix solely to 2.1 release line.

Corrected multi-line indents based on the report by the
PHP static tests.

See build reports for PR magento#12962
@wardcapp
Copy link
Contributor Author

wardcapp commented Jan 3, 2018

Hello @ishakhsuvarov, thank you for your feedback. You might have found it by now, but a similar pull request for 2.2-develop (holding the very same changes) was set up as well, see PR #12963 for the Magento 2.2.x version of the fix.

Apart from that, the PHP code sniffer errors are now corrected (within this PR).

@ishakhsuvarov
Copy link
Contributor

@wardcapp Sorry, concentrated on the one linked in the description too much :)

@ishakhsuvarov ishakhsuvarov self-assigned this Jan 3, 2018
@ishakhsuvarov ishakhsuvarov added this to the January 2018 milestone Jan 3, 2018
@magento-team magento-team merged commit a7c6f07 into magento:2.1-develop Jan 10, 2018
magento-team pushed a commit that referenced this pull request Jan 10, 2018
@magento-engcom-team magento-engcom-team added Fixed in 2.1.x The issue has been fixed in 2.1 release line 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 labels Jan 10, 2018
@kennedyabitbol
Copy link

Hi,

I noticed changes are already in 2.1.13 version but changes are not visible, my attributes are always unsorted.
Is there any change to make?

Damien.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix Component: Catalog Fixed in 2.1.x The issue has been fixed in 2.1 release line 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 Progress: accept Release Line: 2.1 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

Successfully merging this pull request may close these issues.

5 participants