Re: [Django] #5172: Extend the {% for %} tag to work as a simple loop

[Django]

#5172: Extend the {% for %} tag to work as a simple loop
-+--
  Reporter:  SmileyChris | Owner:  nobody   
  
Status:  closed  | Milestone:   
  
 Component:  Template system |   Version:  SVN  
  
Resolution:  wontfix |  Keywords:  for-tag 
enhancement feature
 Stage:  Design decision needed  | Has_patch:  1
  
Needs_docs:  1   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by ubernostrum):

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

Comment:

 Please do not reopen a ticket that's been marked "wontfix" by a core
 developer; if you strongly disagree, consider starting a discussion on the
 developers' mailing list.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9052: Managing Files doc typo

[Django]

#9052: Managing Files doc typo
+---
  Reporter:  KiWiB0RG   | Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution:  fixed  |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 (In [9018]) Fixed #9052: Corrected typo in file handling docs. Thanks to
 KiWiB0RG for the report.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Changeset] r9018 - django/trunk/docs/topics

[noreply]

Author: russellm
Date: 2008-09-14 01:49:28 -0500 (Sun, 14 Sep 2008)
New Revision: 9018

Modified:
   django/trunk/docs/topics/files.txt
Log:
Fixed #9052: Corrected typo in file handling docs. Thanks to KiWiB0RG for the 
report.

Modified: django/trunk/docs/topics/files.txt
===
--- django/trunk/docs/topics/files.txt  2008-09-12 16:56:09 UTC (rev 9017)
+++ django/trunk/docs/topics/files.txt  2008-09-14 06:49:28 UTC (rev 9018)
@@ -35,7 +35,7 @@
 Any ``Car`` instance will have a ``photo`` attribute that you can use to get at
 the details of the attached photo::
 
->>> car = Car.object.get(name="57 Chevy")
+>>> car = Car.objects.get(name="57 Chevy")
 >>> car.photo
 
 >>> car.photo.name


--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9078: Paste-friendly listing in sitemaps docs

[Django]

#9078: Paste-friendly listing in sitemaps docs
--+-
 Reporter:  [EMAIL PROTECTED]  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Documentation | Version:  1.0   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 At http://docs.djangoproject.com/en/dev/ref/contrib/sitemaps/#creating-a
 -sitemap-index there is listing that can be copy-pasted to URLconf for
 common sites. But there is no "," symbol at line ends.

 It is not a bug ot smth, but it can steal several seconds from someone

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9074: The submit line on a change form in the admin site is not rendered correctly if it only contains the Save button

[Django]

#9074: The submit line on a change form in the admin site is not rendered
correctly if it only contains the Save button
---+
  Reporter:  varikin   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  SVN   
Resolution:|  Keywords:  newforms-admin
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by varikin):

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

Comment:

 I found that the popups only have a save button that is rendered
 correctly.  This is because the submit-row div has "overflow: auto;" set
 for the style in the html.  Doing the same in my template solves my issue,
 but I am wondering if that should then be added to the globals.css instead
 of set in the html.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9064: Redirect is broken when HTTP_X_FORWARDED_HOST contains multiple hosts

[Django]

#9064: Redirect is broken when HTTP_X_FORWARDED_HOST contains multiple hosts
+---
  Reporter:  Artur  | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Changes (by [EMAIL PROTECTED]):

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

Comment:

 The current patch seems to work. It's meant to patch against {{{
 trunk/django/http/__init__.py }}}.

 However, the patch doesn't specify which file it's applied to. Please
 resubmit with the proper directory hierarchy information.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9077: pysqlite link on "How to install Django" may be wrong

[Django]

#9077: pysqlite link on "How to install Django" may be wrong
-+--
 Reporter:  velo |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Documentation| Version:  1.0   
 Keywords:  possible link error  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 Here is the html I am speaking of:

 {{{
 If you’re using SQLite and either Python 2.3 or
 Python 2.4, you’ll need

 http://initd.org/tracker/pysqlite";>pysqlite. Use version 2.0.3
 or higher. Python 2.5 ships with an SQLite
 wrapper in the standard library, so you don’t need to install
 anything extra
 in that case.}}}

 It takes me to the psycopg package instead.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #5172: Extend the {% for %} tag to work as a simple loop

[Django]

#5172: Extend the {% for %} tag to work as a simple loop
-+--
  Reporter:  SmileyChris | Owner:  nobody   
  
Status:  reopened| Milestone:   
  
 Component:  Template system |   Version:  SVN  
  
Resolution:  |  Keywords:  for-tag 
enhancement feature
 Stage:  Design decision needed  | Has_patch:  1
  
Needs_docs:  1   |   Needs_tests:  0
  
Needs_better_patch:  0   |  
-+--
Changes (by danielcristian):

 * cc: [EMAIL PROTECTED] (added)
  * status:  closed => reopened
  * resolution:  wontfix =>

Comment:

 I had this model:

 {{{
 class Mana(models.Model):
 name = models.CharField(u'Mana', max_length=200, unique=True)
 image = models.ImageField(u'Symbol', upload_to='manas/')

 class Cost(models.Model):
 card = models.ForeignKey(Card)
 quantity = models.IntegerField('Quantity', max_length=2)
 mana = models.ForeignKey(Mana, related_name=u'mana',
 verbose_name=u'Mana')
 }}}

 (Yes, it's related to Magic Cards...)

 Some cards had a cost with a quantity value (1 Forest, 3 Islands, 5
 Mountains), and I need to loop quantity times to show n-times the image
 cost.

 It could be done with this kind of loop.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #3987: ModelAdmin should allow for overriding of ForeignKey/ManyToMany options

[Django]

#3987: ModelAdmin should allow for overriding of ForeignKey/ManyToMany options
---+
  Reporter:  Baptiste <[EMAIL PROTECTED]>  | Owner:  nobody 
   
Status:  reopened  | Milestone: 
   
 Component:  django.contrib.admin  |   Version:  
newforms-admin
Resolution:|  Keywords:  
nfa-someday   
 Stage:  Design decision needed| Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  1  
   
Needs_better_patch:  1 |  
---+
Changes (by mwdiers):

  * needs_better_patch:  0 => 1
  * needs_tests:  0 => 1
  * stage:  Someday/Maybe => Design decision needed

Comment:

 Sorry. Had some superfluous code in that example. Updated version for
 reference:

 {{{
 #!python
 class SiteAdmin(ModelAdmin):
 def __call__(self, request, url):
 #Add in the request object, so that it may be referenced
 #later in the formfield_for_dbfield function.
 self.request = request
 return super(SiteAdmin, self).__call__(request, url)

 def formfield_for_dbfield(self, db_field, **kwargs):
 field = super(SiteAdmin, self).formfield_for_dbfield(db_field,
 **kwargs) # Get the default field
 if db_field.name == 'home_page':
 #Add the null object
 my_choices = [('', '-')]
 #Grab the current site id from the URL.
 
my_choices.extend(Page.objects.filter(site=self.request.META['PATH_INFO'].split('/')[-2]).values_list('id','name'))
 print my_choices
 field.choices = my_choices
 return field
 }}}

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8903: admin.TabularInline creates duplicate pk input boxes

[Django]

#8903: admin.TabularInline creates duplicate pk input boxes
---+
  Reporter:  Spads | Owner:  nobody 
Status:  new   | Milestone: 
 Component:  django.contrib.admin  |   Version:  1.0
Resolution:|  Keywords:  admin TabularInline
 Stage:  Unreviewed| Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by kratorius):

 Since dpaste is going to delete the code in the near future, here's the
 test case:

 {{{
 #!python
 class NetworkInterface(models.Model):
 location = models.ForeignKey(Equipment, verbose_name="system")
 ip = models.IPAddressField("IP address", primary_key=True,
 default='127.0.0.1')
 mac = models.CharField("MAC address", max_length=17, unique=True,
 default='02:00:00:00:00:01')
 interface_name = models.CharField(max_length=15, default="eth0")
 media_settings = models.CharField(max_length=10, blank=True,
 default='HURG')
 def __unicode__(self):
 return unicode(u'%s %s: %s', location, self.interface_name,
 self.ip)
 }}}

 {{{
 #!python
 class NetworkInterface_Inline(admin.TabularInline):
 model = models.NetworkInterface
 fk_name = 'location'

 class EquipmentOptions(admin.ModelAdmin):
 inlines = [NetworkInterface_Inline, PowerSupply_Inline, Memory_Inline,
 Processor_Inline]

 admin.site.register(models.Equipment, EquipmentOptions)
 }}}

 Producing:
 {{{
 

  


   


   


   


   


 
 }}}

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #3987: ModelAdmin should allow for overriding of ForeignKey/ManyToMany options

