Skip to content

Legacy HTML content is imported to Page Builder as HTML code, not a Text element #38844

Open
@adamlavery

Description

@adamlavery

Summary

Prior to Page Builder, all rich content was managed with the TinyMCE editor. Essentially it is stored as constrained raw HTML and presented for visual editing. If we enable Page Builder then all legacy content is imported as HTML code. Given legacy content is just HTML that could be edited in TinyMCE, what has it not been imported as a Text element? What was the rationale behind this?

That way legacy content could continue to be managed as the single text block it was previously. Only if enhanced layout is required would it need to be extended in Page Builder. As it stands, we cannot enable Page Builder for existing sites because then all rich content would have to be reimplemented in Page Builder for non-developer end-users to work on it.

Examples

Enable Page Builder on an existing site that hasn't used it before. All rich content is now HTML code and effectively non-editable by end users.

Proposed solution

Import legacy content as a single Text element, allowing it be managed as previously.

Release note

Better support for switching from legacy TinyMCE to Page Builder.

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area: ContentComponent: PageBuilderComponent: TinymceIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedPriority: P2A defect with this priority could have functionality issues which are not to expectations.Progress: ready for devReported on 2.4.7Indicates original Magento version for the Issue report.Reproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchTriage: Dev.ExperienceIssue related to Developer Experience and needs help with Triage to Confirm or Reject it

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions