-
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
-
- Closed
-
- Closed
- relates to
-
-
- Closed
-
-
![[Atlassian Support System]](/images/icons/generic_link_16.png "[Atlassian Support System]")
MOVE-1775529
You do not have permission to view this issue
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[CONFSERVER-60526] Confluence generates attachment xml with <ri:content-entity content-id="..."> that renders as an unknown attachment
A fix for this issue is available to Server and Data Center customers in Confluence 7.13.0
Upgrade now or check out the Release Notes to see what other issues are resolved.
Will this be backported to 7.4 LTS as well? I'm currently testing 7.4.9 which includes the first part of the fix (CONFSERVER-55928)
@zaphnet: thank you for that hint! I tested that and it worked
I believe that we also are affected by this problem, seems to be intermittent.
I think that we have another workaround: I think we have seen this happen when we start editing a page.
If you back out of that edit with "Revert to previously published" or previously correct page, and attempt a new edit it might work OK.
We are also affected by this problem. The only remedy is to manually adjust the source code using the Source Code Editor. We urgently need a solution to the problem here.
Affected Confluence version 7.4.6
We also have the issue. Major impact on the teams because there are a lot of case. In the source code we have now:
<ri:url ri:value="https://confluence.corporate.eu/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_US&version=2"/>
instead of an old version of the page that was not modified:
<img class="confluence-embedded-image" width="700" src="/download/attachments/14555272/image2020-8-10_10-59-28.png?version=1&modificationDate=1597049968526&api=v2" data-image-src="/download/attachments/14555272/image2020-8-10_10-59-28.png?version=1&modificationDate=1597049968526&api=v2" data-unresolved-comment-count="0" data-linked-resource-id="16813055" data-linked-resource-version="1" data-linked-resource-type="attachment" data-linked-resource-default-alias="image2020-8-10_10-59-28.png" data-base-url="https://confluence.corporate.eu" data-linked-resource-content-type="image/png" data-linked-resource-container-id="14555272" data-linked-resource-container-version="38" title="Security >
I suspected an effect of a migration from server to data-center but does not seems to be the case.
Re-index did not fix the issue.
We reproduced the issue when we move a page with attached images from one workspace to another one.
Confluence version: 7.10.1
Manual removing ri:content-entity tag from each attached image (using source editor plugin) fixes rendering problem.
We also did a "reindex from scratch" but this did not resolve the issue.
This is really a bigger issue. This happens randomly and we cannot reproduce the error.
In my case Atlassian support told me to reindex but it didn't work..
I guess i found something weird on my pages
The Page ID in the URL is /pages/viewpage.action?pageId=93135229
The Content-Entity is content-entity ri:content-id="93135230"
The workaround is --> Reindex fixes the issue **
How do I do that?
Have just faced that issue un a page, but I cannot tell, how to reproduce yet. However, removing the <ri:content-entity ri:content-id="..."/> entries helped. Looking forward to hear some more news about that.
A fix for this issue is available in Confluence Server and Data Center 7.4.16.
Upgrade now or check out the Release Notes to see what other issues are resolved.