Replace page-version with current in links

[NataliaIvakina]

No description provided.

[recrwplay]

I think this should apply to links to the Cypher manual, but I don't know if links to the Operations manual or HTTP API should be updated.

I'm thinking of the case where LTS docs are published. Would a user reading LTS docs want a link to go to the same LTS version in those other manuals, rather than current?

[NataliaIvakina]

I think this should apply to links to the Cypher manual, but I don't know if links to the Operations manual or HTTP API should be updated.

You might be right. Most of the links to the Ops manual work. But I found the broken link to the Procedures page and decided it's broken because of using the page-version attribute. Probably it is broken because of the non-working redirect. We have the redirect for the Procedures page for sure. But how do redirects work with all this new versioning stuff?

The link to the HTTP API docs does not work now.

I'm thinking of the case where LTS docs are published. Would a user reading LTS docs want a link to go to the same LTS version in those other manuals, rather than current?

Yeah, I was asking myself same questions when in the Operations manual we updated links to the Cypher manual. I'm not sure but in future we may need to update all current links to the specific LTS version.

[recrwplay]

I think the issue with the link to the HTTP API docs is that the target page existed in 4.4 but not from version 5 onwards. If the content was moved to another URL then there should be a redirect in place to that new URL. If the content was removed because the feature is no longer available then a redirect to the best alternative could be used. At the moment it looks like https://neo4j.com/docs/http-api/5/actions/ redirects to https://neo4j.com/docs/http-api/current/ which might not be perfect, but at least there's no 404.

What I think this means is that this link to the HTTP API docs makes no sense after 4.4 - it's a link to something that doesn't exist - so it should be removed.

[NataliaIvakina]

I think the issue with the link to the HTTP API docs is that the target page existed in 4.4 but not from version 5 onwards. If the content was moved to another URL then there should be a redirect in place to that new URL. If the content was removed because the feature is no longer available then a redirect to the best alternative could be used. At the moment it looks like https://neo4j.com/docs/http-api/5/actions/ redirects to https://neo4j.com/docs/http-api/current/ which might not be perfect, but at least there's no 404.

What I think this means is that this link to the HTTP API docs makes no sense after 4.4 - it's a link to something that doesn't exist - so it should be removed.

Sounds reasonable. @recrwplay, thank you for investigating. 🙂

[renetapopova]

I think the issue with the link to the HTTP API docs is that the target page existed in 4.4 but not from version 5 onwards. If the content was moved to another URL then there should be a redirect in place to that new URL. If the content was removed because the feature is no longer available, then a redirect to the best alternative could be used. At the moment, it looks like https://neo4j.com/docs/http-api/5/actions/ redirects to https://neo4j.com/docs/http-api/current/ which might not be perfect, but at least there's no 404.
What I think this means is that this link to the HTTP API docs makes no sense after 4.4 - it's a link to something that doesn't exist - so it should be removed.

Sounds reasonable. @recrwplay, thank you for investigating. 🙂

I quickly looked at the HTTP API docs, and all the pages of the Cypher transaction API in 4.4 are labeled with Deprecated in 5.26, but they have no alternative pages in 5.x. So, this redirect "https://neo4j.com/docs/http-api/5/actions/` redirects to https://neo4j.com/docs/http-api/current/" looks to me as some kind of a quick fix, when actually we are missing page aliases. The same applies to the Introduction, Discovery API, and Authentication and authorization pages.

[renetapopova]

Looks good to me. Thanks, @NataliaIvakina!

[neo-technology-commit-status-publisher]

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.