Actually, this is a typical URL from Google: 1. Search "django models" 2. Get http://docs.djangoproject.com/en/dev/ref/models/instances/?from=olddocs
IMHO, the correct solution is an actual 301 (permanent) redirect to take Google and others where the "current" URL of the page is. Unfortunately, the ?from=olddocs querystring is what Google thinks is the definitive model reference. ?from=olddocs needs to still be supported, but if you Google "Django Models", I don't see any reason to be sent to the 0.96 version of the page. The URL should be whatever the current method is. Part of the problem is that the Google sitemap hasn't been updated in 2 years and looks abandoned: http://code.djangoproject.com/log/djangoproject.com/django_website/sitemaps.py This is what I think is best but it will take some work and seems lower priority than actual development: 1. http://docs.djangoproject.com/en/dev/ref/models/instances/?from=olddocsshould 301 (permanent) redirect to http://docs.djangoproject.com/en/ref/models/instances - it would be nice if this weren't necessary, but it's too late judging from Google's index. 2. http://docs.djangoproject.com/en/dev/ref/models/instances (with the dev/) should work, but should show the message telling the user that this is the development version of this document with a link to http://docs.djangoproject.com/en/ref/models/instances (without dev/ - the "current" version of the page which is an alias for whatever the current version of the codebase is) 3. http://docs.djangoproject.com/en/1.0/ref/models/instances should work with the 1.0 branch of that document with the same message as #2 giving a link to the person to http://docs.djangoproject.com/en/ref/models/instances. The message here would say something like "This is the absolute URL for this version of this document forever. Unless necessary, please use the current documentation at http://docs.djangoproject.com/en/ref/models/instances. #3 seems redundant but I think it's the best solution to the fact that the current stable documentation lasts only as long as that release. As releases become more common (1.0.1,1.0.2, etc...), this will become more difficult to manage than it ever has been before. If somebody would like, I can start a ticket about this although it will probably take some hashing to figure out the truly correct solution - and I'm not in the best position to implement this. On Tue, Nov 18, 2008 at 8:01 PM, Ludvig Ericson <[EMAIL PROTECTED]>wrote: > > On Nov 19, 2008, at 00:13, Russell Keith-Magee wrote: > > That is exactly what _is_ happening. You only get the olddocs > > parameter if you are visiting from a djangoproject.com/docs URL. If > > you go in via docs.djangoproject.com, you don't get the olddocs > > warning. > > > > The confusion may be caused by the fact that the Google index (which > > is used by Django's documentation search) still contains a lot of > > olddocs pages. > > So uh, I agree with the original post a lot. I personally go edit the > URL all the time so I don't have that big red flashy thing. > > The obvious solution -- to me -- is to do a redirect if the referrer > is not djangoproject.com? To the same URL without the from=olddocs. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
