I have a page with a number of links that point to anchors (headings) within the same page. This is using the "#heading" syntax.
However, when I copy the page, all links are messed up, so that instead of refering to "#heading", they refer to "Copy of pageX#heading". Even more annoying, the link text is also updated.
Is this a known defect or something that can be prevented somehow?
I don't think that this is a defect. If I copy a page with "self-referencing" links, I would expect that these self-referencing links keep their self reference. They should link to the same page where they are included and so they also do that on the copy.
Not sure if you agree or disagree with my statement.
I did more testing and am fully confused.
The source page has
<ac:link ac:anchor="Introduction" />
(where introduction is a heading on the same page). This shows as
When I copy the page it shows as
Copy of PageX#Introduction
However, when I then edit the copied page the copied page goes back to normal (markup and display) - even without applying any actual edits.
I would consider this to be an error.
I don't understand the problem, to be honest. My original test page looks like this:
<p><ac:link ac:anchor="test" /></p>
If I copy the page and look at the storage format, it looks exactly the same.
If I look at the target of the link on the original page, it refers to:
and the copy:
If I understand Working with Links correctly, it seems to me that
is the implied form of
iff 'page' is the current page.
So it may be considered an issue to not fully normalize the link, although the rendered result is - as Thomas has shown - identical.
I suppose M.S. encounters an actual problem for a use case due to Confluence not 'normalizing' the links on the copied page fully. Maybe this could provide some more context for this question and therefore we could understand why this should be considered an error?
I just checked with a 6.3.3 and I cannot reproduce the problem.
I created a page with a local link, copied it and the label of the link does not contain the anchor.
I downloaded the WAR with the Atlassian SDK and started the Confluence Server locally.
EDIT: Synchrony is off in this test environment.
For anyone else experiencing this issue, similar behavior has been reported as a bug:
M.S. is going to turn off collaborative editing to see if that fixes the issue for his instance.
Has this issue been logged as a bug in JIRA? We've just discovered we've been exposed to
and we're turning off Collaborative Editing b/c of it. We would like to turn it back on once 51690 is fixed. However, unless we're confident that this "copy" bug won't affect us, I'd be reluctant to turn it back on.
I understand you are concerned that links will break when copying pages with collaborative editing on.
In response to this thread and the related support request I added a comment to the bug report to let the dev team know it is being reported on copies as well as simple edits: An anchor link's name changes after editing the page with Collaborative Editing switched on or set to limited
It's true that the comment is 6 months old. It makes sense that you would be frustrated at being hit by that and other collaborative editing bugs.
The criteria we use to choose which bugs to fix is documented in our Bug Fixing Policy. If you need a new bug report opened, please use our support portal to open a support request so the support engineer can reproduce the issue and open a new Jira issue.
Atlassian Support is eager and happy to help verify bugs—we take pride in it! Create an issue in our support system, providing as much information as you can about how to replicate the problem you're experiencing. We'll replicate the bug to verify, then lodge the report for you. We'll also try to construct workarounds if possible.
Hi my Community friends! For those who don't know me, I'm a product marketer on the Confluence Cloud team - nice to meet you! For those of you who do, you know that I've been all up in your Co...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs