-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
[Issue] Restores backwards compatibility with TinyMCE plugins again (after it… #39262
Comments
Hi @engcom-Hotel. Thank you for working on this issue.
|
Hello @hostep, Thanks for the report and collaboration! We have tried to reproduce the issue in the latest 2.4-develop branch and the issue is reproducible for us. Please refer to the below screenshot for reference: Hence confirming this issue. Thanks |
✅ Jira issue https://jira.corp.adobe.com/browse/AC-13569 is successfully created for this GitHub issue. |
✅ Confirmed by @engcom-Hotel. Thank you for verifying the issue. |
This issue is automatically created based on existing pull request: #39258: Restores backwards compatibility with TinyMCE plugins again (after it…
… broke with introduction of TinyMCE7).
Description (*)
Magento comes with 2 new TinyMCE plugins by default:
Recently, with the switch from TinyMCE v5 to v7 in the latest security patch releases (2.4.7-p3, ...) and 2.4.8-beta1, those plugins got rewritten to adhere to the new system in TinyMCE 7. However, a big mistake was made by not returning the widgets as an object, which meant that you couldn't call the functions defined inside the plugin anymore when trying to use the widget from another location.
Example with magentowidget, old version vs new version, note that in the new version there is no object being returned in that
magentowidget
function anymore.This resulted in this error output when trying to call the
encodeWidgets
on themagentowidget
instance, because that last one was just an empty object:This PR fixes that.
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
That last step will fail and you'll see an error in your browser's console. This PR fixes this issue.
Questions or comments
Adding automated tests for this will be hard, so I'm not doing it, hopefully that's okay, if not, please write them yourselves, I won't have the time to put into this task.
Contribution checklist (*)
The text was updated successfully, but these errors were encountered: