Details
-
Bug
-
Resolution: Fixed
-
Low
-
7.7, 7.13.0, 7.19.0
-
None
-
1
-
Severity 3 - Minor
-
Description
Issue Summary
The 'frontend.editor.v4.disable' dark feature is for customers that want to fall back to the legacy editor (v3). After Confluence 7.7, codes for this legacy editor is removed. So, applying the 'frontend.editor.v4.disable' parameter to the Confluence for version 7.7 and higher, causes Confluence Editing to break as there is no v3 editor anymore for these versions.
For the versions that do not have v3 editor code, Confluence should not accept this parameter (or not trigger anything even if it is applied).
This is reproducible on Data Center: yes
Steps to Reproduce
- Install Confluence 7.7 or higher version
- Navigate to '<Confluence-base-URL>/admin/darkfeatures.action'
- Apply 'frontend.editor.v4.disable' to the Site Dark Features section
- Try to edit a page
Expected Results
Page editor can be loaded successfully and you can edit the page.
Actual Results
The page editor is not loaded successfully and you can't edit the page.
Errors similar to the below ones are thrown in the Console of the browser's Developer Tools:
batch.js?gatekeeper-ui-v2=true&healthcheck-resources=true&highlightactions=true&hostenabled=true&locale=en-GB&user-logged-in=true:2555 Uncaught TypeError: a.on is not a function at Editor.onInitialise (batch.js?gatekeeper-ui-v2=true&healthcheck-resources=true&highlightactions=true&hostenabled=true&locale=en-GB&user-logged-in=true:2555:224) at Editor.execCallback (batch.js?gatekeeper-ui-v2=true&healthcheck-resources=true&highlightactions=true&hostenabled=true&locale=en-GB&user-logged-in=true:1821:130) at new Editor (batch.js?gatekeeper-ui-v2=true&healthcheck-resources=true&highlightactions=true&hostenabled=true&locale=en-GB&user-logged-in=true:1790:6) at Array.<anonymous> (batch.js?gatekeeper-ui-v2=true&healthcheck-resources=true&highlightactions=true&hostenabled=true&locale=en-GB&user-logged-in=true:1782:3) at each (batch.js?gatekeeper-ui-v2=true&healthcheck-resources=true&highlightactions=true&hostenabled=true&locale=en-GB&user-logged-in=true:1514:357) at g (batch.js?gatekeeper-ui-v2=true&healthcheck-resources=true&highlightactions=true&hostenabled=true&locale=en-GB&user-logged-in=true:1781:121) at Object.init (batch.js?gatekeeper-ui-v2=true&healthcheck-resources=true&highlightactions=true&hostenabled=true&locale=en-GB&user-logged-in=true:1782:262) at Object.initialise (batch.js?gatekeeper-ui-v2=true&healthcheck-resources=true&highlightactions=true&hostenabled=true&locale=en-GB&user-logged-in=true:2815:227) at Array.<anonymous> (batch.js?gatekeeper-ui-v2=true&healthcheck-resources=true&highlightactions=true&hostenabled=true&locale=en-GB&user-logged-in=true:2522:262) at c (batch.js?locale=en-GB:44:22895)
Uncaught TypeError: Cannot read properties of undefined (reading 'activeEditor') at Object.getEditor (batch.js?build-number=8804&gatekeeper-ui-v2=true&healthcheck-resources=true&highlightactions=true&hostenabled=true&locale=en-GB&tc-license-setup=true&user-logged-in=true:1766:427) at e (batch.js?build-number=8804&gatekeeper-ui-v2=true&healthcheck-resources=true&highlightactions=true&hostenabled=true&locale=en-GB&user-logged-in=true:5157:251) at Object.activateEditor (batch.js?build-number=8804&gatekeeper-ui-v2=true&healthcheck-resources=true&highlightactions=true&hostenabled=true&locale=en-GB&user-logged-in=true:5163:372) at Object.activateEditor (batch.js?build-number=8804&gatekeeper-ui-v2=true&healthcheck-resources=true&highlightactions=true&hostenabled=true&locale=en-GB&user-logged-in=true:5194:407) at HTMLAnchorElement.activateEventHandler (batch.js?build-number=8804&gatekeeper-ui-v2=true&healthcheck-resources=true&highlightactions=true&hostenabled=true&locale=en-GB&user-logged-in=true:5193:119) at HTMLAnchorElement.dispatch (batch.js?locale=en-GB:137:3915) at v.handle (batch.js?locale=en-GB:137:2004)
Workaround
The 'frontend.editor.v4.disable' parameter needs to be removed from the <Confluence-base-URL>/admin/darkfeatures.action page manually.