mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-09 03:09:38 +03:00
WYSIWYG editor not opening #2679
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wforumw on GitHub (Feb 27, 2022).
Attempted Debugging
Searched GitHub Issues
Describe the Scenario
After update from v21.12.5 to v22.02 it seems that the WYSIWYG editor does not work anymore.
Everything works except if I create a new page or edit an existing page the page stays empty an no editor is seen.
If I change in the setting to 'markdown' I can edit a page or create a new one.
Exact BookStack Version
v22.02
Log Content
Nothing found in the error log
Also no error produced
PHP Version
7.4.28
Hosting Environment
Debian Bullseye
@SmokingCrop commented on GitHub (Feb 27, 2022):
I have the same issue, opening up the browser Console gives an error (on editing a page where the WYSIWYG editor does not open):
Uncaught TypeError: Cannot read properties of undefined (reading 'registry')
at eN.setup (app.js:47:1295)
at eN.execCallback (tinymce.min.js:2:343879)
at new eN (tinymce.min.js:2:343292)
at n (tinymce.min.js:2:353313)
at Array. (tinymce.min.js:2:354874)
at jt (tinymce.min.js:2:29356)
at Object.e (tinymce.min.js:2:354723)
at C (tinymce.min.js:2:10800)
at d (tinymce.min.js:2:10946)
at a (tinymce.min.js:2:10124)
(PHP version 7.4.3 | Ubuntu 20.04.4 LTS without GUI)
(Reverted back to previous checkpoint)
@ssddanbrown commented on GitHub (Feb 27, 2022):
Does this issue remain after a hard refresh? (Shift+R) or (Ctrl+Shift+R)
@SmokingCrop commented on GitHub (Feb 27, 2022):
Ah, this fixed it for me 👍
@wforumw commented on GitHub (Feb 27, 2022):
Thanks!! This fixed it for me
@ssddanbrown commented on GitHub (Feb 27, 2022):
Thanks both for confirming. I usually update references for the editor script to force caches to be broken but forgot to do that for this release. Have tweaked this for our next patch release so users don't have to manually perform a hard refresh.