Pagebuilder appears empty in blocks although there is data already stored!

[cptX]

Preconditions and environment

• Magento version 2.4.7-p3

Steps to reproduce

Don't know the root cause of this. I have 10 blocks and when I tried to edit them the pagebuilder was appearing empty! In the frontend the blocks appear correctly! I also checked the database and the data of these blocks still exist. This happens to all blocks!
Also If I try to edit a product the pagebuilder allows editing the content as expected, so it looks like this happens only in blocks!

Trying to solve the issue, I have cleared all caches, reindex, then put it in dev mode and back to production to trigger all processes to regenerate files, but nothing changed. I didn't change anything recently as far as I remember to trigger this!

If I try to add a new row in the empty pagebuilder and save, the previous data of that block are now deleted from the database!

Please help, I'm unable to edit the contents of my blocks and I need to do so urgently!

If this helps I have another test site in the same server that still works as expected. Maybe is useful for comparisons.

Expected result

Editing the contents of blocks with pagebuilder.

Actual result

Pagebuilder appears empty in all blocks, although there is data stored in database for these blocks.

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]

Hi @cptX. 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.

• 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.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 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.

[m2-assistant]

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: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - 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.

[m2-assistant]

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

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - 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-November]

Hello @cptX ,

Thank you for the report and your collaboration.

We attempted to reproduce the reported issue on our latest 2.4 development instance, but were unable to replicate it. For your reference, please find the attached screenshot for reference.

Could you kindly recheck on your end and let us know if the issue still persists? Additionally, please let us know if there are any specific steps or conditions we might be missing that could help us reproduce the issue accurately.

Hence marking this issue as "Needs Update"

Thank you once again!