Hi All,

d64ffd6b4aa8 - What b03c514954d7 has indicated is correct. I have a bit of an explanation of how the versions work in the comment section of this post Confluence Server and Data Center: Content duplication fix and next steps - Atlassian Community.

986c16497dab - Please review Confluence Server and Data Center: Content duplication fix and next steps - Atlassian Community to understand the fix and for next steps if you feel you're still encountering the bug.

We still haven't seen any new reports, but we'll keep looking to make sure.

Thanks,
James Ponting
Engineering Manager - Confluence Data Center

We are using 7.13.4. But the bug is still occurs. This fix not works

Mmm...

7.4.15 if you are using 7.4.x

7.13.4 if you are on 7.13.x

and 7.15 if you're doing a point upgrade

[Fix Version/s:   7.15.0, 7.4.15, 7.13.4]

Maybe but it says 7.4.15 & most of us are way past that version....

One might suppose that confirming the issue still occurs on a release that isn't fully patched would be expected, yes? Unless something changed, the issue is only confirmed fixed in 7.13.4.

We have 7.13.0 no attachments and it happens ...

Hi,

We use 7.13.2 version. I tried to simulate the bug with attachements but the content was not dulicated. It doesn't happen regularly and I couldn't find the root cause.

Best regards,

Raluca

Hi All,

We're still yet to see any signs of the issue recurring, but are continuing to monitor these issues and our normal support contact points.

986c16497dab - Can I please get you to review the Understanding The Fixes section of the community post. If you're still seeing the issue outside of the expectations detailed there, can you please capture the diagnostic information and submit a support ticket using the instructions on that page?

4dc555c60032 - Could you please also review the information just above? With regards to the plugins, our findings were that the plugins were calling the Atlassian code that caused the duplication behind the scenes. So you could end up with duplication without touching an attachment because a plugin would interact with the code in a similar way. With the fix implemented here, we should have resolved the issue in our code that the plugins were triggering. We don't believe the plugins to cause duplication, but rather trigger it.

Hopefully this helps clear some things up

Thanks,
James Ponting
Premier Support Engineer

Hi,

The bug still occurs in 7.13.4.
In case some plugins might be responsible for the persisting issue I would appreciate an information regarding problematic plugins.

Hi,

the fix of this bug with 7.13.4 has not been successful. Unfortunately. 
The bug also occurs  when the page has no attachment.

Hi, I can confirm the fix of this bug with 7.4.15.

Thanks!

Hi James,

Thanks for pointing this out.
The fix in 7.4.15 solved the problem for us, thanks

Hi All,

A couple of quick updates.

Firstly, we've released Confluence 7.4.15 with the included fix.

Once more, I'd encourage you to review the Understanding The Fixes section of the community post for additional information around the fix.

Additionally, just looping back to c3a01e534ba4's question

But I have one question: From your answer I can see that the problem is very complex and that you are not absolutely sure that the update will finally solve the problem. I would be interested to know if you will continue to work on this special bug when further development and bug fixing for Confluence server is officially discontinued on 15 February.

The long answer is we have committed to security bug fixes through to February 2024, and all of the details are available at Atlassian Data Center and Server Bug Fix Policy. This policy allows for additional bug fixes to be released, but isn't a commitment to provide them.

The short answer is that if we release a fix for this family of bugs for our Data Center customers, our server customers will also receive the fix. The fixes for our Data Center customers will be covered by the Bug Fix Policy listed above, as per normal.

Hopefully this helps clear up some things for everyone. Please let us know how you get on with the recently released fixes.

I'd be happy to hear some "so far so goods" as well

Thanks,
James Ponting
Premier Support Engineer

Hi All,

As qpham@atlassian.com has stated, we have release Confluence 7.13.4 with the included fix.

With the release of this fix, I'd once again encourage you to review the Understanding The Fixes section of the community post.

Please let us know how you get on

Thanks,
James Ponting
Premier Support Engineer

A fix for this issue is available to Server and Data Center customers in Confluence 7.13.4
Upgrade now or check out the Release Notes to see what other issues are resolved.

Hi All,

Just another quick update.

76d47cb436cb - No worries, glad it helped

c3a01e534ba4 had previously asked

But I have one question: From your answer I can see that the problem is very complex and that you are not absolutely sure that the update will finally solve the problem. I would be interested to know if you will continue to work on this special bug when further development and bug fixing for Confluence server is officially discontinued on 15 February.

