-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
6.2.3, 6.8.1
-
15
-
Severity 2 - Major
-
4
-
Summary
When creating a page with both Cache for Confluence (7.8.0) and Refined Themes for Confluence (6.0.6) apps installed, page is not loaded properly and a "Maximum call stack size exceeded" error is thrown.
Steps to reproduce:
- Spawn a Confluence Server 6.2.3
- Install Cache for Confluence (7.8.0) and Refined Themes for Confluence (6.0.6) apps
- Set Refined Themes as Site theme (General Configuration -> Site Theme -> Confirm setting Refined Theme)
- Create a page with Future macro, and inside it, a Code block macro with Java as highlight (as per screenshot)
- Publish the page and it's an eternal "Loading app.." with error:
Uncaught RangeError: Maximum call stack size exceeded at String.replace (shCore.js?locale=en-GB:1) at RegExp.<anonymous> (resource-init-bundle.js?data-wrm-batch-type=resource&data-wrm-key=com.refinedwiki.confluence.plugins.theme.original%3Acore-resources&locale=en-GB:7384) at String.replace (<anonymous>) at String.replace (shCore.js?locale=en-GB:173) at RegExp.<anonymous> (resource-init-bundle.js?data-wrm-batch-type=resource&data-wrm-key=com.refinedwiki.confluence.plugins.theme.original%3Acore-resources&locale=en-GB:7384) at String.replace (<anonymous>) at String.replace (shCore.js?locale=en-GB:173) at RegExp.<anonymous> (resource-init-bundle.js?data-wrm-batch-type=resource&data-wrm-key=com.refinedwiki.confluence.plugins.theme.original%3Acore-resources&locale=en-GB:7384) at String.replace (<anonymous>) at String.replace (shCore.js?locale=en-GB:173)
Notes:
- Issue does not occur for Confluence 6.10.0
- mentioned in
-
Page No Confluence page found with the given URL.
- relates to
-
DEVHELP-1521 Failed to load
Just observed this on Confluence Data Center 7.19.12 LTS. Culprit was a "Code Macro" embedded on a page. Page become un-editable on Chromium based browsers (Chrome, MS Edge), Firefox still behaved normal. Replacing the Code-Macro by a Panel-Macros solved the issue.
Not clear yet if this might be also triggered by an interference with one of our Apps installed. However, we are definitively not using Refined Theme, so it might be a different one ...