Re: [Django] #19330: change model instance with unique_together using modelform

[Django]

#19330: change  model instance with unique_together  using modelform
-+-
 Reporter:  molavy   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  modelform| Triage Stage:
  ,unique_together ,instance ,save,  |  Unreviewed
  change |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

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


Comment:

 I'm afraid we have not enough information in the ticket description to
 assume that there is a bug in Django. Please try to debug the problem a
 little further and tell us why you think the problem is in Django and not
 in your code.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19330: change model instance with unique_together using modelform

[Django]

#19330: change  model instance with unique_together  using modelform
-+-
 Reporter:  molavy   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  modelform| Triage Stage:
  ,unique_together ,instance ,save,  |  Unreviewed
  change |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Old description:

> I have Problem on changing a model with modelform and instance
> model form return form validate error:
> user with this title already exist
>
> model:
>
> class Tag(models.Model):
> user = models.ForeignKey(User)
> title = models.CharField(max_length=765)
> create_time = models.DateTimeField(null=True, blank=True)
> status = models.IntegerField(null=True, blank=True)
> color = models.CharField(max_length=765, blank=True)
> cnt_member = models.IntegerField(null=True, blank=True)
> cnt_items = models.IntegerField(null=True, blank=True)
> def __unicode__(self):
> return self.title+ " || "+self.user.username
> class Meta:
> db_table = u'tbl_tag'
> unique_together=("user","title")
>

> form:
>
> class Tagform(forms.ModelForm):
>
> class Meta:
> model=Tag
> exclude = ('status','create_time')
>

>
> view:
> def change_tag_title(request):
> if request.POST and request.is_ajax():
> cur_id=request.POST["id"]
> cur_tag=Tag.objects.get(id=cur_id,user=request.user)
> cur_req=request.POST.copy()
> cur_req['user']=request.user.id
> cur_form=Tagform(data=cur_req, instance=cur_tag)
> if cur_form.is_valid():
> cur_form.save()

New description:

 I have Problem on changing a model with modelform and instance
 model form return form validate error:
 user with this title already exist

 model:
 {{{
 class Tag(models.Model):
 user = models.ForeignKey(User)
 title = models.CharField(max_length=765)
 create_time = models.DateTimeField(null=True, blank=True)
 status = models.IntegerField(null=True, blank=True)
 color = models.CharField(max_length=765, blank=True)
 cnt_member = models.IntegerField(null=True, blank=True)
 cnt_items = models.IntegerField(null=True, blank=True)
 def __unicode__(self):
 return self.title+ " || "+self.user.username
 class Meta:
 db_table = u'tbl_tag'
 unique_together=("user","title")
 }}}

 form:
 {{{
 class Tagform(forms.ModelForm):

 class Meta:
 model=Tag
 exclude = ('status','create_time')
 }}}

 view:
 {{{
 def change_tag_title(request):
 if request.POST and request.is_ajax():
 cur_id=request.POST["id"]
 cur_tag=Tag.objects.get(id=cur_id,user=request.user)
 cur_req=request.POST.copy()
 cur_req['user']=request.user.id
 cur_form=Tagform(data=cur_req, instance=cur_tag)
 if cur_form.is_valid():
 cur_form.save()
 }}}

--

Comment (by claudep):

 Please use preview and proper formatting.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19328: bug in code

[Django]

#19328: bug in code
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by claudep):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => invalid
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 See #19013 (and many others...)

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19330: change model instance with unique_together using modelform

[Django]

#19330: change  model instance with unique_together  using modelform
-+-
 Reporter:  molavy   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  modelform| Triage Stage:
  ,unique_together ,instance ,save,  |  Unreviewed
  change |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by molavy):

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


Comment:

 db :sqlite

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19330: change model instance with unique_together using modelform

[Django]

