-
Bug
-
Resolution: Fixed
-
Highest
-
7.4.6, 7.4.7, 7.4.8, 7.4.11, 7.7.4, 7.8.1, 7.8.3, 7.9.0, 7.9.1, 7.11.2
-
58
-
Severity 2 - Major
-
540
-
Issue Summary
Confluence generates attachment xml with <ri:content-entity content-id="..."> that renders as an unknown attachment. When it happens, it affects the whole page, probably multiple pages.
Example:
<p> <ac:image> <ri:attachment ri:filename="image2020-10-21_12-40-38.png"> <ri:content-entity ri:content-id="138910055"/> </ri:attachment> </ac:image> </p>
Steps to Reproduce
Not known yet.
Expected Results
Attachment is rendered correctly.
Actual Results
Attachment is rendered as an unknown attachment.
Workaround 1
Reindex fixes the issue.
Workaround 2
Alternatively one can manually remove <ri:content-entity ri:content-id="..."/> inside <ri:attachment> tag using source editor plugin - that also seems to fix it, though much less convenient.
- is related to
-
CONFSERVER-63615 Provide workaround for fixing broken unknown attachment placeholder in storage format
- Closed
-
CONFSERVER-63700 Provide workaround for fixing unknown attachment placeholder with ri:content-entity
- Closed
-
CONFSERVER-65151 Prevent Confluence to generate storage format which has a attachment with ri:content-entity of a draft
- Closed
- relates to
-
CONFSERVER-55928 Attachments become 'Unknown Attachment' in the page editor with Collaborative Editing turned on
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...