It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
Hi. We're in the process of inserting anchors within our documentation and we're finding that the anchors are randomly breaking and renamed.
For example, we create an achor called Requirements
Later, when testing, we find that links to that anchor have been renamed to Requi. We fixed it, and later we found it called Requ.
Of course, any link within the document that links to #Requirements is now broken.
Any ideas?
Edit: Update with clarification:
The anchor names remain the same. It's the links that get renamed.
For example, I might have text that says "check the requirements section" and the link is to #requirements.
Later I check and the text is the same, but the link is now #requi and doesn't jump to the anchor.
Matthew, I'm sorry I wasn't clear.
The anchor names remain the same. It's the links that get renamed.
For example, I might have text that says "check the requirements section" and the link is to #requirements.
Later I check and the text is the same, but the link is now #requi and doesn't jump to the anchor.
When you say it has been renamed, do you mean the actual <a> (anchor) tag within the page has been "renamed" or the text in the link to that anchor tag has been "renamed".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Huh, I use a lot of local anchors and haven't seen this before. I can't think of why it might be happening. Can you reproduce this, or is it fairly random? I'd say if it's reproducible, you should file a bug. If not, hopefully, someone else can chime in and suggest what might be happening.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's fairly random. Me (and my documentation team) just noticed it this morning. I haven't found a way to reliably reproduce it.
Our workflow right now is focused on adding links, anchors, and cross-referencing articles. So we're going through articles and adding this, then we check each others' work. We fixed links, but now we're finding links that we /know/ we fixed broken again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess one thing I would do to diagnose would be to look at the history of the page and diff the page with the previous to see when the change occurs. Not sure if this is going to lead to anything, but at least there's a chance that a pattern will emerge.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi team, I’m Avinoam, a product manager on Confluence Cloud, and today I’m really excited to let the Community know that all customers can now try out the new editing experience and see some of the ...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.