#19330: change  model instance with unique_together  using modelform
-+-
 Reporter:  molavy   |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Forms|Version:  1.4
 Severity:  Normal   |   Keywords:  modelform ,unique_together
 Triage Stage:   |  ,instance ,save, change
  Unreviewed |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 I have Problem on changing a model with modelform and instance
 model form return form validate error:
 user with this title already exist

 model:

 class Tag(models.Model):
 user = models.ForeignKey(User)
 title = models.CharField(max_length=765)
 create_time = models.DateTimeField(null=True, blank=True)
 status = models.IntegerField(null=True, blank=True)
 color = models.CharField(max_length=765, blank=True)
 cnt_member = models.IntegerField(null=True, blank=True)
 cnt_items = models.IntegerField(null=True, blank=True)
 def __unicode__(self):
 return self.title+ " || "+self.user.username
 class Meta:
 db_table = u'tbl_tag'
 unique_together=("user","title")


 form:

 class Tagform(forms.ModelForm):

 class Meta:
 model=Tag
 exclude = ('status','create_time')



 view:
 def change_tag_title(request):
 if request.POST and request.is_ajax():
 cur_id=request.POST["id"]
 cur_tag=Tag.objects.get(id=cur_id,user=request.user)
 cur_req=request.POST.copy()
 cur_req['user']=request.user.id
 cur_form=Tagform(data=cur_req, instance=cur_tag)
 if cur_form.is_valid():
 cur_form.save()

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19329: code broken

[Django]

#19329: code broken
---+--
 Reporter:  timbauer@… |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by anonymous):

 * status:  new => closed
 * needs_docs:   => 0
 * resolution:   => invalid
 * needs_tests:   => 0
 * needs_better_patch:   => 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 https://groups.google.com/groups/opt_out.

[Django] #19329: code broken

[Django]

#19329: code broken
---+
 Reporter:  timbauer@… |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 The following code from Tutorial 3 produces a type error ('str' object is
 not callable).


  from django.conf.urls import patterns, include, url

  from django.contrib import admin
  admin.autodiscover()

  urlpatterns = patterns('',
  url(r'^polls/', include('polls.urls')),
  url(r'^admin/', include(admin.site.urls)),
  )

 This happens even when the code is copied and pasted (everything worked
 fine prior to that change. The error code seems to specifically point at
 "include('poll.urls')." Have tried a couple of different things, including
 ditching the apostrophe's. The problem appears to stem from the something
 within Django itself

 C:\Python27\lib\site-packages\django\core\handlers\base.py in
 get_response, line 111

 is specifically where the error is being generated from.

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19328: bug in code

[Django]

#19328: bug in code
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 when running through this tutorial i ran into an issue at the top of page
 4.

 in the code snipet it uses:

 

 however this threw an error, i think it should be this:

 

 which seems to work

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19327: Admin doesn't handle double login attempts

[Django]

#19327: Admin doesn't handle double login attempts
-+-
 Reporter:  KJ   |Owner:  KJ
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
  sensitive_post_parameters, login   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by KJ):

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


Comment:

 I've created a pull request: https://github.com/django/django/pull/545

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19327: Admin doesn't handle double login attempts

[Django]

#19327: Admin doesn't handle double login attempts
+--
 Reporter:  KJ  |  Owner:  KJ
 Type:  Bug | Status:  new
Component:  |Version:  master
  contrib.admin |   Keywords:  sensitive_post_parameters, login
 Severity:  Normal  |  Has patch:  0
 Triage Stage:  Unreviewed  |  UI/UX:  0
Easy pickings:  1   |
+--
 When sending login form on admin site when user is already logged in,
 admin view gets called as if no login attempt was being made. Login form
 POST data can then easily cause some of the admin views to break.
 Furthermore, sensitive_post_parameters decorator isn't applied because
 login view doesn't get called, so if an exception is raised, a traceback
 is emailed with username and password in plain text.

 A real life example would be when user opens 2 tabs with login form, logs
 in on one of them and then forgets about it and tries to log in on the
 second.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18658: Better support for exceptions / error messages in custom admin actions

[Django]

#18658: Better support for exceptions / error messages in custom admin actions
-+-
 Reporter:  dbrgn|Owner:  thiderman
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  contrib.admin|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  admin, exception |  checkin
  handling, ui/ux, docs  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by Preston Holmes ):

 In [changeset:"3a0e0230f76131cf23c0fdd0b18f3dd718c0f62f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3a0e0230f76131cf23c0fdd0b18f3dd718c0f62f"
 [1.5.x] Fixed #18658 -- Improved ModelAdmin.message_user API

 Thanks to Lowe Thiderman for the patch and tests
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 3a0e02: [1.5.x] Fixed #18658 -- Improved ModelAdmin.messag...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 3a0e0230f76131cf23c0fdd0b18f3dd718c0f62f
  
https://github.com/django/django/commit/3a0e0230f76131cf23c0fdd0b18f3dd718c0f62f
  Author: Preston Holmes 
  Date:   2012-11-19 (Mon, 19 Nov 2012)

  Changed paths:
M AUTHORS
M django/contrib/admin/options.py
M docs/ref/contrib/admin/actions.txt
M docs/ref/contrib/admin/index.txt
M docs/releases/1.5.txt
M tests/regressiontests/admin_views/admin.py
M tests/regressiontests/admin_views/models.py
M tests/regressiontests/admin_views/tests.py

  Log Message:
  ---
  [1.5.x] Fixed #18658 -- Improved ModelAdmin.message_user API

Thanks to Lowe Thiderman for the patch and tests



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18658: Better support for exceptions / error messages in custom admin actions

[Django]

#18658: Better support for exceptions / error messages in custom admin actions
-+-
 Reporter:  dbrgn|Owner:  thiderman
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  contrib.admin|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  admin, exception |  checkin
  handling, ui/ux, docs  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by Preston Holmes ):

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


Comment:

 In [changeset:"edf7ad36faab8d45aafe1f96feaf46794de22fc1"]:
 {{{
 #!CommitTicketReference repository=""
 revision="edf7ad36faab8d45aafe1f96feaf46794de22fc1"
 Fixed #18658 -- Improved ModelAdmin.message_user API

 Thanks to Lowe Thiderman for the patch and tests
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] edf7ad: Fixed #18658 -- Improved ModelAdmin.message_user A...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: edf7ad36faab8d45aafe1f96feaf46794de22fc1
  
https://github.com/django/django/commit/edf7ad36faab8d45aafe1f96feaf46794de22fc1
  Author: Preston Holmes 
  Date:   2012-11-19 (Mon, 19 Nov 2012)

  Changed paths:
M AUTHORS
M django/contrib/admin/options.py
M docs/ref/contrib/admin/actions.txt
M docs/ref/contrib/admin/index.txt
M docs/releases/1.5.txt
M tests/regressiontests/admin_views/admin.py
M tests/regressiontests/admin_views/models.py
M tests/regressiontests/admin_views/tests.py

  Log Message:
  ---
  Fixed #18658 -- Improved ModelAdmin.message_user API

Thanks to Lowe Thiderman for the patch and tests



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19243: Edit GeoDjango Tutorial for consistency and style.

[Django]

#19243: Edit GeoDjango Tutorial for consistency and style.
--+
 Reporter:  shepdl|Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timo):

 Left a few trivial comments, English looks fine to me.

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 5b6db3: [1.5.X] Fixed typo in docs/ref/models/querysets.tx...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 5b6db35a7472d745c2878b77406c0b730ea362d7
  
https://github.com/django/django/commit/5b6db35a7472d745c2878b77406c0b730ea362d7
  Author: Anton Danilchenko 
  Date:   2012-11-19 (Mon, 19 Nov 2012)

  Changed paths:
M docs/ref/models/querysets.txt

  Log Message:
  ---
  [1.5.X] Fixed typo in docs/ref/models/querysets.txt

Backport of 76859e6eab from master



-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 76859e: Update docs/ref/models/querysets.txt

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 76859e6eab1e411d1b7cc92d8160e89df6375cfb
  
https://github.com/django/django/commit/76859e6eab1e411d1b7cc92d8160e89df6375cfb
  Author: Anton Danilchenko 
  Date:   2012-11-18 (Sun, 18 Nov 2012)

  Changed paths:
M docs/ref/models/querysets.txt

  Log Message:
  ---
  Update docs/ref/models/querysets.txt

Fix typo: replace "can can" to "can"


  Commit: 8b659e439b51953064a7a79924b4066e08d7127d
  
https://github.com/django/django/commit/8b659e439b51953064a7a79924b4066e08d7127d
  Author: Tim Graham 
  Date:   2012-11-19 (Mon, 19 Nov 2012)

  Changed paths:
M docs/ref/models/querysets.txt

  Log Message:
  ---
  Merge pull request #536 from 1st/patch-1

Fixed typo in docs/ref/models/querysets.txt


Compare: https://github.com/django/django/compare/c559c3c3b9fb...8b659e439b51

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 27ecab: [1.5.X] Fixed typo in docs/releases/1.5.txt

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 27ecabf73f82104dd7624a9321ea34b15e51d83d
  
https://github.com/django/django/commit/27ecabf73f82104dd7624a9321ea34b15e51d83d
  Author: Anton Danilchenko 
  Date:   2012-11-19 (Mon, 19 Nov 2012)

  Changed paths:
M docs/releases/1.5.txt

  Log Message:
  ---
  [1.5.X] Fixed typo in docs/releases/1.5.txt

Backport of 3bdb2ca560 from master



-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 3bdb2c: Update docs/releases/1.5.txt

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3bdb2ca5608d6530adbf91e7914e5d5e05acc07a
  
https://github.com/django/django/commit/3bdb2ca5608d6530adbf91e7914e5d5e05acc07a
  Author: Anton Danilchenko 
  Date:   2012-11-18 (Sun, 18 Nov 2012)

  Changed paths:
M docs/releases/1.5.txt

  Log Message:
  ---
  Update docs/releases/1.5.txt

Deleted word that used second time


  Commit: c559c3c3b9fb99c723a9e0d060ecebc805a6eb30
  
https://github.com/django/django/commit/c559c3c3b9fb99c723a9e0d060ecebc805a6eb30
  Author: Tim Graham 
  Date:   2012-11-19 (Mon, 19 Nov 2012)

  Changed paths:
M docs/releases/1.5.txt

  Log Message:
  ---
  Merge pull request #537 from 1st/patch-2

Fixed typo in docs/releases/1.5.txt


Compare: https://github.com/django/django/compare/1f1f60d12f78...c559c3c3b9fb

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19326: Add a first method to the QuerySet

[Django]

#19326: Add a first method to the QuerySet
-+-
 Reporter:  Wim Feijen   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  first|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

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


Comment:

 Something like this should work:
 {{{
 try:
 return self.filter(*args, **kwargs)[0]
 except IndexError:
 return None
 }}}

 I am not sure if the `IndexError` is correct error type...

 If .last() is needed then that is going to be a bit more problematic as
 you will need to revert all of the ordering clauses of the query.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19056: Admin password change page relies on user.username

[Django]

#19056: Admin password change page relies on user.username
-+
 Reporter:  russellm |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  contrib.admin|  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by russellm):

 * severity:  Normal => Release blocker
 * stage:  Unreviewed => Accepted


Comment:

 Good catch -- it's would also be worth doing a quick search for .username
 to see if there is anywhere else that the attribute is being used
 directly.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19323: Add django.contrib.redirects setting for turning redirect on/off.

[Django]

#19323: Add django.contrib.redirects setting for turning redirect on/off.
-+-
 Reporter:  Melevir  |Owner:  Melevir
 Type:  New feature  |   Status:  new
Component:  contrib.redirects|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  redirects,   | Triage Stage:
  is_active  |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by russellm):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Someday/Maybe
 * type:  Uncategorized => New feature
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 A reasonable idea, but we're hampered by the lack of a built in schema
 migration system.

 Marking it someday/maybe; once we have a built-in migration system, this
 sort of change will be easy to make, but in the meantime, it's a non-
 trivial change.

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19326: Add a first method to the QuerySet

[Django]

