Error creating configurable products in 2.1.1

[dapdx]

This was working fine in 2.1, but now in 2.1.1 there is an issue. When creating a configurable product, when you click into the "create configurations" menu, the first couple steps work fine. I am able to select the correct attribute, then select the values I want to apply, then on the next step, all the settings work fine (apply image to all products, apply custom quantities, ect), but when you go to click next, nothing happens, then when you click next again it skips over the summary step and goes back to the main product page. The configurable options show up there like it worked, but when you go to save the product the associated simple products are not saved.

Is Magento 2 still in testing or something. This is getting really frustrating.

Preconditions

Magento 2.1.1 oh PHP 7

Steps to reproduce

1. Add new configurable product
2. Fill out configurable product information and save
3. Go to create configurations
4. Select attribute set (in this case shirt size)
5. Select attribute values (example Small, Medium, Large)
6. Choose image for each, price for each, quantity for each
7. Click Next to go to Summary (nothing happens)
8. Click Next again and it skips summary and goes back to original configurable product page
9. New associated simple products show up, but when you click save they are not actually created
10. When you go back to the configurable product the simple associated products are gone as well

Expected result

1. Expected result is for it to work like 2.1
2. Create configurable product and save
3. Click create configurations
4. Select Attribute set
5. Select Attribute Values you want to create
6. Enter image/pricing/quantities for each associated product
7. Hit next and go to summary
8. Hit Next and have it actually create the associated products and keep them associated with the configurable product

Actual result

1. Add new configurable product
2. Fill out configurable product information and save
3. Go to create configurations
4. Select attribute set (in this case shirt size)
5. Select attribute values (example Small, Medium, Large)
6. Choose image for each, price for each, quantity for each
7. Click Next to go to Summary (nothing happens)
8. Click Next again and it skips summary and goes back to original configurable product page
9. New associated simple products show up, but when you click save they are not actually created
10. When you go back to the configurable product the simple associated products are gone as well

Please get Magento 2 working correctly, this thing is an absolute mess and my clients are pissed and I'm frustrated.

[rudik99]

I have the same problem. I am also running 2.1.1 on PHP 7.0.9

Some additional information. If you regenerate your static files and make sure the file owner is the web server, then you will be able to "create" variants - but only on a clean install. I found the with Migrated databases the error is still present.

To make matters worse. If you edit the description of a configurable product (without touching configurations) it will then dis-associate all your variants on Save !!!!!

This is a massive, massive problem...... Configurable products is the backbone of Magento and its been broken in some-way since version 2.0

[SewHappy58]

I have same problem. Also I have upgraded to 2.1.1 and now when I save a configurable product, it removes the associated simple products. Is anyone testing these before releasing?

[andidhouse]

Same here - just tested with an upgraded version to 2.1.1.

Can anyone of the magento team pls check this.

I realized that a lot of new bugs appear on every update. Things that worked perfect in former versions now cause problems (fotorama bugs etc. etc.).

I think this must be a quality check problem on magento side. To me it appears as new features are implemented and not tested completely 👎
A feedback from magento side would be great.

[heldchen]

@SewHappy58 a content manager in our shop also reported this after our 2.1.1 upgrade, but I am not able to reproduce it. neither using her account nor on a nightly backup - when I save the product, the associated simple products are kept...

[heldchen]

we did some screen sharing sessions with our content manager to try to reproduce the problem. I was not able to find a pattern. most of the configurable products saved just fine after modifying their values, others would save but loose their associated products.

then one case we observed the product was saved ok, then immediately edited again due to a misspelled word in the description, and this second save removed the children.

it all seems pretty random to me at this point...

[gewaechshaus]

In our case, the configurable products children are loosing prices if you update the configurable product itself. In conclusion with every small change made, you'll have to mass update the associated simple products price.

Composer 2.1.1

[heldchen]

@gewaechshaus if you're not using en_US as locale in the admin backend, you ran into issue #5973

[fendowuk]

Same issue here, if we edit a Configurable product it dissociates all simple products. This is a major issue, we have had to stop all further development, this needs addressing immediately.

[PascalBrouwers]

It does seem more and more issues derive from upgrades. When upgrading to 2.1.0 I could not create an Invoice!
These are basic functionalities that should be tested. Don't run you tests on a clean install but run them upgraded install too!

[picamator]

@dapdx Thanks for reporting.
We've created internal ticket MAGETWO-58017 to fix it.

[heldchen]

@picamator does MAGETWO-58017 also include the problem while saving a preexisting configurable product (and then losing the child asssociations) as discussed in the comments? if not, should a separate issue be opened?

[picamator]

@heldchen MAGETWO-58017 includes scenario about updating an existing configurable product.
Therefore, it does not need to create separate ticket.

[heldchen]

thank you!

[andidhouse]

@picamator
Can i ask you a question regrading this topic?

We have seen bugs reported for month here and internal tickets created but nothing happened after this. Also in the new version 2.1.1 many bugs are not implemented.

Is there any timeline on this bug to be implemented.
We want to go online in a view weeks but with this bug it is simply not possible.

Many thanks!

[rudik99]

If I was Magento I'd pull 2.1.1 down for downloading, this to me is a critical bug.... anyone who might not throughly test could get could ruining their production database.

[fendowuk]

I'd second that @rkhoury82, 2.1.1 is unusable if using configurable products.

[picamator]

@andidhouse we have put highly that particular issue and expect them to solve in a nearest patch releases.
So thank you all of your participation here. Please feel free to take next steps forward to become Magento 2 contributors.

[ksz2013]

Same issue here as well, after upgrade to 2.1.1 if you try to upload images to the configurable product the product is changed from Configurable to Simple Product!!!
Also on save the simple associated products are lost!!
On a clean 2.1.1 instance these issues are not happening, it is very strange how the upgrades are added to Magento, does anyone know a proper way to upgrade from old instances to the latest ones and how can we be sure that our site won't brake? Every time I upgraded had to revert because more problems appeared...

[heldchen]

@ksz2013 simulate the upgrades on an identical copy of your sites and test test test. if everything works or is patched, upgrade the production instance...

[andidhouse]

I feel like more of a testing company then a company building working online-shops :-/.

I do not want to calculate the time we spent in testing and bug reporting - by for the worst experience so far for us. Hope this changes now. On a long term view we are not able to handle and support a software with that many new and existing bugs with every release.

So fingers crossed magento changes its policy here now and not later.

[heldchen]

@andidhouse I hear you - our project is ~4 man-months overdue due to magento 2.x "quirks"

[FredericMartinez]

Same problem here.

[daschenbrener]

I feel the pain guys as well. And I would pay to get these bugs dealt with to make this platform usable, as where it is right now, it is not. and the fact this is the CE channel as opposed to the EE, should not be the excuse here.

[andidhouse]

I think that this is the CE version should have nothing to do with it - if the ce version is gone i think magento has a much bigger problem ;-) Really hope this is changing now. Fingers crossed guys!

[rudik99]

This is fixed now in 2.1.3

[maksek]

The issue is fixed in develop.

[Caryyon]

We are still seeing this issue in 2.1.5. Has anyone found a fix?

[Ctucker9233]

@maksek Can we get references to the commits?

[KrystynaKabannyk]

@dapdx, @Ctucker9233, you can find fix here 4c4a4a2

[hezide]

I am having the same problem in 2.1.4...

[Ragspur]

This is still an issue for me as well. I cannot have a product with more than 19 configurations! Can someone please put in some sort of update on this issue or when it will be released?

[alrayn]

I am having the same problem in 2.1.5 when use PHP 7.0.x

[Shopliftdeals]

Version 2.1.3-error has not been fixed-VERY FRUSTRATING!

[denchev]

This is still an issue with version 2.1.6

[idlea]

re Magento2 products not showing front end
Hi I had a similar problem. Using collar size as an attribute I used for example 16 16.5 17 and so on.
I recalled that when using 1.7 I could not use " for inches I used in instead.
Changing the collar size in simple products fixed it and the product then appeared on the front end.

[kilis]

Issue still present on version 2.1.6

[MichaelJamesParsons]

This is still an issue for 2.1.7. It was very embarrassing for this bug to come up during a demo with one of my clients. I hope a fix is coming up soon.

[SchumacherFM]

This bug will/might be fixed in 2.2. The 2.1 Version only receives security fixes. For client demos we use 2.2 ;-)

[andidhouse]

i am not shure but not fixing a major bug since over 10 month from magento side... if it is fixed in 2.2 ok - but then it is 12 month and i think all agree that this is a time period nobody can work with.

[korostii]

Hi @SchumacherFM, is that official?

The 2.1 Version only receives security fixes.

Is there some kind of public announcement you could reference in that regard?

[andidhouse]

@korostii - i think you will not revceive a public announcement regarding this. There are over 2K issues reported here (maybe 200-300 are really bugs) and i think magento has no interest at all to communicate that 2.1 is only getting security updates.

In my opinion the magento communication should be more developer centered - not marketing centered.

[MichaelJamesParsons]

@SchumacherFM I've got an application that is ready to launch, with the exception of this blocker. Is there a known temporary fix or a stable version I can downgrade to? If you're using 2.2 for demos, which version are you using in production?

[Caryyon]

This seems to be an issue with decimal points in some of the custom options. Try and drop any of those before downgrading.

[MichaelJamesParsons]

@Caryyon After extensive testing, it seems the issue may be related to the size of the request, not the values of each attribute. I was able to create product variations using single attributes at a time. When I attempted to generate the variations using the two larger attributes (most values), the request failed.

Failed Attempt: size (5 values) and color (9 values)

The following request returned a 404 status.

POST  /catalog/product/validate/id/{id}/type/configurable/store/{id}/set/{id}/key/{key}/?isAjax=true

Successful Attempt: size (5 values) and quality (2 values)

The following request returned a 200 status.

 POST catalog/product/validate/id/{id}/type/configurable/store/{id}/set/{id}/key/{key}/?isAjax=true

The only notable difference between these two requests is the size of the configurable-matrix-serialized parameter sent in the POST request.

Findings

1. In the failed request, the parameter contained 39561 characters. While in the successful request, it contained 16745 characters.
2. In the failed request, the controller was never executed.
3. In the successful request, the controller was executed. Upon receiving a response, the page reloaded as expected, whereas the failed request returned a 404 and did not reload the page.

I'm looking into bypassing the validation to see if the variations will still save.

[MichaelJamesParsons]

Quick update, it turns out the issue I addressed in my previous post was related to a firewall on my hosting provider's end.

[StasKozar]

Can't reproduce this issue on 2.1.7.

[SyedMuneebb]

Creating a configurable product in Magento 2 is a long process so maybe you are missing any step. Here's a simple and detailed guide: Configurable product Magento 2.

[veloraven]

Internal ticket for ver. 2.1 - MAGETWO-59501
It was fixed already and fix will be available in one of the nearest releases.

[haalmaguer]

@antboiko this shows as solved but I still have the same problem in magento.2.2.4.