Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation versioning has broken links #37

Open
4 tasks
sashabrava opened this issue Jun 26, 2019 · 1 comment
Open
4 tasks

Documentation versioning has broken links #37

sashabrava opened this issue Jun 26, 2019 · 1 comment

Comments

@sashabrava
Copy link

Checklist

  • I have checked the issues list
    for similar or identical bug reports.
  • I have checked the pull requests list
    for existing proposed fixes.
  • I have checked the commit log
    to find out if the bug was already fixed in the master branch.
  • I have included all related issues and possible duplicate issues in this issue
    (If there are none, check this box anyway).

Related Issues and Possible Duplicates

Related Issues

celery/celery#380
celery/celery#4007

Possible Duplicates

  • None

Description

If I visit page https://docs.celeryproject.org/en/latest/whatsnew-4.3.html and try to change the version of documentation, I get 404 error (generated link http://docs.celeryproject.org/en/v4.0.1/whatsnew-4.3.html doesn't look valid). The same thing happens if I visit http://docs.celeryproject.org/en/3.0/whatsnew-4.0.html and try to change on later documentation version.
bug

I've also found some broken links over forums, let me know if you're interested.

Suggestions

Django 1.7 documentation doesn't allow me to view Django 2.2 article "What's new" since I'm on earlier versions of documentation. However, they allow to view Django 1.7 "What's new" even if I'm on Django 2.2 documentation.

Which means that limiting available documentation versions for some articles will decrease the amount of 404 pages users can get.

solution

@auvipy auvipy transferred this issue from celery/celery Jun 26, 2019
@thedrow
Copy link
Member

thedrow commented Jun 30, 2019

Strange.
I disabled some of them on readthedocs and I figured that they are simply removed.
Maybe we should trigger a new build for them.
@auvipy Can you take care of that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants