Unable to add full description during product creation with page builder enabled

[engcom-November]

Preconditions and environment

2.4-develop Page builder enabled

Steps to reproduce

1. Login to admin and create new product
2. Expand Content - Full Description - Edit with Page builder
3. Drag and drop any Layouts

Expected result

Able to add the content

Actual result

Unable to drag and drop any of the pagebuilder layouts and add content

Additional information

No response

Release note

No response

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @engcom-November. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant[bot]]

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:

• [ ] 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.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.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. Add label Issue: Confirmed once verification is complete.

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

[engcom-Bravo]

Hi @engcom-November,

Thank you for reporting and collaboration.Verified the issue on Magento 2.4-develop branch and the issue is reproducible.

I have updated the Description with a video.

Hence confirming the issue.

Thanks.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-6743 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[konarshankar07]

@magento I am working on this

[engcom-November]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

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

[magento-deployment-service[bot]]

Hi @engcom-November, here is your Magento Instance: https://72102ebd138ec104e3864d40a81d9408.instances.magento-community.engineering Admin access: https://72102ebd138ec104e3864d40a81d9408.instances.magento-community.engineering/admin_b6dc Login: 1b10a3b2 Password: e364810ba854

[nishant04412]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @nishant04412. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @nishant04412, here is your Magento Instance: https://72102ebd138ec104e3864d40a81d9408.instances.magento-community.engineering Admin access: https://72102ebd138ec104e3864d40a81d9408.instances.magento-community.engineering/admin_1986 Login: ec3dddbb Password: 817ee089043d

[hostep]

@engcom-Bravo: what was the reason for closing this? Please always specify a reason when closing issues in the future, otherwise it's confusing the people who watch the ticket.

/cc @sdzhepa (this closing of issues without specifying a reason happens way too often over here, please talk to all people that do this so it no longer happens, thanks!)

[github-jira-sync-bot]

:x: Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-6743

[vandijkstef]

I'm not sure, but this might possibly be related to #36051

[AshishKumarPundeer]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @AshishKumarPundeer. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @AshishKumarPundeer, here is your Magento Instance: https://72102ebd138ec104e3864d40a81d9408.instances.magento-community.engineering Admin access: https://72102ebd138ec104e3864d40a81d9408.instances.magento-community.engineering/admin_bb9e Login: 8ac41d91 Password: ec8723d141a2

[AshishKumarPundeer]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @AshishKumarPundeer. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @AshishKumarPundeer, here is your Magento Instance: https://72102ebd138ec104e3864d40a81d9408.instances.magento-community.engineering Admin access: https://72102ebd138ec104e3864d40a81d9408.instances.magento-community.engineering/admin_36a1 Login: 0de33158 Password: a1e7ae290890

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

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

[magento-deployment-service[bot]]

Hi @engcom-Bravo, here is your Magento Instance: https://72102ebd138ec104e3864d40a81d9408.instances.magento-community.engineering Admin access: https://72102ebd138ec104e3864d40a81d9408.instances.magento-community.engineering/admin_e7e5 Login: 9a858d37 Password: 69f17fbdd821

[AshishKumarPundeer]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @AshishKumarPundeer. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @AshishKumarPundeer, here is your Magento Instance: https://72102ebd138ec104e3864d40a81d9408.instances.magento-community.engineering Admin access: https://72102ebd138ec104e3864d40a81d9408.instances.magento-community.engineering/admin_e341 Login: 4e5b4d1e Password: 42359d1593f1

[engcom-Alfa]

As @AshishKumarPundeer and other internal team - tried to reproduce in the 2.4-develop Magento instance (Installed via Git clone), the issue is not reproducible at all. - tried to reproduce in the internal Magento cloud instance with the version 2.4.5. Only it is reproducible with the instance that is deployed via Github bot's 2.4-develop instance.

We will not be able to debug as we don't have issue reproducible in our local instance and Github cloud instance code base doesn't support to install in our local. On which note, it clarifies that, due to some of the internal installation procedures, we might be getting this issue! Let's this set to P3 as of now, and re pick up in case of more relevant observation found from different users! Thanks! cc: @engcom-Hotel @engcom-Bravo