I put the question to the relevant team and am yet to receive an official response, but want to share what I can. With the February 15 date approaching, all of the product and related teams are reviewing the plans and upcoming communication for this date. The request I made has been marked held until this review is complete, so I don't have an official answer just yet. As soon as the review is done, I'll make sure I get the answer out to you. I'll also add this information to the community post at Confluence Server and Data Center: Content duplication fix and next steps - Atlassian Community when it is available.

If you're chasing more information around the changes to our Server licenses, you can find additional information at the Atlassian Server End of Support Information page.

I'll update you all when I know more.

Thanks,
James Ponting
Premier Support Engineer

@jponting Thanks you for your explanation and the targeted dates. Now I have something to communicate and I can plan our server down-time. This helps a lot.

Hey All,

Just in reply to c3a01e534ba4's question.

This morning I escalated the question to the appropriate team to confirm the response. I'm still waiting to hear back from the team, I'll update you all when I receive their response.

Just to set expectations, tomorrow is a public holiday in Australia, so it will be at least another day before I get back to you.

Thanks,
James Ponting
Premier Support Engineer

Hi James,

Thank you very much for your detailed feedback. It's great that a solution is in sight.

But I have one question: From your answer I can see that the problem is very complex and that you are not absolutely sure that the update will finally solve the problem. I would be interested to know if you will continue to work on this special bug when further development and bug fixing for Confluence server is officially discontinued on 15 February.

Thanks for your answer.

Kind regards,
Hendrik

Hi All,

Just a quick update as promised.

76d47cb436cb - We definitely understand the frustration, and I think it would be fair to say that none of us are happy with the situation within which we find ourselves. Unfortunately there is a balance to be struck with LTS releases where we want to ensure everything we're releasing into the LTS is safe and doesn't introduce new issues. In this situation we completed a complex bug fix about two weeks before the release of the next LTS, and there was too much risk of introducing additional issues by forcing this complex fix into the LTS in such a short time period. The targeted versions are the very next LTS release, and we got the work done as promptly as we could. None of the options available to us were excellent, and all we can do is apologise for the experience you've had despite our best efforts.

We're currently aiming to release the fixed versions on the below dates. These are not concrete as we may need to push back the release if we find any problems during our pre-release testing which is currently underway.

• Confluence 7.4.15 - 16th February 2022
• Confluence 7.13.4 - 2nd February 2022

Understanding the Fixes

With backports for the most recent issue complete and awaiting release, I want to explain the impact these fixes will have. A version of Confluence that has the above fixes should not create new duplicated content. However, content that was already duplicated can still remain, due to how Confluence handles publishing of pages and the creation of drafts.

When a page is published, Confluence creates a new draft of the page in the background for easy access via the REST API, database etc. As some of the bugs cause content duplication in the page draft at the time of publication, this can lead to a situation where a page shows the expected content at the time of publishing, but in the background, the draft contains duplicated content. Next time someone edits the page, it appears as if the content duplication has just occurred, whereas the duplication actually occurred at the time of publishing, not editing. We call this stale duplication, and it may be present in your site after upgrading.

We’ve addressed all of the causes of duplication that we’ve been able to identify so far, and will continue to monitor for fresh content duplication reports from the community in case there are additional causes that we’ve not yet identified. Unfortunately, we have not been able to devise a way to determine whether duplication is stale, or a new case. For this reason, we ask that you only submit duplicate content reports when the duplication has occurred on pages created (as opposed to published) AFTER you upgraded to the fixed version. For more information on submitting a report, please see the "How You Can Help" section of the blog post at Confluence Server and Data Center: Content duplication fix and next steps - Atlassian Community.

To b03c514954d7's previous question, I would expect the above behaviour to be contributing to the reports the IT team is receiving from their users. (EDIT: I might have misunderstood here, if you're waiting to know which version is safe to proceed with, currently we believe the pending LTS releases are safe but we can't be completely certain. If you're on a version of Confluence not impacted by these bugs, it may be worth waiting to see how this issue develops so we can confirm the fixes.) If there are additional specific questions, please let me know and I'll see how I can assist.

Thanks,
James Ponting
Premier Support Engineer

I am looking at this resolution time, then looking at that modest but surely justifiable 525% price increase looming ahead for confluence (not including addons which will lose renewal discounts).

