With the release of Magento version 2.4.7, a significant issue was discovered affecting the functionality of WYSIWYG (What You See Is What You Get) editors. When there are multiple editors on the same page, only the first one functions correctly — the others may have issues displaying content or saving the entered data. As a result, only the content of the first field is saved, while the others remain empty.
This error limits the editing capabilities of content in various modules that use the WYSIWYG editor and creates significant inconvenience for site administrators. The problem is specific to Magento version 2.4.7. and does not occur in previous versions, where the functionality works stable.
Causes and Consequences
The problem arose due to the optimization and restructuring of the JavaScript code, which was changed in Magento version 2.4.7.
Here are the key indicators of this error:
- Incorrect content saving: When multiple fields with a WYSIWYG editor in Magento 2.4.7 are located on the page, the data can be saved only in the first editor. The others remain empty after an attempt to save them.
- Broken/missing WYSIWYG editor elements: Some elements of the editor interface may not display properly or may even be missing, including the “Show/Hide Editor” button.
These WYSIWYG issues in Magento 2.4.7 affect the workflow of Plumrocket extensions as well. Here’s the full list of extensions that have WYSIWYG editors and may be affected:
- AMP
- AMP Email
- Call For Price
- Checkout Success Page
- Coming Soon & Maintenance Page
- Cookie Consent
- Estimated Delivery Date
- GDPR
- Google Page Speed Optimizer
- Hide Price
- LGPD
- Newsletter Popup
- Returns & Exchanges (RMA)
- Size Chart
- Social Login Pro
- Splash Page
- US Privacy Laws
How to Fix the Magento 2.4.7 WYSIWYG Not Working Issue
The Magento team has confirmed the existence of this WYSIWYG issue and has already started working on a solution. More details on the error discussion can be found on Magento GitHub Issue #38622. In the future, a patch is expected to be issued officially to fix this bug.
In order to avoid unpleasant consequences and keep WYSIWYG editors working correctly and efficiently, the Plumrocket team has developed a temporary solution — the extension that fixes the WYSIWYG issue in Magento 2.4.7 and ensures the editors are functioning correctly.
The extension is publicly available and can be downloaded from the Plumrocket GitHub repository:
Important Information:
The WYSIWYG fix extension can be used both independently and with Plumrocket extensions.