Article URLs should not contain version numbers (URL changing bug)
Tim Overbeck
I think this is a recent change because I don't recall this being a problem in the past. But i have noticed that currently, the URL has the article version number in it (/version/10?kb_language=en_US)
This means that if any one has an article bookmarked for quick access, if we link to an article within an article, or link to an article anywhere else. Those links always have to be updated when a change is made to the article.
The URL needs to be static so that it always points to the most current article.
To clarify, after doing some digging. The URL with the version # is presented after clicking "view published" from the editor. With the old editor it just provided the static link for the article. Often when creating or editing an article, the person doing the work will click "view publised" check the work and then use the link to share out to others.
Now that the link changes with each version, we have to go find the article from the search function and use that link. All in all, pretty confusing.
Muris Brcaninovic
Merged in a post:
Lock a URL
Tami Sutcliffe
Add a "lock" for the URL of a public, published article, so it cannot be moved/changed. This is needed when article URLs are referenced directly within product code, where any URL change becomes expensive and confusing. Adding internally-visible notes on the articles themselves, warning any potential editors to be careful changing anything is the only option available right now. "Freezing" those specific article URLs would be preferable.
Muris Brcaninovic
Merged in a post:
URL (slugs) Duplicates
daniel.bozek Božek
I would like to point out that the indexing and unique URLs should be processed by the Helpjuice engine.
It is literally impossible for a regular user to remeber all the pages within the knowledgebase to try to avoid duplicities in the URLs and sadly, it makes Helpjuice user expereince very, very poor as there is no control mechanism which would prevent or at least warn the user about such duplicity. I think this should be address. One of the ideas could be new logic of URL structure Category/subcategory/article.html or just generate unique ID (e.g. as in Confluence): https://kb.notino.com/pages/viewpage.action?pageId=22447443
Raff Lagatta
I'm not sure if this helps, but we have a 'share' button on our articles which just has a static URL and we use this for sharing. If linking an article within another article, we simply just delete the start of the URL. For example, clicking the share button gives us https://help.aroflo.com/office-assets-overview. If we want to link this page within another article (e.g. text linking to this article), we simply delete the start of it to make /office-assets-overview.
Naama Cohen
this is really an issue worth finding a solution for!
For the time being, a workaround that I've been using is to enter an article page in the admin > select "draft and unpublish > make the changes needed, and then publish once more. this way the URL stays the same - because you keep editing version 1, which doesn't affect the URL.
This way you always stay on the same version.. but I admit it is exceptionally cumbersome on a daily basis.
Giovanna de Castro Moreira Silva
We've also been facing this issue, particularly when it comes to translated articles, as the number of versions is hardly ever the same in all three languages that we use. We have agreed internally to shorten the link to the original URL, but it is something we must always be on the lookout for.
Adam Botterbusch
Yes, my team has had some confusion on Draft versions too. A draft version (say 3) is sent outside the system for review, has changes, and once changes are made a new draft link must be provided with new version (say 4), so that the reviewer isn't looking at the old unchanged version.
Marc Olivier Meunier
Exactly. I have an introduction article in multiple categories. If I name the article "Introduction", it starts creating a mess because there will be other articles named Introduction in another category
Marco Verdoliva
I also agree. I think that both your suggestion of URL structure Category/subcategory/article.html or a unique ID are good solutions
Katy Gerhold
I left a suggestion similar to this, we need unique article IDs for every single article, preferably in its own field so we can use it to search. The organization by slug is inefficient and leads to duplication.
Christine Perez
Agreed, just ran into this problem this week. When we first signed up in 2018, the URL Slugs would automatically assign a unique article ID (same as you would see when you would insert an article before). Now it just adds the same words as the title with no ID. It took me 30 minutes yesterday to figure out why 1 article was overriding and doing weird things to another titled the same thing yesterday. I was able to figure it out and add the brand name to the slug to fix it. We have multiple brands with multiple branding but most articles/categories have the same names. Trying to have consistency, it's seems redundant to have to change the title to the brand name or remember to change the slug
Load More
→