magento / magento2

Prior to making any Submission(s), you must sign an Adobe Contributor License Agreement, available here at: https://opensource.adobe.com/cla.html. All Submissions you make to Adobe Inc. and its affiliates, assigns and subsidiaries (collectively “Adobe”) are subject to the terms of the Adobe Contributor License Agreement.
http://www.magento.com
Open Software License 3.0
11.56k stars 9.32k forks source link

Impossible to edit a Widget with PageBuilder after it is saved once #37564

Closed vbidou closed 1 year ago

vbidou commented 1 year ago

Preconditions and environment

Steps to reproduce

  1. Navigate to Content on Back-End (for example Home page)
  2. Open Page Builder
  3. Create a ProductsList widget.
  4. Save it and exit.
  5. Re-enter the PageBuilder.
  6. Try to edit the Widget.

Expected result

When mouseover the widget section the menu to Edit should appear.

Actual result

No Edit menu appears on mousover the widget section.

Additional information

No response

Release note

No response

Triage and priority

m2-assistant[bot] commented 1 year ago

Hi @vbidou. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

m2-assistant[bot] commented 1 year ago

Hi @engcom-Bravo. 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:

engcom-Bravo commented 1 year ago

@magento give me 2.4-develop instance

magento-deployment-service[bot] commented 1 year ago

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

magento-deployment-service[bot] commented 1 year ago

Hi @engcom-Bravo, here is your Magento Instance: https://9b08eb313452b52526e43da201766bac.instances-prod.magento-community.engineering Admin access: https://9b08eb313452b52526e43da201766bac.instances-prod.magento-community.engineering/admin_84c3 Login: 8efdc09b Password: 8c2a14a98d1a

vbidou commented 1 year ago

I tested on your Magento instance server and the widget seems to work... image

On my Magneto 2.4.6, here is what I see... image

vbidou commented 1 year ago

For information, the widgets which doesn't show are from this section of PageBuilder: image

engcom-Bravo commented 1 year ago

Hi @vbidou,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the attached video.

Steps to reproduce

When mouseover the widget section the menu to Edit section is appeared successfully.

https://github.com/magento/magento2/assets/51680745/4e6282d3-4c69-46fc-a826-20e5ddf943a0

Kindly recheck the behaviour on Magento 2.4-develop instance and elaborate steps to reproduce if the issue is still reproducible.

it is recommended to verify the issue on Magento 2.4-develop instance as it is an upcoming 2.4.x release and have latest code base. Thanks.

vbidou commented 1 year ago

Update: The issue happened after switching Magento from Production mode to developper mode. As we can't replicate the issue, we are recovering backup to better understand the root cause.

engcom-Bravo commented 1 year ago

Thanks for your contribution & collaboration over here @jerry32410

Hi @vbidou,

Thanks for your update.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

We have checked after switching Magento from Production mode to developper mode.

Screenshot 2023-06-05 at 3 08 23 PM Screenshot 2023-06-05 at 3 06 21 PM

Kindly recheck the behaviour on Magento 2.4-develop instance and elaborate steps to reproduce if the issue is still reproducible.

Thanks.

vbidou commented 1 year ago

Dear Team, After long and deep investigations, we have identified that the issue was due to 2 aheadworks extensions which affected the pagebuilder javascript. The issue was pushed to their dev department for a fix. This iussue can be marked as resolved for now. Thanks for your support in determining that it is not a core Magento script issue. Best regards