#19326: Add a first method to the QuerySet
--+
 Reporter:  Wim Feijen|  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:  first
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 Many times, get() is being used inside a try except Model.DoesNotExist
 clause. In order to save us lines of code and in order to prevent the
 Exception becoming common, a discussion followed which can be found here:

 https://groups.google.com/forum/?fromgroups=#!searchin/django-
 developers/first$20jacob/django-developers/3RwDxWKPZ_A/discussion

 According to our BDFL:

 After thinking a bit, I'm +1 on the idea, and I think
 `Queryset.first()` is the right name (which implies we should probably
 have a `last()` for completion).

 This mirrors the name used by a few other ORM/collection APIs that I
 think have really nice APIS:

 * SQLalchemy
 
(http://docs.sqlalchemy.org/en/rel_0_7/orm/query.html#sqlalchemy.orm.query.Query.first)
 * Storm
 (http://people.canonical.com/~therve/storm/storm.store.ResultSet.html#first)
 * Backbone (http://backbonejs.org/#Collection-Underscore-Methods /
 http://documentcloud.github.com/underscore/#first)

 If someone produces a patch I'll review it and commit it.

 Jacob

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19152: Add support to create database without template_postgis with PostGIS 2

[Django]

#19152: Add support to create database without template_postgis with PostGIS 2
--+
 Reporter:  claudep   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  GIS   |  Version:  1.4
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

 * needs_better_patch:  0 => 1


Comment:

 I just reviewed the pull request; I'd like to see one improvement and one
 explanation.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19152: Add support to create database without template_postgis with PostGIS 2

[Django]

#19152: Add support to create database without template_postgis with PostGIS 2
--+
 Reporter:  claudep   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  GIS   |  Version:  1.4
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by anonymous):

 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 https://groups.google.com/groups/opt_out.

Re: [Django] #19243: Edit GeoDjango Tutorial for consistency and style.

[Django]

#19243: Edit GeoDjango Tutorial for consistency and style.
--+
 Reporter:  shepdl|Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by claudep):

 Thanks, this looks very good (as seen by a non-native speaker). I'd still
 like a quick review by a native English speaker before the commit, if
 possible.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #17050: add id attribute to individual model divs in the admin index

[Django]

#17050: add id attribute to individual model divs in the admin index
---+-
 Reporter:  scytale|Owner:  thiderman
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  1
---+-

Comment (by thiderman):

 Pull request updated: https://github.com/django/django/pull/535

 I removed everything from the documentation, including the release note. I
 merged the tests into the `admin_views` test and tested againt the first
 two generic models (`Actor` and `Album`). This made for a much cleaner
 patch!

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19243: Edit GeoDjango Tutorial for consistency and style.

[Django]

#19243: Edit GeoDjango Tutorial for consistency and style.
--+
 Reporter:  shepdl|Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * owner:  shepdl =>
 * status:  reopened => new
 * stage:  Unreviewed => Accepted


-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #15760: Feature: JS Hooks for Dynamic Inlines

[Django]

#15760: Feature: JS Hooks for Dynamic Inlines
-+-
 Reporter:  mlavin   |Owner:
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  inlines jquery   | Triage Stage:  Accepted
  callback   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  1
Easy pickings:  0|
-+-
Changes (by per856):

 * needs_docs:  1 => 0


Comment:

 Updated this patch to current master, with some alterations. Added
 documentation.

 Patch: https://github.com/django/django/pull/542

 This fix also fixes accepted duplicate #19314

 Example usage:
 {{{
 django.jQuery(document).bind('formset_add.admin.my_widget',
 function(event, row_element) {
 my_widget_setup($('.my_widget', row_element));
 });
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19325: Make E-Mail Connection Overridable in AdminEmailHandler

[Django]

#19325: Make E-Mail Connection Overridable in AdminEmailHandler
--+
 Reporter:  hannesstruss  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  logging   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by claudep):

 * needs_docs:  0 => 1
 * needs_tests:  0 => 1
 * stage:  Unreviewed => Accepted


-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #9025: Nested Inline Support in Admin

[Django]

#9025: Nested Inline Support in Admin
---+
 Reporter:  pixelcort  |Owner:  Gargamel
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+

Comment (by Gargamel):

 @bjola, thanks again, bugs are always helpfull to learn :). About your
 'hack', I have thought about this too, but it makes the html so incredibly
 cluttered and very hard to handle, not to mention that jquery performance
 would nosedive when models get more complicated with such a massive DOM.
 So thats why I am now, as you said, trying to make the server side
 generate 1 sample formset for every inline used.

 Well, I'm glad to announce I have made some progress. It's not the most
 pythonic code I've ever written, but its ok and it seems to work
 perfectly. I still need to implement the whole error checking, templates
 and jquery shebang, so it won't be done for a while, but suggestions are
 always welcome. If anyone would like a diff to check my approach and maybe
 offer some suggestions, just ask :)

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19321: Add django.contrib.redirects setting for redirect status.

[Django]

#19321: Add django.contrib.redirects setting for redirect status.
-+-
 Reporter:  Melevir  |Owner:  Melevir
 Type:  New feature  |   Status:  new
Component:  contrib.redirects|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  redirects,   | Triage Stage:  Accepted
  status_code|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * version:  1.4 => master
 * needs_docs:   => 0
 * type:  Uncategorized => New feature
 * stage:  Unreviewed => Accepted


Comment:

 The trend is more to add a redirect_class (`HttpResponseRedirectBase`
 subclass) attribute instead of setting the status code directly (see
 #19277). But yes, this seems to be a reasonable feature to add.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19325: Make E-Mail Connection Overridable in AdminEmailHandler

[Django]

#19325: Make E-Mail Connection Overridable in AdminEmailHandler
--+--
 Reporter:  hannesstruss  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  logging   | Triage Stage:  Unreviewed
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by anonymous):

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


Comment:

 Pull request: https://github.com/django/django/pull/543

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19325: Make E-Mail Connection Overridable in AdminEmailHandler

[Django]

#19325: Make E-Mail Connection Overridable in AdminEmailHandler
--+-
 Reporter:  hannesstruss  |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Core (Other)  |Version:  master
 Severity:  Normal|   Keywords:  logging
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+-
 Users might want to use a different email backend for error logging than
 the default one configured in the settings, e.g. if the default backend
 uses unreliable/delayed delivery methods such as an asynchronous task
 worker.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18833: Model returns incorrect values from Postgres DB View

[Django]

#18833: Model returns incorrect values from Postgres DB View
-+-
 Reporter:  paul.ortman@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by paul.ortman@…):

 Replying to [comment:3 aaugustin]:
 > If `USE_TZ = True`, the database connection will be set to UTC, meaning
 aggregation will be performed in UTC.
 >
 > If `USE_TZ = False`, the database connection is set to `TIME_ZONE`.
 >
 > When you're connecting directly to PostgreSQL, the connection uses the
 system time zone.
 >
 > As a consequence, aggregating on a DateTimeField by day can return
 different values, since the day of a datetime depends on the time zone.


 Exactly the right diagnosis.  Changin USE_TZ to False returned all the
 expected information.  Thank you.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19314: JavaScript for Widget in added inline

