-
Bug
-
Resolution: Fixed
-
High
-
None
-
OnDemand
It turns out that some customers have pages that contain multiple contentLayout divs. Since the OnDemand upgrade from Confluence 5.2-OD-5 to 5.2-OD-13, these pages no longer behave like they used to and are missing content when rendered (either for viewing or editing).
Inspecting the document storage format, the content is all still there. It might look like this, where only the content in the final contentLayout div is rendered:
<div class="contentLayout" ...> (content that is NOT rendered) </div> <div class="contentLayout" ...> (content that is rendered) </div>
or this, where nothing on the page is rendered:
<div class="contentLayout" ...> <div class="contentLayout" ...> <div class="innerCell"> (content is here but not rendered)
These duplicate contentLayout divs should be cleaned up by the editor on the fly so that the content will be displayed. OnDemand customers have no way to edit the storage format data directly on their own.
- is related to
-
-
- Closed
-
- relates to
-
-
- Closed
-
- mentioned in
-
Wiki Page Failed to load
-
Page
Failed to load
-
Wiki Page
Failed to load
-
Wiki Page Loading...
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CONFCLOUD-54549] Pages with unexpected page layout (contentlayout) structure no longer have some content rendered
Don't know if this is related to this issue, but it started happening at the same OD refresh. Preview of pages with section/column macro type pages (that I use a lot 
) does not show the multiple columns. It is ok once saved, but then what is the point of doing a preview 
.
I've changed the title from "Pages with multiple contentLayout divs no longer have some content rendered".
The initial handling code for displaying pre-5.2 page layouts in 5.2 was naïve.
It assumed the structure of contentLayout, header, footer, columnLayout, cell, innerCell divs would be as described in https://confluence.atlassian.com/display/CONF51/Confluence+Storage+Format#ConfluenceStorageFormat-Pagelayouts
However, that structure is unenforced, and page structure can quite easily become rearranged by browser/editor quirks during operations such as copy/paste.
At least two customers have had pages where the innerCell div ended up directly within a contentLayout div. This is fixed in 5.2. A variety of other unexpected structures will be fixed in the next OnDemand release, and in Confluence 5.2.1.
We've noticed thus far that the unstructured data included having two top-level contentLayout divs. However, that particular unexpected structure is not actually the problem, although its occurrence may have very high correlation with problematic content. Pages can have two contentLayouts and be displayed correctly. And pages could have only one contentLayout but not display correctly.
If customers find instances of pages being incorrectly displayed due to this bug, please contact Atlassian Support via http://support.atlassian.com so we can confirm that:
- support can fix your page;
- we can confirm the fixed code correctly handles your page
Hi bob.swift@charter.net,
It's unlikely to be the same issue. There were some recent changes in the layout plugin to make the sections and columns divs instead of tables. I've reproduced the issue and it's very consistent. I'll file another bug for it.
Thanks,
Don