Magento2: 2.2.2 - Duplicating Bundle Product Removes Bundle Options From Original Product

[MattUnity]

I can't seem to duplicate bundle products and retain their bundle options on a Vanilla 2.2.2 installation - It moves the bundle options over but doesn't appear to retain them for the original product, leaving it blank and stripping its options.

Preconditions

1. Magento 2.2.2
2. PHP 7.0.27

Steps to reproduce

1. Create a simple product
2. Create a bundle product, adding the aforementioned simple product as a bundle option
3. Click Save he bundle product
4. Click Save and Duplicate the bundle product

Expected result

1. Both the original and duplicated bundle products should contain the simple product as a bundle option.

Actual result

1. The duplicated bundle product contains the bundle options, but the original product has bundle options removed.

[magento-engcom-team]

@MattUnity, thank you for your report.
We've created internal ticket(s) MAGETWO-86647 to track progress on the issue.

[magento-team]

Hi @MattUnity. Thank you for your report.
The issue has been fixed in magento-engcom/magento2ce#1217 by @nmalevanec in 2.2-develop branch
Related commit(s):

• b57eb03b2f6491d271221d08b185e2ff37bfcd4c
• d8bd657c94175392eca5ad462932bc2e86c51257

The fix will be available with the upcoming patch release.

[densen45]

Unfortunately, the fix is not included in the 2.2.3 release. However, it is currently included in the 2.2.4-preview branch.

[macrodesignuk]

This problem still exists in v2.3.0, has this fix been made live?

[getsolved]

Problem still exists in 2.3.0
When will it be fixed? Mass creation of products very annoying.
No solution in over a year??

[macrodesignuk]

Problem still exists in 2.3.0
When will it be fixed? Mass creation of products very annoying.
No solution in over a year??

They have fixed it, they just haven't released the patch. Its annoying as a lot of the Magento 2 faults I've experienced were fixed 1 year ago, but they haven't officially released them yet.

You can replace the related problem files from here
https://github.com/magento/magento2/commit/b57eb03b2f6491d271221d08b185e2ff37bfcd4c
https://github.com/magento/magento2/commit/d8bd657c94175392eca5ad462932bc2e86c51257

[Goeny]

Problem still not fixed ?

[hostep]

Re-opening, since it looks like the fix never was forward ported to the 2.3-develop branch.
If someone wants to take a stab at it, please do so :)

[m2-assistant[bot]]

Hi @AlexWorking. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!
  

• [ ] 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• [ ] 6. Add label Issue: Confirmed once verification is complete.

• [ ] 7. Make sure that automatic system confirms that report has been added to the backlog.

[AlexWorking]

Issue is really reproduced only on 2.3-develop (fixed on 2.2-develop). Steps to Reproduce here have been slightly modified: there has been added an additional step number 3. Without it the issue won't reproduce - if You start to create a new bundle product and instead of Save You click Save and Duplicate everything will work as expected, e.g. two bundle products with the same bundle option will be created.

[magento-engcom-team]

:white_check_mark: Confirmed by @AlexWorking
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-99840 were created

Issue Available: @AlexWorking, _You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself._

[Goeny]

Why is this issue still not resolved?

How can i implement a manual fix in either 2.3.1 or 2.3.2 ?

[macrodesignuk]

@magento-engcom-team @magento-team
Why has this fix not been applied to the official Magento release yet? The fix works.

I recently updated to 2.3.2 which caused Magento to revert back to the old broken version and overridden my manual file fix.

[hostep]

@macrodesignuk, or somebody else: can you create a pull request with the suggested fixes, it will be much quicker integrated in Magento that way than endlessly waiting for Magento core devs to finally take a look at this. Thanks! 🙂

[macrodesignuk]

@macrodesignuk, or somebody else: can you create a pull request with the suggested fixes, it will be much quicker integrated in Magento that way than endlessly waiting for Magento core devs to finally take a look at this. Thanks!

Thanks Pieter, I just tried to fork it and the related file is completely different in the fork copy to that of the official release. It looks like somebody has rewritten the fix, but it is significantly different. Not sure what to do in this case.

[hostep]

Hi @macrodesignuk, I just created a PR for this at https://github.com/magento/magento2/pull/24703

It wasn't very difficult, just cherry-picked the two commits mentioned above on the 2.3-develop branch, which applied cleanly, had no conflicts to solve.

[macrodesignuk]

@hostep Thanks,

The reason I didn't do it was because the version that they give on the released version of Magento is not the same as in that development branch. Therefore its not patching the same file and could cause a problem. Hopefully it all works out though, thank you for your help

[magento-engcom-team]

Hi @MattUnity. Thank you for your report.
The issue has been fixed in magento/magento2#24703 by @hostep in 2.3-develop branch
Related commit(s):

• f1a187eba85b2eaeca4c619c1482ca8916fdb284
• bf36defe362496ecb6f6b7693600a9054fbd801b
• 629fcdfc22c35ce0cc2f3732b54b9885e8b2b362

The fix will be available with the upcoming 2.3.4 release.