[Django]

#19314: JavaScript for Widget in added inline
---+-
 Reporter:  per856 |Owner:  per856
 Type:  New feature|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  duplicate
 Keywords:  admin forms| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by per856):

 * status:  assigned => closed
 * resolution:   => duplicate


Comment:

 Yes, this is exactly #15760.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18375: F() doesn't work as expected across multijoin relations

[Django]

#18375: F() doesn't work as expected across multijoin relations
-+-
 Reporter:  FunkyBob |Owner:  akaariai
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 The patch is stale. The compare view is misleading, as it now compares my
 current master instead of the master at the time of when I created that
 patch... Maybe using that compare view isn't such a good idea after all.
 Updated patch available from here:
 
https://github.com/akaariai/django/commit/bf6f1def617176503f2fc1c1e81c45c4b1b6fff2

 As for what is the use case? Something like
 `People.objects.filter(friends__age__gt=F('friends__age') * 2)`. This of
 course can't be true for single join, but multijoin case returns any
 people who have friends with 2x difference in age. Not too realistic
 example, but to me it seems there could be some real use cases for this.

 IMO if we can get good notes about the backwards compatibility hack it
 doesn't cost us much in code complexity.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #12502: Diagram doesn't match text in Middleware documentation

[Django]

#12502: Diagram doesn't match text in Middleware documentation
---+
 Reporter:  petrilli   |Owner:
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by shai):

 I would like to point out that with the introduction of
 `process_template_response`, the middleware documentation has become
 unclear and ambiguous: I couldn't fathom, by reading it, if
 `process_template_response` calls are all made before `process_response`
 calls or instead of them. If the former, than my suggested diagram is no
 longer correct, and the true picture is even more complex.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19314: JavaScript for Widget in added inline

