Re: [Django] #12043: Incorrect redirect to http instead of https

[Django]

#12043: Incorrect redirect to http instead of https
--+-
  Reporter:  ad...@gpuserver.com  | Owner:  nobody 
Status:  new  | Milestone: 
 Component:  Core framework   |   Version:  1.1
Resolution:   |  Keywords:  redirect http https
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by ad...@gpuserver.com):

 It looks like you've got the right idea.

 I am using Webfaction.

 I haven't tried dumping out WSGI environment before it is passed into
 Django, but I assume that your hypothesis is correct.

 When I dump request.META (inside my Django view), I get:

   - wsgi.url_scheme = http
   - HTTP_X_FORWARDED_PROTO = https

 So there are two possible solutions:

  1. I get Webfaction to do as you suggest (to fix wsgi.url_scheme).
  2. You change is_secure() to include HTTP_X_FORWARDED_PROTO in it's
 calculation.
  3. Do both.

 Option 3 seems the most solid to me.

 I'm sending Webfaction a link to this ticket.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #12043: Incorrect redirect to http instead of https

[Django]

#12043: Incorrect redirect to http instead of https
--+-
  Reporter:  ad...@gpuserver.com  | Owner:  nobody 
Status:  new  | Milestone: 
 Component:  Core framework   |   Version:  1.1
Resolution:   |  Keywords:  redirect http https
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by grahamd):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Those change sets aren't going to be most recent for is_secure(). This is
 because for WSGI the code was since changed to correctly use
 wsgi.url_scheme.

 There is no issue with wsgi.url_scheme generation in mod_wsgi, so long as
 Django code still checking that then should be fine.

 One possibility for problems is that your Apache isn't handling HTTPS but
 you are hosting it behind a front end server, such as nginx. WebFaction
 for example does this. In that case, that HTTPS was used isn't known by
 Apache as it only receives HTTP from front end. In this case, necessary
 for front end web server to set a special HTTP header which is then
 detected by Apache behind, which using certain directives in Apache can
 detect that and set HTTPS in request environment which mod_wsgi will
 detect and convert to appropriate value for wsgi.url_scheme.

 So, are you 100 percent certain that your Apache is accepting HTTPS
 requests in the first place.

 Have ou tried dumping out WSGI environment before it is passed into Django
 to see what it is passed. Use code examples in:

 
http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Tracking_Request_and_Response

 to capture such information and post here.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #2713: Sitemap Index with Cache gives a NoReverseMatch exception

[Django]

#2713: Sitemap Index with Cache gives a NoReverseMatch exception
---+
  Reporter:  JayKlehr  | Owner:  stavros
Status:  new   | Milestone: 
 Component:  Contrib apps  |   Version:  SVN
Resolution:|  Keywords: 
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  1  
Needs_better_patch:  0 |  
---+
Changes (by askfor):

 * cc: ask...@gmail.com (added)

Comment:

 Got the same problem here.
 I was wondering why the cache_page decorator works for
 www.djangoproject.com according to the code on the trac
 
(http://code.djangoproject.com/browser/djangoproject.com/django_website/urls.py)
 ?
 And there's also another problem. Since sitemap reverse the url by
 'django.contrib.sitemaps.views.sitemap' , if there's a app also use
 sitemap, there will be a conflict.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #6378: Capture arbitrary output as a template variable

[Django]

#6378: Capture arbitrary output as a template variable
-+--
  Reporter:  kcarnold| Owner:  nobody
Status:  new | Milestone:
 Component:  Template system |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by ericholscher):

 Imaging an implementation along the lines of this:

 http://github.com/nathanborror/django-basic-
 
apps/blob/01b37fb28605504893811ffac89cb97852f2e0a4/basic/tools/templatetags/capture.py

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #12047: Copy/paste error in documentation

[Django]

#12047: Copy/paste error in documentation
+---
  Reporter:  schickler  | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution: |  Keywords:  typo  
 Stage:  Ready for checkin  | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * keywords:  => typo
  * needs_better_patch:  => 0
  * stage:  Unreviewed => Ready for checkin
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7835: Provide the ability for model definitions that are only availably during testing

[Django]

#7835: Provide the ability for model definitions that are only availably during
testing
+---
  Reporter:  russellm   | Owner:  kkubasik   
Status:  new| Milestone: 
 Component:  Testing framework  |   Version:  SVN
Resolution: |  Keywords:  feature test models
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

 * cc: t.dja...@sandbox.cz (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11250: InlineModelAdmin with can_delete

[Django]

#11250: InlineModelAdmin with can_delete
---+
  Reporter:  ctao  | Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  InlineModelAdmin,  
can_delete
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by gsf):

  * has_patch:  0 => 1

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #11250: InlineModelAdmin with can_delete

[Django]

#11250: InlineModelAdmin with can_delete
---+
  Reporter:  ctao  | Owner:  nobody 
  
Status:  new   | Milestone: 
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  InlineModelAdmin,  
can_delete
 Stage:  Accepted  | Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by gsf):

  * version:  1.0 => SVN
  * component:  Uncategorized => django.contrib.admin

Comment:

 This is pretty much a duplicate of #8341, which brosner fixed by making
 subclassing easier, but nonetheless it's something I've wanted enough
 times as a simple attribute in TabularInline that I think it's worth
 considering for inclusion.  Patch attached with necessary changes to tests
 and docs.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #12047: Copy/paste error in documentation

[Django]

#12047: Copy/paste error in documentation
---+
 Reporter:  schickler  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 http://docs.djangoproject.com/en/dev/ref/generic-views/#django-views-
 generic-date-based-archive-day

 In the template context portion of the documentation for the
 date_based.archive_day generic view, "previous_day" is incorrectly
 documented:


 "previous_day: A datetime.date object representing the given day. [...]"

 I believe this is just a copy/paste error from "day":

 "day: A datetime.date object representing the given day."


 The correct documentation should be:


 "previous_day: A datetime.date object representing the previous day."

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #12046: fastcgi dies under heavy load

[Django]

#12046: fastcgi dies under heavy load
---+
 Reporter:  acoder |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Using Django with fastcgi and nginx, Django often dies because it can't
 create new threads. I am using maxchildren=512 and daemonize=true. I am
 using blocking operations (such as http GET) in my views, so a request can
 take a while to finish.
 {{{
 Traceback (most recent call last):
   File "./manage.py", line 11, in 
 execute_manager(settings)
   File "/var/lib/python-
 support/python2.6/django/core/management/__init__.py", line 340, in
 execute_manager
 utility.execute()
   File "/var/lib/python-
 support/python2.6/django/core/management/__init__.py", line 295, in
 execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/var/lib/python-support/python2.6/django/core/management/base.py",
 line 192, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/var/lib/python-support/python2.6/django/core/management/base.py",
 line 219, in execute
 output = self.handle(*args, **options)
   File "/var/lib/python-
 support/python2.6/django/core/management/commands/runfcgi.py", line 16, in
 handle
 runfastcgi(args)
   File "/var/lib/python-support/python2.6/django/core/servers/fastcgi.py",
 line 176, in runfastcgi
 WSGIServer(WSGIHandler(), **wsgi_opts).run()
   File "/var/lib/python-support/python2.6/flup/server/fcgi.py", line 113,
 in run
 ret = ThreadedServer.run(self, sock)
   File "/var/lib/python-support/python2.6/flup/server/threadedserver.py",
 line 98, in run
 if not self._threadPool.addJob(conn, allowQueuing=False):
   File "/var/lib/python-support/python2.6/flup/server/threadpool.py", line
 74, in addJob
 thread.start_new_thread(self._worker, ())
 thread.error: can't start new thread}}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7270: selected_related() can not follow reverse relations of OneToOne.

[Django]

#7270: selected_related() can not follow reverse relations of OneToOne.
---+
  Reporter:  towjz...@hotmail.com  | Owner:  
mtredinnick
Status:  new   | Milestone:  1.2

 Component:  Database layer (models, ORM)  |   Version:  SVN

Resolution:|  Keywords:  
select_related onetoone reverse
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Changes (by oldium):

 * cc: oldium@seznam.cz (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #12045: BooleanField with choices in ModelForm does not show selected value in MySQL

[Django]

#12045: BooleanField with choices in ModelForm does not show selected value in
MySQL
+---
  Reporter:  jittat   | Owner:  nobody

Status:  new| Milestone:

 Component:  Forms  |   Version:  SVN   

Resolution: |  Keywords:  ModelForm, 
MySQL, BooleanField
 Stage:  Unreviewed | Has_patch:  0 

Needs_docs:  0  |   Needs_tests:  0 

Needs_better_patch:  0  |  
+---
Changes (by jittat):

  * needs_better_patch:  => 0
  * version:  1.1 => SVN
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #12045: BooleanField with choices in ModelForm does not show selected value in MySQL

[Django]

#12045: BooleanField with choices in ModelForm does not show selected value in
MySQL
+---
 Reporter:  jittat|   Owner:  nobody
   Status:  new |   Milestone:
Component:  Forms   | Version:  1.1   
 Keywords:  ModelForm, MySQL, BooleanField  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 From ticket #7190 `BooleanField` in MySQL would return 0 or 1.   When it
 is used in `ModelForm`, this `BooleanField` will be rendered as
 `TypedChoiceField` using `Select` widget.  A problem occurs when the field
 has choices.

 '''How to reproduce:'''

 1. Create a model in MySQL with `BooleanField` with choices, e.g.,
 {{{
 class MyModel(models.Model):
 is_working = models.BooleanField(
 choices=((False,"This doesn't work"),
  (True,"This works!")))
 }}}
 2. In `./manage.py shell`, try the following:
 {{{
 >>> from testbf.models import MyModel
 >>> m = MyModel()
 >>> m.is_working = True
 >>> m.save()
 >>> m.is_working
 True
 >>> n = MyModel.objects.all()[0]
 >>> n.is_working
 1
 >>> from django.forms import ModelForm
 >>> class MyModelForm(ModelForm):
 ...  class Meta:
 ...  model = MyModel
 ...
 >>> f = MyModelForm(instance=n)
 >>> f.as_p()
 u'Is working:
 \n
 This doesn't work\n
 This works!\n
 '
 }}}

 The correct output should have attribute `selected="selected"` in ``

 '''Code...'''

 The code for checking selected value is in
 `forms.widgets.Select.render_options.render_option` is
 {{{
 def render_option(option_value, option_label):
 option_value = force_unicode(option_value)
 selected_html = (option_value in selected_choices) and u'
 selected="selected"' or ''
 return u'%s' % (
 escape(option_value), selected_html,
 conditional_escape(force_unicode(option_label)))
 }}}
 Now, the option_value is converted to unicode, and `True` is converted to
 `u'True'`.  However, the choices in `selected_choices` is `[u'1']`
 (because the value returned by `BooleanField` in MySQL is 1).

 Therefore, the expression: `(option_value in selected_choices)` is false,
 and the `selected="selected"` is not included in the rendered html.

 I have no idea how to patch it.  There are too many places to start, as
 the value is passed from `models.BooleanField` to `forms.BoundField` and
 to `Select` widget in `TypedChoiceField`.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #12044: Add extra_context to admin action delete_selected

[Django]

#12044: Add extra_context to admin action delete_selected
--+-
 Reporter:  rjc   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 We need to pass extra context in admin action delete_selected, just like
 admin view's delete_view.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10060: Multiple table annotation failure

[Django]

#10060: Multiple table annotation failure
--+-
  Reporter:  svsha...@intellecap.net  | Owner: 
Status:  new  | Milestone: 
 Component:  ORM aggregation  |   Version:  SVN
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by fitoria):

 I can confirm this one... It happens with aggregate too wrong values in 2
 - 5% range.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8611: Reverse for '' not found

[Django]

#8611: Reverse for '' not found
-+--
  Reporter:  imbac...@gmail.com  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Core framework  |   Version:  1.1   
Resolution:  fixed   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by lukeplant):

  * status:  reopened => closed
  * resolution:  => fixed

Comment:

 Suor - I don't understand your comment or why you reopened the ticket.
 Currently all our decorators use functools.wraps (or equivalent) as far as
 I know, and the view functions are now reported correctly in the
 !NoReverseMatch error.  Also, before r11482 it was not enough simply to
 use correct wrapping, because callables like _CheckLogin (or
 !MethodDecoratorAdaptor) would still display the unhelpful message given
 above.  Or did you re-open by mistake?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  1 |  
---+
Comment (by mrts):

 :)

 Your nitpicking is most welcome, thanks!

 I plan continue taking care of the patch and I'll think about the popup
 cascading case as well as implement the things mentioned in the TODO
 comments. However, it is unclear when I have time for it. But I'd say the
 patch is usable as-is for those who need it.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #6904: Dictsort filter should sort case insensitive

[Django]

#6904: Dictsort filter should sort case insensitive
-+--
  Reporter:  mich...@mathwizard.org  | Owner:  nobody
Status:  new | Milestone:
 Component:  Template system |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  0 
Needs_better_patch:  1   |  
-+--
Changes (by Michael P. Jung):

 * cc: mpj...@terreon.de (added)
  * needs_better_patch:  0 => 1

Comment:

 Please don't just lower() the strings when sorting them. Use the collation
 of the locale.

 http://groups.google.com/group/django-
 developers/browse_thread/thread/a6fa8df5787b9c32

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  1 |  
---+
Comment (by marcob):

 fanny = funny :) (Italian common error)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  1 |  
---+
Comment (by marcob):

 mtrs, after looking at your patch I remembered this comment of mine:
 http://code.djangoproject.com/ticket/6903#comment:30

 Fanny, isn't it? I would like to say "great minds think alike" but perhaps
 is more proper "great asses fart alike" :-)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  1 |  
---+
Comment (by marcob):

 Tested and it works! Both in FF than IE. Thanks!

 I was to write about update the label if changed when I saw you already
 write it in the "it needs" part of you comment.
 Just to know, are you willing to do it or you left it as an exercise for
 the reader? :)

 Another minor glitch is that I have a table with a FK on a table of
 hierarchical codes that has a "self" FK. When I open the first popup
 window and I click on the inside label for the "self" FK I don't get
 another popup but it opens in the same window. I'm not sure if it's better
 in this way or to open a new window but to obtain this behaviour it's
 enough to name the window with the id of the object.

 Btw this is nitpicking. You did a wonderful job.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #12043: Incorrect redirect to http instead of https

[Django]

#12043: Incorrect redirect to http instead of https
-+--
 Reporter:  ad...@gpuserver.com  |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Core framework   | Version:  1.1   
 Keywords:  redirect http https  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 To reproduce on a secure django website - Django (1.1)/mod_wsgi
 (2.5)/Python (2.5):

   1. Verify that https://secure.example.com/admin/ works
   2. Now try https://secure.example.com/admin
   3. Note that it has redirected to http://secure.example.com/admin
 instead of https://secure.example.com/admin/

 This also happens in various other circumstances where Django decides to
 do a redirect for you.  E.g. after logging out and back in.

 This is probably caused by [http://code.djangoproject.com/changeset/3410
 changeset 3410] - fix for [http://code.djangoproject.com/ticket/2092
 ticket 2092].  Please take a look at these for insight.

 Humorous note: The following rather dubious hack works great for me
 because all of my pages are https :)

 {{{
 # Not recommended for general use!
 def is_secure(self):
 return True
 }}}

 The correct fix will involve figuring out the correct detection of the url
 scheme in all cases.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  1  
  
Needs_better_patch:  1 |  
---+
Changes (by mrts):

  * needs_better_patch:  0 => 1
  * needs_tests:  0 => 1

Comment:

 Although the patch is quite usable, it needs
  * more view tests, specifically for the template tag and
 `options.py/ModelAdmin.response_change` when the next item is implemented
  * when the object's label changes via the popup, it makes sense to update
 it with !JavaScript in the DOM as well (similarly to
 `dismissAddAnotherPopup`), there are TODOs in the patch for the places
 that need updating.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7028: Better raw_id_fields feedback in newform-admins branch

[Django]

#7028: Better raw_id_fields feedback in newform-admins branch
---+
  Reporter:  Marcob   | Owner:  nobody 
  
Status:  new   | Milestone:  1.2
  
 Component:  django.contrib.admin  |   Version:  SVN
  
Resolution:|  Keywords:  
raw-id-fields nfa-someday
 Stage:  Accepted  | Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Comment (by mrts):

 Marco, please review and test when you have time (checking with that same
 failing case in IE is much appreciated). Using {{{`}}} was both a hack and
 a bad idea, thanks for rectifying this (my only excuse, albeit a feeble
 one, is that it doesn't matter in my language, {{{`}}} and {{{'}}} are
 treated more or less equivalently).

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #6138: newforms: when accessing directly form.errors, error_class is not used

[Django]

#6138: newforms: when accessing directly form.errors, error_class is not used
---+
  Reporter:  Michal Moroz  | Owner:  peter2108
Status:  closed| Milestone:   
 Component:  Forms |   Version:  SVN  
Resolution:  fixed |  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by peter2108):

  * status:  new => closed
  * resolution:  => fixed

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8611: Reverse for '' not found

[Django]

#8611: Reverse for '' not found
-+--
  Reporter:  imbac...@gmail.com  | Owner:  nobody
Status:  reopened| Milestone:
 Component:  Core framework  |   Version:  1.1   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Suor):

  * status:  closed => reopened
  * resolution:  invalid =>

Comment:

 Actual problem is not wrapping view carefully, I used my own decorator
 which used functools.wraps decorator to wrap wrapper function and view
 function
 was reported right in reverse error.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #12037: A ContextLazyObject-wrapped User breaks {% url myurlname user %}

[Django]

#12037: A ContextLazyObject-wrapped User breaks {% url myurlname user %}
-+--
  Reporter:  chipx86 | Owner:  lukeplant
Status:  closed  | Milestone:   
 Component:  Authentication  |   Version:  1.1  
Resolution:  fixed   |  Keywords:   
 Stage:  Unreviewed  | Has_patch:  0
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by chipx86):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 Thanks, our builds are no longer tripping up on this :) Not sure why you
 weren't able to reproduce it. Maybe there was something more subtle going
 on, but this fixes it regardless.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8054: Move method properties for admin list customisation to ModelAdmin

[Django]

#8054: Move method properties for admin list customisation to ModelAdmin
+---
  Reporter:  Daniel Pope   | Owner:  
brosner
Status:  assigned   | Milestone:
 
 Component:  django.contrib.admin   |   Version:  
SVN
Resolution: |  Keywords:
 
 Stage:  Accepted   | Has_patch:  1 
 
Needs_docs:  1  |   Needs_tests:  1 
 
Needs_better_patch:  1  |  
+---
Changes (by anonymous):

 * cc: a...@andybak.net (added)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---