Configurable product is not added to cart, when using "add to cart" on category page.

[martins-scandiweb]

In http://magento2-demo.nexcess.net/men/tops-men/jackets-men.html

if I choose size and color and then press "add to cart", then I get redirected to product detail page with message "You need to choose options for your item."

Expected result

1. Configurable product is added to cart and success message is shown and user stays on category page.

[parekhreena]

Same issue reported earlier here reference id - #2574

[piotrekkaminski]

Internal ID MAGETWO-47017

[rickwhitehead]

Any progress on this issue please? Can I help investigate?

[rickwhitehead]

Hi @piotrekkaminski can I get involved with this? It's a show stopper for me.

[rickwhitehead]

@tanya-soroka ??

[piotrekkaminski]

cc @elenleonova
@rickwhitehead it's on our backlog but might take some time to implement.

[devhn]

Any news on this? The error messages are also missplaced by showing below the add-to-cart button instead next to non-selected attribute.

[rickwhitehead]

@piotrekkaminski @tanya-soroka how do we get involved please?

[rickwhitehead]

IS THERE A PULL REQUEST? IS ANYBODY DOING ANYTHING? PLEASE RESPOND!

[veloraven]

We are working on this issue.

[rganin]

Fixed under MAGETWO-47017 ticket.

[rickwhitehead]

Is there a pull request for this fix please?

[carlowens]

Hi,
Could anyone tell me which specific version of Magento 2 has this fix? Has it been released yet?
Thanks

[JDavidVR]

@carlowens it works without problem on 2.1.x

[carlowens]

ah ok I am using Magento ver. 2.1.1 but it doesn't seem to be working. Does each configurable product need it's own attribute set with a default?

[rickwhitehead]

@rganin if this issue is fixed please could you link to the pull request or advise of the fix so that people don't waste their time in this repository?

[antonkril]

@rickwhitehead, @carlowens, the issue was fixed on develop branch: e643a67

It's scheduled to be merged to 2.1.4

Sorry for the lack of info. We'll discuss issue closing report with more information.

[rganin]

@rickwhitehead there is no public pull-request for this fix, it was implemented under following revisions:
27d2486, cce06d2, d8a2550, 4b96c90, 0025497, 7420329, ac363e4 in develop branch and merged in e643a67.

[rickwhitehead]

Thank you @rganin, @antonkril & @alankent.
Asking for myself but also for others who might find this thread/issue: Would you advise simply cloning the current develop branch to implement this fix? or would you patch using files from those 7 commits?

[antonkril]

"Develop" branch is not stable, so you should not use it to build production stores.

If this fix is critical for your project, you can apply the patch. But be aware that patch might be not 100% compatible with your codebase or may cause some new issues.

The most preferred way is to wait till the new Magento version with this patch included is released.

[rickwhitehead]

Hi @antonkril , thank you for your speedy response.
I can't imagine that this bug isn't 100% critical for all but the most very basic of stores, but maybe that's just me? I highlighted this bug for a number of extension developers when I was looking for a workaround - so I'm sure this issue is a show stopper for many. However, Is there a roadmap for Magento 2 releases that we can view/track please? Obviously in particular this thread is interested in v2.1.4. Thank you.

[rickwhitehead]

@antonkril , @alankent Please could you respond with timelines/roadmap for next M2 releases?
Looking at the commits that @rganin mentioned for this fix I can already see new files that didn't exist in the last "stable" release v2.1.1, e.g. /dev/tests/functional/tests/app/Magento/Swatches/* and hunting through parent commits to see when these were added is also not that helpful. I'll be back to either using dev branch or grabbing all 50 files from that referenced pull request?

[rickwhitehead]

@antonkril @alankent?
on commit 0025497 merged in e643a67 please can I ask why we now have files in /app/code/Magento/ when /app/code doesn't exist in current stable releases 1.1.X ??? I'm busy trying to merge/patch to test this fix and of course this list of 7 commits only records

[sneakingJ]

@antonkril Are there any news on this? When will version 2.1.4 come out?

[helicops]

Is there any news about this patch?