[Django]

#19314: JavaScript for Widget in added inline
---+
 Reporter:  per856 |Owner:  per856
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin forms| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by mlavin):

 This is a similar approach as #15760 which also contains an event for form
 deletion.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19314: JavaScript for Widget in added inline

[Django]

#19314: JavaScript for Widget in added inline
---+
 Reporter:  per856 |Owner:  per856
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin forms| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by per856):

 * has_patch:  0 => 1


Comment:

 Patch: https://github.com/django/django/pull/542

 My Widget uses this JS, which makes use of this patch:

 {{{
 jQuery(document).ready(function ($) {
 var setup = {
 basePath: '{% static "js/wymeditor/" %}',
 updateSelector: 'input[type=submit],',
 updateEvent: 'click',
 lang: '{{ language }}',
 skin: 'default',
 logoHtml: ''
 };
 {% if "__prefix__" not in name %}
 $('#id_{{ name }}').wymeditor(setup);
 {% else %}
 /* This is used in an empty form in the admin, that is used to
 clone new inline forms.
  * Django feature #19314 adds the admin_add_row event that is used
 here.
  */
 django.jQuery(document).unbind('admin_add_row.{{ name }}');
 django.jQuery(document).bind('admin_add_row.{{ name }}',
 function(event, row_element) {
 $('.{{ name }}', row_element).wymeditor(setup);
 });
 {% endif %}
 });
 }}}

 For the code above to work, the widget's render function adds {{{
 {'class': name} }}} to the attrs of the parent TextArea widget.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19056: Admin password change page relies on user.username

[Django]

#19056: Admin password change page relies on user.username
---+--
 Reporter:  russellm   |Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

 * status:  closed => reopened
 * 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 https://groups.google.com/groups/opt_out.

[Django] #19324: invalid session keys cause unnecessary empty records in django_session table

[Django]

#19324: invalid session keys cause unnecessary empty records in django_session
table
--+
 Reporter:  liangrubo@…   |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  contrib.sessions  |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 db session store calls self.create when no record is found for the session
 key, which causes an empty record inserted. Is this necessary? This gives
 chance to user to fill the session table with empty records by sending
 invalid session keys.

 is it more appropriate to set session_key to be None in this case?

 current implementation:
 {{{
 def load(self):
 try:
 s = Session.objects.get(
 session_key=self.session_key,
 expire_date__gt=timezone.now()
 )
 return self.decode(s.session_data)
 except (Session.DoesNotExist, SuspiciousOperation):
 self.create()
 return {}
 }}}

 suggested implementation:
 {{{
 def load(self):
 try:
 s = Session.objects.get(
 session_key=self.session_key,
 expire_date__gt=timezone.now()
 )
 return self.decode(s.session_data)
 except (Session.DoesNotExist, SuspiciousOperation):
 self.session_key = None
 return {}
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19056: Admin password change page relies on user.username

[Django]

#19056: Admin password change page relies on user.username
---+--
 Reporter:  russellm   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by gabejackson):

 this also applies to the 'title' context variable set in UserAdmin's def
 user_change_password(self, request, id, form_url=''): somewhere about:

 context = {
 'title': _('Change password: %s') % escape(user.username),
 'adminForm': adminForm,

 this should be changed to

 context = {
 'title': _('Change password: %s') %
 escape(user.get_username()),
 'adminForm': adminForm,

 i'm on the run right now, but perhaps somebody could commit that.

 Greetings,

 Gabe

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #6707: Another implementation for ReverseManyRelatedObjectsDescriptor.__set__ method

[Django]

#6707: Another implementation for ReverseManyRelatedObjectsDescriptor.__set__
method
-+-
 Reporter:  favo |Owner:  sfllaw
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by bberes):

 * cc: botondus@… (added)


Comment:

 Ran into this as well on multiple occasions.
 This basically makes the m2m_changed signal almost useless :(

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #4682: [patch] Add UuidField

[Django]

#4682: [patch] Add UuidField
-+-
 Reporter:  John Downey  |Owner:  nobody
 |   Status:  closed
 Type:  Uncategorized|  Version:  master
Component:  Database layer   |   Resolution:  wontfix
  (models, ORM)  | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:  uuid field   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by anonymous):

 +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 https://groups.google.com/groups/opt_out.

[Django] #19323: Add django.contrib.redirects setting for turning redirect on/off.

[Django]

#19323: Add django.contrib.redirects setting for turning redirect on/off.
---+--
 Reporter:  Melevir|  Owner:  Melevir
 Type:  Uncategorized  | Status:  new
Component:  contrib.redirects  |Version:  1.4
 Severity:  Normal |   Keywords:  redirects, is_active
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+--
 At the moment django.contrib.redirects doesn't allow to disable particular
 redirect.
 To do this I have do remove it completely or rename old_path to
 nonexistent. It neither clear nor correct.
 Good solution is to add is_active bool field with default=True.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19322: Django Import CSV

[Django]

#19322: Django Import CSV
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.3
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => invalid
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Please see TicketClosingReasons/UseSupportChannels.

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19322: Django Import CSV

[Django]

#19322: Django Import CSV
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.3
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I would like to import a CSV to another, eg. upload the csv to model
 MailingList and import the information to MailingListContact model. Tried
 using Django csvImporter library with no success.

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #19321: Add django.contrib.redirects setting for redirect status.

[Django]

#19321: Add django.contrib.redirects setting for redirect status.
---+
 Reporter:  Melevir|  Owner:  Melevir
 Type:  Uncategorized  | Status:  new
Component:  contrib.redirects  |Version:  1.4
 Severity:  Normal |   Keywords:  redirects, status_code
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 At the moment django.contrib.redirects redirects only with status
 301(Moved Permanently).
 It doesn't allow to use django.contrib.redirects if user needs temporary
 redirect (one of 302/303/307).
 This can be solved easily with with adding optional parameter
 REDIRECT_STATUS_CODE=301/302/303/307.
 It will make redirects middleware more flexible and convenient.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #19319: mod_wsgi docs need ...Require all granted (was: https://docs.djangoproject.com/en/dev/howto/deployment/wsgi/modwsgi/ need ...Require all gr

[Django]

#19319: mod_wsgi docs need  ...Require all granted
+--
 Reporter:  colinnkeenan@…  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Documentation   |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  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 https://groups.google.com/groups/opt_out.

Re: [Django] #19320: Ability to leverage cache key generation for cache templatetag

[Django]

#19320: Ability to leverage cache key generation for cache templatetag
-+
 Reporter:  Alex hayes   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Cache system)  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by aaugustin):

 * stage:  Unreviewed => Accepted


-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #17050: add id attribute to individual model divs in the admin index

[Django]

#17050: add id attribute to individual model divs in the admin index
---+-
 Reporter:  scytale|Owner:  thiderman
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  1
---+-

Comment (by thiderman):

 I agree about the test app creation. I'll merge them into `admin_views`
 and check for some of the existing models instead.
 Should I leave the release note in or should I remove that as well?

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #13978: Allow inline js/css in forms.Media

[Django]

#13978: Allow inline js/css in forms.Media
---+
 Reporter:  nathforge  |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Forms  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  sprintdec2010  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by dmpayton):

 I've updated this patch for the latest Django. Assuming I were to write
 docs and a test, could this feasibly make it into 1.5?

-- 
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 https://groups.google.com/groups/opt_out.