[Django]

#3987: ModelAdmin should allow for overriding of ForeignKey/ManyToMany options
---+
  Reporter:  Baptiste <[EMAIL PROTECTED]>  | Owner:  nobody 
   
Status:  reopened  | Milestone: 
   
 Component:  django.contrib.admin  |   Version:  
newforms-admin
Resolution:|  Keywords:  
nfa-someday   
 Stage:  Someday/Maybe | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by mwdiers):

 There is a serious problem with this patch. It changes the
 formfield_for_dbfield method of ModelAdmin, requiring a request object to
 passed in as a positional argument. This method is not in the docs, but it
 is commonly overridden, and represents a significant change to the API for
 the Admin.

 There is a way to do what this patch does on 1.0, without any patching:

 {{{
 class SiteAdmin(ModelAdmin):
 def __call__(self, request, url):
 #Add in the request object, so that it may be referenced
 #later in the formfield_for_dbfield function.
 self.request = request
 return super(SiteAdmin, self).__call__(request, url)

 def get_form(self, request, obj=None):
 form = super(SiteAdmin, self).get_form(request, obj)
 #print form
 return form

 def formfield_for_dbfield(self, db_field, **kwargs):
 field = super(SiteAdmin, self).formfield_for_dbfield(db_field,
 **kwargs) # Get the default field
 if db_field.name == 'home_page':
 #Add the null object
 my_choices = [('', '-')]
 #Grab the current site id from the URL.
 
my_choices.extend(Page.objects.filter(site=self.request.META['PATH_INFO'].split('/')[-2]).values_list('id','name'))
 print my_choices
 field.choices = my_choices
 return field
 }}}

 The trick is the override of _ _call_ _, adding the request object as an
 attribute of the instance. Once you have this, you can do pretty much
 anything you need in the formfield_for_dbfield override. Granted, this is
 not very elegant. But it works in 1.0, and our users are already
 accustomed to overriding formfield_for_dbfield to make custom form tweaks.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9076: Inline forms can result in a "Please correct the errors below." message with no errors listed.

[Django]

#9076: Inline forms can result in a "Please correct the errors below." message
with no errors listed.
---+
 Reporter:  coady  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 This error can reproduced with the poll app in the tutorial with a minor
 change.  Remove the choice field from the Choice model (file attached).
 Edit a poll by adding two choices; enter any numbers in the votes fields.
 Any subsequent save will result in the "Please correct the errors below."
 message with no highlighted errors.

 The problem occurs in BaseModelFormSet._construct_form where an index
 access on the queryset is returning duplicate pks.  This in turn leads to
 validation failing in BaseModelForm.validate_unique.  The error occurs in
 1.0 and the trunk, probably introduced around the time core=True was
 removed.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9075: Missing destination.close()

[Django]

#9075: Missing destination.close()
---+
 Reporter:  bmsleight  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 In page http://docs.djangoproject.com/en/dev/topics/http/file-uploads/

 {{{
 def handle_uploaded_file(f):
 destination = open('some/file/name.txt', 'wb+')
 for chunk in f.chunks():
 destination.write(chunk)
 }}}

 IMHO should read:-
 {{{
 def handle_uploaded_file(f):
 destination = open('some/file/name.txt', 'wb+')
 for chunk in f.chunks():
 destination.write(chunk)
 destination.close()
 }}}

 Regards,
 Brendan

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8768: Document that ugettext_lazy returns `` in non-unicode string context

[Django]

#8768: Document that ugettext_lazy returns `` in non-unicode string context
+---
  Reporter:  mrts   | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by mk):

 The patch only mentions force_unicode(), but unicode() would be enough.

 {{{
 >>> unicode(ugettext_lazy(u'Some string'))
 u'Some string'
 }}}

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #3987: ModelAdmin should allow for overriding of ForeignKey/ManyToMany options

[Django]

#3987: ModelAdmin should allow for overriding of ForeignKey/ManyToMany options
---+
  Reporter:  Baptiste <[EMAIL PROTECTED]>  | Owner:  nobody 
   
Status:  reopened  | Milestone: 
   
 Component:  django.contrib.admin  |   Version:  
newforms-admin
Resolution:|  Keywords:  
nfa-someday   
 Stage:  Someday/Maybe | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by mwdiers):

 * cc: mwdiers (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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9074: The submit line on a change form in the admin site is not rendered correctly if it only contains the Save button

[Django]

#9074: The submit line on a change form in the admin site is not rendered
correctly if it only contains the Save button
+---
 Reporter:  varikin |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Contrib apps| Version:  SVN   
 Keywords:  newforms-admin  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 I have a custom template/view/form in the admin site which only has the
 save button in the submit row.  The gray box that should contain all the
 buttons is collapses with the Save button rendered over/below the gray
 box.  See the attached image for a screenshot.  I am also attaching my
 template, view, and form to ease reproducing.

 The issue seems to stem from "float: right" set to the button with
 "input[type=submit].default" in admin/media/globals.css.  Removing the
 "float: right" though makes the save button appear as the left most button
 with multiple buttons on the submit row and the delete button is messed
 up.  To fix that, I also updated the submit_line.html template to have the
 Save button last in the list.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9006: QuerySet indexing by __getitem__ gets wrong answer in edge cases

[Django]

#9006: QuerySet indexing by __getitem__ gets wrong answer in edge cases
-+--
  Reporter:  smoluf  | Owner:  nobody 
Status:  new | Milestone: 
 Component:  Core framework  |   Version:  1.0
Resolution:  |  Keywords:  queryset index race
 Stage:  Unreviewed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Comment (by anonymous):

 I encountered the similar problem with my web application. The cause of
 error is the unpredictable order of the returned rows.
 During {{{__getitem__}}}
  calling if the indexed item is absent in the cache, the queryset object
 is cloning and building new sql expression with new OFFSET value and LIMIT
 1. The builded expression doesn't include ORDER BY part, so in general SQL
 backend can return any row.
 The best solution that I found is to add
 {{{
 class Meta:
   ordering = ['id']
 }}}
 to the model definition.
 Maybe framework have to do it by default for models without specified
 ordering?

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9072: Outdated link in 'Writing models' documentation

[Django]

#9072: Outdated link in 'Writing models' documentation
---+
  Reporter:  Piotr Lewandowski <[EMAIL PROTECTED]>  | Owner:  
nobody
Status:  closed| Milestone: 
   
 Component:  Documentation |   Version: 
 1.0   
Resolution:  duplicate |  Keywords: 
   
 Stage:  Unreviewed| Has_patch: 
 0 
Needs_docs:  0 |   Needs_tests: 
 0 
Needs_better_patch:  0 |  
---+
Changes (by julien):

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

Comment:

 Dupe of #9007. The model examples have gone and need to be restored.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9071: Can't disable "add" popup links in the admin

[Django]

#9071: Can't disable "add" popup links in the admin
---+
  Reporter:  jacob | Owner:  kratorius
Status:  new   | Milestone:   
 Component:  django.contrib.admin  |   Version:  1.0  
Resolution:|  Keywords:  pyconuk  
 Stage:  Unreviewed| Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by kratorius):

  * has_patch:  0 => 1

