Skip to content
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

Broken pagebuilder after saving #39663

Closed
5 tasks
fenneyachtsupplier opened this issue Feb 27, 2025 · 4 comments
Closed
5 tasks

Broken pagebuilder after saving #39663

fenneyachtsupplier opened this issue Feb 27, 2025 · 4 comments
Assignees
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.x Indicates original Magento version for the Issue report.

Comments

@fenneyachtsupplier
Copy link

Preconditions and environment

Hello, I need urgent help with the following issue regarding magento 2 pagebuilder
I was editing a page in pagebuilder and I put css code into the source code of a text element. After done this I saved the page and now the whole pagebuilder is broken and i cannot access and/or edit the page builder. The page does still work on the website but i am not able to save or change anything. It was a pge in which a lot of work was put.

Is someone able to help me with the steps to be able to recover this page or maybe undo the saving of the page so it will be reset to an earlier version before saving the css code that was put into the text segment?

This image shows how the pagebuilder looks like right now:
Image

With regards,

Fenne
Yachtsupplier B.V.

Steps to reproduce

Expected result

Actual result

Additional information

Release note

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”.
Copy link

m2-assistant bot commented Feb 27, 2025

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


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.

@engcom-Bravo engcom-Bravo self-assigned this Feb 27, 2025
Copy link

m2-assistant bot commented Feb 27, 2025

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.

@engcom-Bravo engcom-Bravo added the Reported on 2.4.x Indicates original Magento version for the Issue report. label Feb 27, 2025
@github-project-automation github-project-automation bot moved this to Ready for Confirmation in Issue Confirmation and Triage Board Feb 27, 2025
@engcom-Bravo engcom-Bravo pinned this issue Feb 28, 2025
@engcom-Bravo engcom-Bravo unpinned this issue Feb 28, 2025
@engcom-Bravo
Copy link
Contributor

Hi @fenneyachtsupplier,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Image

we are able to save the page with CSS and able to access and edit the page successfully.

Kindly recheck the issue in Latest 2.4-develop instance and elaborate the steps to reproduce if the issue is still reproducible.

Thanks.

@engcom-Bravo engcom-Bravo added the Issue: needs update Additional information is require, waiting for response label Feb 28, 2025
@engcom-Bravo engcom-Bravo moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board Feb 28, 2025
@engcom-Bravo
Copy link
Contributor

Hi @fenneyachtsupplier,

This issue is being closed since it has not been updated in a long time.Please feel free to reopen or raise a new ticket if the issue still exists.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.x Indicates original Magento version for the Issue report.
Projects
None yet
Development

No branches or pull requests

2 participants