Please bring back the old link editor
under review
Ed Hawco
I do NOT like not seeing the slug that is used when I make an XREF. The new advanced editor Link editor only shows the article title when you select the article to be linked. I want to see the SLUG as well as the title. I also want to be able to manually enter or edit the slug. Sometimes I create a link to an article that has not yet been created, or I know the slug will change soon. The old editor let you do that because it let you edit the slug in the link. The new link editor doesn't allow that.
Another problem: this has always been a problem but now it's worse: When linking to a HEADING on the same page, the link editor has always added the slug and then the anchor ID. This is very annoying because it means when the user clicks on the link on the published page, THE WHOLE PAGE REFRESHES instead of just jumping to the heading.
I have always worked around this by NOT USING the "link to a heading" feature. I simply manually add the anchor ID in the link box. BUT NOW I CAN'T DO THAT because I don't have access to the slug when making a link.
I know of a workaround: I click the tab to add an EXTERNAL link and then add the anchor ID in the URL field. This works for now, but is it just a matter of time before you take that away too?
At a higher level I find it annoying that so many features keep changing in ways that are supposed to make tasks "easier" but in reality they only make it easier for people who don't know what they're doing. For people with experience working on web-based documents, we find this "dumbing down" of the features to be very annoying. This removal of the slug field in the link editor is a perfect example of this.
Log In
T
Tobias Punzmann
I also miss the option to edit an inserted link manually. I've always added the language identifier (e.g. /en/) in the path manually for the main language. It will be added automatically for all other languages but the main language. Links in the main language work with or without, but when the main language is changed one time, all links w/o the language identifier in the path will be broken.
Glenn Elliott
And this is why i still use the WYSIWYG editor and not the "Advanced" one!
D
D360 Product Management
under review
V
Viswanathan
Ed Hawco
Thank you for your detailed and well-articulated feedback — we truly appreciate you taking the time to share this.
You've raised valid concerns around the new link editor, especially with regard to:
Not being able to view or edit slugs
Difficulty in linking to headings on the same page without triggering a full page reload. For this we have bought the Link to heading feature recently, can you please check on this and let us know if this works. Please find the screenshot attached,
The impact these changes have on experienced users who rely on more control
We understand how crucial these capabilities are for advanced workflows and agree that removing manual slug access can disrupt certain use cases — particularly when working with future or changing content. We will keep you posted on the updates after discussing with the team.
Ed Hawco
Viswanathan Thank you for your quick response. I have tried the "link to a heading" for the same article and it fails on two counts.
First, it is buggy and does not seem to pick up all of the headings on a page, so I will want to link to a h2 or h3 heading but it does not appear in the list. On a few test pages I tried, generally only about half of the headings appeared in the list of heading to select.
Second, when it does work, it creates the link with the entire slug and not just the #anchorID. E.g., the link will be to /user/docs/article-title#anchor instead of just to #anchor.
As a result, the entire page refreshes when the user clicks the link on the published page. This looks bad and is disruptive; this is why I manually edit the link to only include the #anchorID. This way it just jumps to the heading instead of re-loading the page and then jumping to the heading.