Comment:

 Attached patch adds an {{{exclude_add}}} option (I'm not happy with the
 naming, any suggestion is welcome) that allows to specify which related
 fields shouldn't have the add image. Fields should be specified in a list,
 like {{{exclude_add = [ 'rel_field1', 'rel_field2' ]}}}.

 However, docs are missing since I'm not a native english-speaker, so it
 would be nice if someone else could do that.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8974: ModelChoiceField raises "ValueError: invalid literal for int() with base 10: 'abc'" when non-numerical value is supplied

[Django]

#8974: ModelChoiceField raises "ValueError: invalid literal for int() with base
10: 'abc'" when non-numerical value is supplied
+---
  Reporter:  burp_  | Owner:  nobody
Status:  new| Milestone:
 Component:  Uncategorized  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

 * cc: [EMAIL PROTECTED] (added)
  * needs_better_patch:  => 0
  * 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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9073: [9002] broke modeladmin tests

[Django]

#9073: [9002] broke modeladmin tests
+---
 Reporter:  kratorius   |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Testing framework   | Version:  1.0   
 Keywords:  modeladmin, admin, validationerror  |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 [9002] fixed a wrong error message being thrown when admin
 prepopulated_fields referred to a field that does not exist. However the
 tests has not been changed to reflect this. Attached patch fixes this
 issue.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9072: Outdated link in 'Writing models' documentation

[Django]

#9072: Outdated link in 'Writing models' documentation
--+-
 Reporter:  Piotr Lewandowski <[EMAIL PROTECTED]>  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Documentation | Version:  1.0   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 On the [http://docs.djangoproject.com/en/dev/topics/db/models/ Writing
 models] page you have '''See also''' box (at the beggining) which contains
 link to [http://www.djangoproject.com/documentation/models/ official
 repository of model examples]. This links seems to be outdated.

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9071: Can't disable "add" popup links in the admin

[Django]

#9071: Can't disable "add" popup links in the admin
---+
  Reporter:  jacob | Owner:  kratorius
Status:  new   | Milestone:   
 Component:  django.contrib.admin  |   Version:  1.0  
Resolution:|  Keywords:  pyconuk  
 Stage:  Unreviewed| Has_patch:  0
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by kratorius):

  * owner:  nobody => kratorius
  * needs_better_patch:  => 0
  * 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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9071: Can't disable "add" popup links in the admin

[Django]

#9071: Can't disable "add" popup links in the admin
--+-
 Reporter:  jacob |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.0   
 Keywords:  pyconuk   |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 There's no way to prevent the little green "plus" icons from appearing on
 related fields in the admin (well, other than removing the related object
 from the admin). It should be possible to prevent those from appearing --
 an admin option would make sense 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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9070: the value of parse_until will be overwritten when using a block in a loop of {%include%}

[Django]

#9070: the value of parse_until will be overwritten when using a block in a loop
of {%include%}
--+-
 Reporter:  ledil <[EMAIL PROTECTED]>  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Template system   | Version:  0.96  
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Ive tried the columnize tag
 (http://code.djangoproject.com/wiki/ColumnizeTag) in my template.
 Everything works if I use it in one template file:

 #mytemplate.html

 {% load columnize %}
 {% for item in items %}
 {%columnize 13%}
 
 {%endcolumnize%}
 {% endfor %}

 But the problem is when I put the stuff in the {%for%}-loop in an external
 template file like this:

 #myinternalloop.html
 {% load columnize %}
 {% columnize 13%}
 
 {% endcolumnize%}

 #mytemplate.html

 {% for item in items %}
 {% include "myinternalloop.html" %}
 {% endfor %}

 Ive tried to debug and it seems that "parse_until" seems to lose
 {%endcolumnize%} and this results in that columnize will never start again
 when traversing a new item. It will continue there where it stops on the
 previous item. (__init__.py of ColumnizeNode will not be called)

-- 
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---