This is simply unacceptable how long it takes to get this fixed for latest long term support release.

Dear Atlassian Team,

this issue was resolved in November last year. You also announced the fix to be implemented in version 7.13.4. However 7.13.4 is not released yet. Our users feel insecure and annoyed by this bug. When do you think we can satisfy our internal customers with a solution? As I remember correctly 7.13 was announced as Long Term Support not Long Delayed Support. Please forgive my impatience but I feel the pressure from the other end. As you can imagine the most affected people are the most "important" people.

Kind regards
Florian

Hey b03c514954d7,

All of the issues we are currently aware of are detailed on the summary page. There are currently no new issues that we are aware of. Everything is up to date as of this reply.

I'm going to hold off on addressing the second paragraph until the blog post is published, and hopefully can provide some answers in doing so. I'll update everyone here when the blog update is up.

Thanks,
James Ponting
Premier Support Engineer

So, question... because it's unclear if the summary page has been updated.

Right now the situation (as posted) seems to be that known issues are patched (but 7.13.4 and 7.4.15 are yet to be released) but that there is the long-term hard data removal issue, that itself seems very low risk.

So are there NEW issues not yet reflected in the summary status? We are hearing from our IT team that they are told Synchrony is dangerous even as recently as 1/11. It would be good to demystify some of this so we understand what issues are really out there and when it might be safe to proceed.

Hi All,

Just a quick update.

We've completed the backport work for this ticket into Confluence 7.4.15 and Confluence 7.13.4.

We'll have additional information to share in the coming days through the community post at Confluence Server and Data Center: Content duplication fix and next steps - Atlassian Community.

If you're not already following that post, I would encourage you to do so.

Thanks,
James Ponting
Premier Support Engineer

Hi 3beb08ce6fca,

The change is made, Hopefully that'll help clarify for users finding the issue.

Thanks for the feedback

Regards,
James Ponting
Premier Support Engineer

Hi James,

the point is that the descriptions says: "This bug fix is a candidate for backporting ..."

If it would be: "This bug fix will be backported ..."

then all would be clear and community will wait and lloking forward

Hi All,

I'm a little unsure of what's being asked with that comment.

We're working on the backports currently, and once tested and shown to be safe, they'll be released into both Confluence 7.4 and 7.13.

Just to be clear, we're not holding the fixes back for any reason, the issue has just been very complex to troubleshoot and resolve.

We'll get them to you as soon as possible.

Thanks,
James Ponting
Premier Support Engineer

We really need this to be backported in 7.13.4 as this bug is frustrating to our users.

Assuming the latest findings, can we now expect a backport for LTS 7.13?

Hi All,

Just providing an update here as well.

During our investigation of CONFSERVER-73383: Duplicate Content Shown When Editing A Newly Published Page (fixed in Confluence Server and Data Center 7.15.0), we confirmed that these issues are related and that CONFSERVER-73383 is fixed by the fix to this issue.

We additionally discovered that a number of plugins directly interact with the attachment manager in Confluence during page creation and publishing in a way that can cause this duplication to occur. This behaviour is completely transparent to the user, and does not require the user to have interacted with attachments at all. To be clear, the plugins are not the root cause of the issue but rather trigger a bug in Confluence. We have been able to confirm that the fix in Confluence 7.15.0 corrects this behaviour.

With this in mind, please be aware that you may be impacted by this particular bug, without having actively interacted with attachment as a user.

I'll update when we have more information to share.

Thanks,
James Ponting
Premier Support Engineer

Please fix it also in LTS Version 7.13.xx

We also see this occuring in 7.14.1

Hello James Whitehead, you are fixed it also in the LTS - Version 7.13.* ? Please!

A fix for this issue is available to Server and Data Center customers in Confluence 7.15 Upgrade now or check out the Release Notes to see what other issues are resolved.

Hi All,

Confluence 7.15.0 is due for release in the next few days and includes a fix for this issue.

This issue is a candidate for backporting to the LTS releases of Confluence, and will be backported as soon as we can establish that the fix is safe. I'll provide an update on this front as soon as I have one.

Thanks,
James Ponting
Premier Support Engineer

We are also seeing this on 7.13.1 and are waiting for a backported fix in 7.13.x

Will there be a fix for enterpriise release version 7.13.x?

We are seeing a similar symptom with duplicated and triplicated content on some pages in the Confluence 7.13.0 version.

