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

Doesn't appear to be working anymore with TinyMCE 7 #54

Open
hostep opened this issue Oct 11, 2024 · 1 comment
Open

Doesn't appear to be working anymore with TinyMCE 7 #54

hostep opened this issue Oct 11, 2024 · 1 comment

Comments

@hostep
Copy link
Contributor

hostep commented Oct 11, 2024

After upgrading Magento from 2.4.7-p2 to 2.4.7-p3 (which comes with a upgrade of TinyMCE 5 to 7, what were they thinking 🙄), if you open a cms page that already has content in the backoffice and then open the 'Content' tab, the page designer fails to initialise properly and we see this error message in the console:

Uncaught (in promise) TypeError: tinymce.activeEditor.plugins.magentowidget.encodeWidgets is not a function
    at mageWidgetEncode (page_designer.js:35:63)
    at Object.<anonymous> (page_designer.js:373:69)
    at Function.each (jquery.js:383:35)
    at jQuery.fn.init.each (jquery.js:205:27)
    at Object.<anonymous> (page_designer.js:370:40)
    at Function.each (jquery.js:383:35)
    at jQuery.fn.init.each (jquery.js:205:27)
    at pageDesigner.importWithPreviews (page_designer.js:369:34)
    at UiClass.<anonymous> (page_designer.js:112:35)
    at page_designer.js:88:29

I know that you guys no longer support this module, but I'm getting quite desperate as some of our clients do still have this module installed and now no longer can edit their content anymore after the latest security patch update of Magento.

Can somebody give me a hint if this would be easily solvable?
We already tried for 2-3 hours with 2 persons to figure out a solution to fix this in code, but we are failing hard.
Some hints would be greatly appreciated.

Many thanks! :)

@hostep
Copy link
Contributor Author

hostep commented Oct 13, 2024

Found the problem, it's a bug introduced in some Magento code: magento/magento2#39258

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant