Code

Changes between Initial Version and Version 4 of Ticket #18922


Ignore:
Timestamp:
11/13/12 14:30:40 (17 months ago)
Author:
aaugustin
Comment:

Yes, we can keep this ticket to track other ideas to resolve this problem.

For the record, the original proposal was:

Hopefully, removing the dev documentation pages from search engines will help solve this issue, since those who want to read the dev docs can just click through to them by using the version navigation at the bottom of the docs pages.

I think there is a small subset of actual Django users who run their applications on trunk. I don't have data to back that up but I can't imagine it's a lot.

I talked with Alex earlier today about how to deal with this issue--he also suggested redirecting users from dev -> 1.4 (or whatever the latest version is). I initially thought it was a good idea, but I thought about it and realized you would have to at least add some sort of referrer check. I then thought whether it would be ok to do something like

    def conditional_documentation_redirect(request):
        if not request.META['REFERER'].startswith("http://docs.djangoproject.com"):
            return HttpResponseRedirect #... and so on

This felt wrong to me because if that sort of check were in place, users would no longer be able to permalink to dev docs.

PR @ https://github.com/django/djangoproject.com/pull/43

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18922

    • Property Status changed from new to reopened
    • Property Patch needs improvement unset
    • Property Needs tests unset
    • Property Owner changed from nobody to dloewenherz
    • Property Needs documentation unset
    • Property Triage Stage changed from Unreviewed to Accepted
  • Ticket #18922 – Description

    initial v4  
    664. Invalid bug is filed in trac. 
    77 
    8 Hopefully, removing the dev documentation pages from search engines will help solve 
    9 this issue, since those who want to read the dev docs can just click through to 
    10 them by using the version navigation at the bottom of the docs pages. 
    11  
    12 I think there is a small subset of actual Django users who run their applications 
    13 on trunk. I don't have data to back that up but I can't imagine it's a lot. 
    14  
    15 I talked with Alex earlier today about how to deal with this issue--he also suggested 
    16 redirecting users from dev -> 1.4 (or whatever the latest version is). I initially 
    17 thought it was a good idea, but I thought about it and realized you would have to at 
    18 least add some sort of referrer check. I then thought whether it would be ok to do 
    19 something like 
    20  
    21 {{{ 
    22     def conditional_documentation_redirect(request): 
    23         if not request.META['REFERER'].startswith("http://docs.djangoproject.com"): 
    24             return HttpResponseRedirect #... and so on 
    25 }}} 
    26  
    27 This felt wrong to me because if that sort of check were in place, users would 
    28 no longer be able to permalink to dev docs. 
    29  
    30 PR @ https://github.com/django/djangoproject.com/pull/43 
     8EDIT: rejected proposal removed, see comment 4.