Hello, I would like to inform you that there are 3 bugs involved in this behaviour. Only one of them has been fixed in 7.13.0.
Here is a brief list of what I was able to find out:

Status of relevant tickets related to the bug "duplicate content":
https://jira.atlassian.com/browse/CONFSERVER-59227
from Dec. 2019, duplicate content, fixed in 7.13.0 backport to 7.4.x possible
https://jira.atlassian.com/browse/CONFSERVER-69074
from Sep. 2021, duplicate content, fix planned in 7.15. Backport to 7.4.x/7.13.x open
https://jira.atlassian.com/browse/CONFSERVER-73383
from Sep. 2021, duplicate content, fix open

Hi, our experience is that the bug is occuring editing pages that have large tables or editing attachments. We are using version 7.12.5.

Hello,

we are updating our application today. Is the issue fixed in 7.14.1?

Hi Atlassian, we are useing Version 7.4.11 and are affected to.

You offer a bugfix in release 7.15, which is far away in the future for us.

1. is there a possibility to backport a bugfix to our version?
2. if not, how long have we to wait für a fixed release?
3. @Rainer Pöhlmann informed in comment from 29 Okt 2021, that this can happen in v 7.13 without touching an attachment - can you confirm this issue?

I could read in the financial news, Atlassian had the best business result ever. Please invest some of this money in better bug fix strategy.

Regards, Jürgen Buchinger

Hey Atlassian, what's going on?

7.13.2 is now released without the fix. We have more than 10 customers who are very upset because of this.
Can you please let us know if we have to wait days, weeks, or months?

Thanks

Any updates on this case?

Dear @James Pointing,

unfortunately very bad news: I just triggered a content duplication on 7.13.0 LTS without touching any attachment on that page. So there is still voodoo like content duplication going on without touching an attachment

@jponting: Sorry to say but this annoying content duplication still happens on both of our 7.13.0 LTS instances. Gut feeling: seems to be more prominent on pages using sections for layout purposes. As a result, a whole section gets duplicated upon page update.

A timely fix for LTS versions would be greatly appreciated!

Thanks,
-Rainer

This one is really bad, as others have already mentioned, this open bug is really annoying on a daily basis. This should get fixed withing the next iteration of 7.14.x and not pushed to v7.15 (due probably next year...).

Atlassian, you're not doing yourselves any favors with mistakes like this. The discontinuation of the server version and the price increase makes many companies think about alternatives. Such errors in the core functionality of a collaboration system are no arguments for you.

A quick fix would be very desirable. Our users are quite annoyed by it.

Hi All,

14af2cf208b9 - Yes this issue will be backported to 7.4.x as well, seems I was having a moment yesterday.

Sorry for the confusion.

Thanks,
James Ponting
Premier Support Engineer

Dear @James Pointing,

this fix is planend to be backported to both LTS releases, right? When can we expect the fix in version 7.4.x?
The users are quite disappointed about the issue.

Thanks.

Hi All,

Unfortunately this issue was introduced as a part of another fix that was released in the affected versions listed above.

We are aware that the issue is impacting production environments. The issue was identified roughly a month ago (with the help of the community) and work begun immediately on correcting it.

The fix is planned for Confluence 7.15.0 because that's the next release we can get it into. The fix will certainly be a backport candidate and as such we'll backport it to Confluence 7.13.x (LTS) as soon as we know it won't introduce additional new problems.

Once we have a potential fix version for Confluence 7.13.x, we'll update the ticket to reflect it.

Thanks,
James Ponting
Premier Support Engineer

It will not be fixed in current LTS 7.13?

Single user edit test on 7.13.0
tested editing an old page with attachment,
1. edit page and edit attachment at same time, two different tabs.
2. save attachment, this was an excel workbook edit, then save edited page,

got duplicate data, entire content of original page was duplicated and displayed below the new version of the page.
I did not execute a hard data eviction for Synchrony, 

The workaround "Revert to last published version" is not valid, I do not have this option when I click the ellipsis, and restoring the page from history erases my new edits to the page.
I was able to edit the page and remove the duplicate data as a workaround.

Confluence 7.13.1 is affected too.

Also happening for us. 7.15 fix, may be a little to late? This affects production environment. Thank you

Same for us: the "duplicated content phenomenon" re-appeared after upgrading to 7.13.0 LTS, however this time only when editing the page in conjunction with updating the attachment.