-
Bug
-
Resolution: Fixed
-
Low
-
6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.0.6, 6.0.7
-
3
-
Severity 2 - Major
-
Summary
Per Developer Escalation creating this defect for a problem that occurs when a Page Properties report on a grandchild Page contains an embedded JIRA macro. The ultimate parent page will be thrown into a continuously refreshing loop, and we are unable to stop the loop from occurring without forcing the browser to stop.
Steps to Reproduce
- Create a new Confluence 6.0.6 instance
- Add the demo site content and a local admin account
- Import the attached Space Export se2.zip into the newly created Confluence 6.0.6 site
- Perform a Content Indexing administration for the site
- Navigate to <yourConfleunceURL>/display/TS2/Page+Properties+testing
- Observe the page in a continuous loop as the Page Properties report in a grandchild page has a JIRA issues gadget in the report
- Observe that you can not stop the page from looping by clicking links, the back button or other methods
- Quit your browser
- Reopen your browser
- Go to <yourConfluenceURL>/display/TS2/Summary+of+BLUE+Child+Pages
- Remove the JIRA Gadget in the report for Blue page 1, with JIRA Gadget
- Navigate back to <yourConfleunceURL>/display/TS2/Page+Properties+testing
- Observe that the page looping is no longer present
Expected Results
Page Properties reports would display without issue and the page would render normally.
Actual Results
Page becomes stuck in a loop, and continues to attempt to render the reports - refreshing the page continuously and appending to the page URL with each attempt. The only way to stop the rendering is to force the browser to stop the attempt by manual intervention.
Workaround
The only workaround at present is to insure that JIRA macros are only embedded at the Child Page level and no deeper than the child level, or the looping will occur.
- is a regression of
-
CONFSERVER-40499 Page properties report broken when using nested macros.
- Closed
- relates to
-
CONFSERVER-40154 "Content by label" can render itself recursively, causing a stack overflow
- Closed