You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
Checklist
for similar or identical bug reports.
for existing proposed fixes.
to find out if the bug was already fixed in the master branch.
(If there are none, check this box anyway).
Related Issues and Possible Duplicates
Related Issues
celery/celery#380
celery/celery#4007
Possible Duplicates
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.
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.
The text was updated successfully, but these errors were encountered: