-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Magento 2.1 CE, Cannot change attribute set for bundled product #5999
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
Comments
I have the same problem. Same specs and error. |
Same issue. So many bugs |
Does anybody know if there is a way to change the attribute set of a product, other than doing it on the edit product page? I tried creating new bundle products with the correct attribute set, but I get the same error when trying to create a new product. |
I'm having the same issue with simple products. The error occurs both when editing an existing product and when creating a new product. I'm on Magento CE 2.1.0 with PHP 5.6.20 |
@sean-jamersan @s00071609 @mikelevy300 Have any of you guys, been able to figure out solution or workaround for this error? Or are you still having the same problem? I tried creating new bundle products with the correct attribute set at the outset. But I get the same hanging error when created a new bundled product, that I get when trying to edit the attribute set of an existing product. As a last resort, I tried manually changing the attribute set in the database. Which at first, seems to have solved the problem. After manually changing the attribute set, I see that the product reflects the new set. But when I try to make changes to the product and save it, I get a lot of errors. So I don't think manually changing the attribute set, in the db, is the way to go. |
I have the same issue but here is my console error message. TypeError: $data.recordData(...) is undefined |
I think I found a workaround. For me it seems like the root issue was the price attribute not being in the 'Product Details' group of my destination attribute set. Before I started tinkering, my destination attribute set had a 'Prices' group where the price attribute was located. When I moved the price attribute out of the 'Prices' group back into the 'Product Details' group and deleted the 'Prices' group, I was able to change the attribute set for my product to the destination attribute set without any problem. Not sure if that's just a very specific example relevant to just me, but wanted to share that finding nonetheless. |
Thank you for the direction. No more issue after adding the "Bundle Items" group in my destination attribute set. |
Hi guys, Do you still experiencing this issue? I've tried it on new CE version 2.1.1 with sample data and it works fine for me from the scratch. Can anyone of you recheck it and provide detailed steps how I can reproduce it? Thanks! |
Same issue in 2.1.1. |
Hi there, Thanks for help. I've managed to reproduce it so I created internal ticket (#MAGETWO-58212) for it. This issue will be closed after fix. Thanks for contributing! |
Hi there, for me it works without "bundle items". But it fails if I move "price type" out of "product details. |
Same as flipflap. You should avoid moving "price type AND price" out of "product details". |
I had the same issue with 2.1.7 EE , in my case we have upgraded our store from 2.0.15 EE to 2.1.7 EE and with 2.1.x versions I noticed that there is a new attribute Group called "Bundle Items" which wrapped "shipment_type" attribute. So to resolve the issue I have manually "Bundle Items" group wrapped with "shipment_type" attribute to each custom Attribute sets and it resolved the issue |
same problem here with 2.1.9 |
actually this seems to happen with any attribute from the default attribute set, which is missing in the custom target attribute set |
@colinwolff are you sure that your custom attributeset has (at least) every attribute from the default attribute set? That "solved" it for us immediately |
Hi guys need some help magento 2 version 2.1.9 cannot change to my new attribute, only loading loading. :( |
@TClilMouse's and @cchamikara's solution worked for me. My destination attribute set did not have a "Bundle Items" group even though it had the "shipment_type" attribute. The "shipment_type" was located under a different group. I added the "Bundle Items" group to my destination attribute set and put the "shipment_type" attribute under and it worked. |
…or bundled product #5999 - Bug fix.
…or bundled product #5999 - Fix after review.
…or bundled product #5999 - Bug fix.
…or bundled product #5999 - Bug fix.
Fixed: MAGETWO-58212 [GITHUB] Magento 2.1 CE, Cannot change attribute set for bundled product #5999 MAGETWO-96842 [2.3.x] [Magento Cloud] [QUANS] Tiered block displayed on configurable products without any tiered pricing MAGETWO-96412 [2.3.x] Not possible to drag specified Related/Upsell/Cross-sell products to new positions in Windows 10 machine MAGETWO-96847 [2.3.x] Special price does not work when "default config" scope timezone does not match "website" scope timezone MAGETWO-96424 [2.3.x] [Magento Cloud] Requesition list qty of configurable product variation not updated individually MAGETWO-91589 Slow query delete on sub SELECT query MAGETWO-82221 [CE 2.1.0 rc3] - Cancel an order [configurable product] #5313 MAGETWO-92226 Product export creates 2 rows for Simple product with custom options MAGETWO-60910 Session initialized during reindex from CLI and result fatal error MAGETWO-97260 creating new shipment: gettting all trackers. after this commit 2307e16 MAGETWO-96342 MySQL connection issue MAGETWO-97434 MFTF test cases have parsing error MAGETWO-91513 Password reset email cannot be sent if the customer does not have customer attribute set that is changed to required after original account creation MAGETWO-95802 [EE] Admin date wrong formatting for French locale
…or bundled product #5999
…or bundled product #5999
Hi all, |
[TSG] Fixes for 2.4 (pr74) (2.4-develop)
I did the same what you suggest still getting the same error, any other possibilities of error? |
Preconditions
Steps to reproduce
Expected result
Actual result
The text was updated successfully, but these errors were encountered: