-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
5.8.16
-
Tomcat app server; JDK version jdk1.8.0_60; RHEL 7 OS
When editing the same page by two people in two different browsers, it appears that a few macros break upon save, even if they/their section of the page was never edited.
For example, I create a new page from the out-of-box Product Requirements Confluence template*. Save page. Now I edit the page, while in edit mode, a colleague also edits that page. He saves (macro appears as it should). Now I save (now the macro is broken). The typical flow and correct flow is that if the same section/piece were edited by both people, the second person to save would receive a merge conflict notification. If both people edited different sections then no conflict arrises and it saves fine.
However, in either case, no matter if the same section was edited or different sections were edited, the status macro (that comes with the template) now presents a "Broken Macro" error on the page for the second person who saves. When you edit the page, it still has that error; you have to delete it and re-insert the macro. This same behavior occurs with the Column macro inside the section macro. This behavior did not occur with the Section macro itself, but once the Column macro was inside the Section macro, it then produced the same "Broken Macro" error.
This was tested in Safari and Chrome, producing the same results.
*Note: the Product Requirements template was only used as an example. This same error occurs even from creating standard Blank Pages.
Error log attached.
- duplicates
-
CONFSERVER-40988 Macro within another macro is broken after the second user saves the page
-
- Closed
-
[CONFSERVER-42768] Macros break in concurrent editing/saving
Workflow | Original: JAC Bug Workflow v3 [ 2890081 ] | New: CONFSERVER Bug Workflow v4 [ 2982469 ] |
Workflow | Original: JAC Bug Workflow v2 [ 2803638 ] | New: JAC Bug Workflow v3 [ 2890081 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Bug Workflow [ 2737251 ] | New: JAC Bug Workflow v2 [ 2803638 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2385913 ] | New: JAC Bug Workflow [ 2737251 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2282341 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2385913 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2223204 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2282341 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2174627 ] | New: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2223204 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 1943763 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2174627 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v3 [ 1738051 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 1943763 ] |
FYI - I'm on Confluence 6.0.7 and we have this same issue. Running on RHEL 6.8/JDK 1.8.0.66