Copy of a document to a different space contains links to original
Hello,
after coping a document to a different space I discovered, that all the links within are still pointing to the original pages of the source document, not the new copied one. So if I click on any link in the document viewer, the view does not just scroll to the appropriate caption, but a new tab is open with single page view of the original page in original space.
I would expect, that the document copy in the new space would have all the links modified to the copied versions of the pages, so it will behave as an independent document. This way I will have to manually edit all the links in the copy and change them to point to the copied pages instead of the original, which will be a very tedious proces and degrades the copy functionality severely.
Is this the expected behavior, or am I doing something wrong?
I am using a cloud version of the confluence and plugin and using the "new editing experience" editor.
The mentioned documents are public and can be viewed here:
(I want to use the copy to translate the document to english.)
Best Regards,
Pavel Novák
-
Official comment
Hello Pavel,
Thank you for reaching out to us and bringing this issue to our notice.
To answer your question - this is not the intended behaviour of Scroll Documents. We investigated further into the issue and it looks like this behaviour is something Atlassian has introduced with the new Confluence Editor on cloud and is potentially a bug.
We have reached out to Atlassian and trying to get this resolved as soon as possible.
In the mean time, could you let me know how you added the page links in the editor -
- by pasting the link directly into the editor? Or,
- by using the '/' command to insert a link to the child page?
Best regards,
Dash.
Comment actions -
Hello,
thank you for a fast reaction. Glad to hear this might be bug and get fixed.
To answer your question, I added most of the links by highlighting some text and pressing Ctrl+K (or clicking the chain icon in the top toolbar, which is the same).
I also found out, that if I insert a link without having some text selected, a feature in the new editor inserts the full page URL and almost instantly rewrites it to the linked page title with icon in front. Which would be fine and I would use it, but in this case the links in the Scroll document viewer then do not get rewritten to the page title and stay as the full URL, which is ugly. So I quickly got used to the way of inserting links to other pages only on existing selected text.
Best Regards,
Pavel Novak.
-
I just found out, that the same problem occurs when versioning the document. That is even more serious issue for our use case. We are releasing a new version of our application, for which I am writing documentation in the form of Scroll Documents. So I just created versions of all the manuals, so they stay valid for the previous version of the application and I can start working on the modifications for the new version of the application. But I found out, that the saved version also now contains wrong links (to current version of pages instead of links to the version specific copy). That makes the saved version of the manual unusable.
So after I manually fixed all the wrong links in the document copies used for translation into english I now find out I have to also manually fix all the links in the saved versions of the documents? That makes the plugin practically unusable for our use case as such a process is very time consuming and error prone. We will have to seek other solutions for maintaining documentation, if this is not fixed, because in this state I consider the benefits not worth the added work needed to constantly fix the broken links in copies and saved versions of documents.
Regards,
Pavel.
-
Hi Anshuman,
since Confluence Cloud has many many more drawbacks we decided to move away from Cloud and switched to a server instance for Confluence.
Here the problem does not exist. I wish you the very best that Atlassian will address this problem ASAP since it really shines a bad light on you guys, and as far as I can tell you are doing an amazing job with your plugins...
Best
Mathias -
Hi Pavel and Mathias,
I am extremely sorry to hear that. We have trying our best to push Atlassian to fix this issue but haven't had any success yet. We are also exploring any possible alternatives that we could use in the meantime.
I will keep you posted here.
Thanks a lot for your patience and sincere apologies for the inconvenience that this issue has caused.
Best regards,
Dash.
-
Hi,
This may be a little late, but with Scroll Documents 2.1.0, we have migrated to a new copy api that avoids the issue highlighted in this post.
In addition to that, it enables for better prefix management as well. With this latest version we have significantly improved the copy document experience.
Best regards,
Dash.
Please sign in to leave a comment.
Comments
8 comments