Re: [Django] #11843: MultipleHiddenInput outputs invalid HTML (inputs all get the same ID)

2009-09-06 Thread Django
#11843: MultipleHiddenInput outputs invalid HTML (inputs all get the same ID)
+---
  Reporter:  SmileyChris| Owner:  SmileyChris
Status:  assigned   | Milestone: 
 Component:  Forms  |   Version:  1.1
Resolution: |  Keywords: 
 Stage:  Ready for checkin  | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by SmileyChris):

  * needs_tests:  1 => 0
  * stage:  Accepted => Ready for checkin

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



Re: [Django] #11843: MultipleHiddenInput outputs invalid HTML (inputs all get the same ID)

2009-09-06 Thread Django
#11843: MultipleHiddenInput outputs invalid HTML (inputs all get the same ID)
--+-
  Reporter:  SmileyChris  | Owner:  SmileyChris
Status:  assigned | Milestone: 
 Component:  Forms|   Version:  1.1
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  1  
Needs_better_patch:  0|  
--+-
Changes (by SmileyChris):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 1
  * needs_docs:  => 0

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



[Django] #11843: MultipleHiddenInput outputs invalid HTML (inputs all get the same ID)

2009-09-06 Thread Django
#11843: MultipleHiddenInput outputs invalid HTML (inputs all get the same ID)
-+--
 Reporter:  SmileyChris  |   Owner:  SmileyChris
   Status:  new  |   Milestone: 
Component:  Forms| Version:  1.1
 Keywords:   |   Stage:  Unreviewed 
Has_patch:  1|  
-+--
 Yep, that's the gist of it. `CheckboxSelectMultiple` already has a fix for
 this, but not `MultipleHiddenInput`.

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



Re: [Django] #11842: django-admin.py should display help output when no arguments are given

2009-09-06 Thread Django
#11842: django-admin.py should display help output when no arguments are given
--+-
  Reporter:  bitprophet   | Owner:  nobody
Status:  new  | Milestone:
 Component:  django-admin.py  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by bitprophet):

  * needs_better_patch:  => 0
  * summary:  `django-admin.py` should display `--help` output when no
  arguments are given => django-admin.py should
  display help output when no arguments are given
  * needs_tests:  => 0
  * needs_docs:  => 0

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



[Django] #11842: `django-admin.py` should display `--help` output when no arguments are given

2009-09-06 Thread Django
#11842: `django-admin.py` should display `--help` output when no arguments are
given
-+--
 Reporter:  bitprophet   |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  django-admin.py  | Version:  SVN   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  1|  
-+--
 Ticket #378 mentions having `django-admin.py` honor Unix traditions -- and
 yet if you invoke it with no arguments, you get a profoundly unfriendly
 and non-Unix-like message:
 {{{
 $ django-admin.py
 Type 'django-admin.py help' for usage.
 }}}

 Compare to, say, `apt-get`:
 {{{
 $ apt-get
 apt 0.7.9ubuntu17.2 for i386 compiled on Apr 17 2009 16:29:24
 Usage: apt-get [options] command
apt-get [options] install|remove pkg1 [pkg2 ...]
apt-get [options] source pkg1 [pkg2 ...]

 [...]
 }}}

 or git:
 {{{
 $ git
 usage: git [--version] [--exec-path[=GIT_EXEC_PATH]] [-p|--paginate|--no-
 pager] [--bare] [--git-dir=GIT_DIR] [--work-tree=GIT_WORK_TREE] [--help]
 COMMAND [ARGS]

 [...]
 }}}

 I'm sure I didn't need to give examples, but I felt like being thorough :)

 The code related to this has not changed significantly since the 1.0.X
 branch -- i.e. the (tiny) patch applies cleanly to the latest 1.0.X branch
 checkout, as well as the latest SVN.

 I'm not seeing any tests that apply to django-admin.py at all, so not
 including one -- please point me to the right spot if I've missed
 something.

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



Re: [Django] #7501: template rendering doesn't reset cycle tag

2009-09-06 Thread Django
#7501: template rendering doesn't reset cycle tag
-+--
  Reporter:  mitsuhiko   | Owner:  nobody
Status:  new | Milestone:
 Component:  Template system |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by SmileyChris):

 This would be fixed by #6262 - and I consider the ticket there to contain
 the correct fix to 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 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---



Re: [Django] #11838: Make syncdb understand "initialdata" directory

2009-09-06 Thread Django
#11838: Make syncdb understand "initialdata" directory
+---
  Reporter:  skorpan| Owner:  nobody
  
Status:  new| Milestone:  1.2   
  
 Component:  Uncategorized  |   Version:  SVN   
  
Resolution: |  Keywords:  syncdb loaddata 
initial_data
 Stage:  Accepted   | Has_patch:  0 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  0  |  
+---
Changes (by russellm):

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

Comment:

 I can see the value in the idea, but I'd favor something more generic.
 Rather than making a special case of an 'initialdata' directory, make a
 directory a valid form for a fixture. That is, the loading sequence for
 `./manage.py loaddata foo` would be something like:

  * foo.json, foo.yaml etc for each registered serializer
  * foo.json.gz, foo.yaml.gz etc (i.e., look for the compressed fixture
  * a directory named foo that may contain fixtures.

 This would allow you to split your initial_data fixture over mutliple
 files as long as you called the fixture directory initial_data, but would
 also allow any other fixture to follow the same behavior.

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



[Django] #11841: Allow subclasses of AdminSite to overwrite all admin templates

2009-09-06 Thread Django
#11841: Allow subclasses of AdminSite to overwrite all admin templates
--+-
 Reporter:  pjanderson|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.1   
 Keywords:  AdminSite templates   |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 When creating custom admin sites, it is sometimes expected to modify each
 site's branding, if not the whole look of the custom admin site (by
 providing custom stylesheets.) AdminSite class allows to overwrite index,
 login and app_index templates in its subclasses, but not every template.

 Would it be possible to allow AdminSite subclasses to define all of its
 own templates? For example, I changed these three templates to provide
 custom branding for local, regional and worldwide content managers and
 administrators, but when viewing application records, default
 "change_list.html" template is used and it is extending default
 "base_site.html".

 Perhaps I haven't looked at the source code too closely, or maybe there is
 no way to do that quickly and simply.

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



[Django] #11840: Form validation should check for IOErrors

2009-09-06 Thread Django
#11840: Form validation should check for IOErrors
---+
 Reporter:  stavros|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Forms currently break on various types of images when PIL raises an
 IOError exception. This should be handled as a form error instead of
 crashing Django. A traceback is below:

   File "main/views.py", line 244, in ad_create_category
 if form.is_valid() and image_formset.is_valid():

   File "lib/python2.6/site-packages/django/forms/formsets.py", line
 237, in is_valid
 if bool(self.errors[i]):

   File "lib/python2.6/site-packages/django/forms/formsets.py", line
 211, in _get_errors
 self.full_clean()

   File "lib/python2.6/site-packages/django/forms/formsets.py", line
 250, in full_clean
 self._errors.append(form.errors)

   File "lib/python2.6/site-packages/django/forms/forms.py", line 111,
 in _get_errors
 self.full_clean()

   File "lib/python2.6/site-packages/django/forms/forms.py", line 238,
 in full_clean
 value = field.clean(value, initial)

   File "lib/python2.6/site-packages/django/forms/fields.py", line 511,
 in clean
 trial_image.load()

   File "lib/python2.6/site-packages/PIL/ImageFile.py", line 155, in
 load
 self.load_prepare()

   File "lib/python2.6/site-packages/PIL/PngImagePlugin.py", line 337,
 in load_prepare
 raise IOError("cannot read interlaced PNG files")

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



[Django] #11839: Strip tags from django document title elements

2009-09-06 Thread Django
#11839: Strip tags from django document title elements
---+
 Reporter:  glenjamin  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Quite a simple one this

 See http://docs.djangoproject.com/en/dev/ref/models/options/ for an
 example

 basically requires
 
http://code.djangoproject.com/browser/djangoproject.com/djangodocs/templates/docs/doc.html#L3
 to be given a |striptags filter.

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



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

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

  * needs_tests:  0 => 1
  * stage:  Ready for checkin => Accepted

Comment:

 The last comment makes this look not quite ready for checkin.  Also there
 are no tests in the latest patch, not even the earlier posted test changes
 required to fix test breakage, so it isn't clear what exactly is supposed
 to be applied.  This ticket needs a consolidated patch with tests for the
 new function before it can be called ready for checkin.

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



[Django] #11838: Make syncdb understand "initialdata" directory

2009-09-06 Thread Django
#11838: Make syncdb understand "initialdata" directory
--+-
 Reporter:  skorpan   |   Owner:  nobody
   Status:  new   |   Milestone:  1.2   
Component:  Uncategorized | Version:  SVN   
 Keywords:  syncdb loaddata initial_data  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 In many projects I often find the need to load my data from several
 separate JSON formatted data dumps.  This is because it's easier to manage
 dumps from different models separately.  Unfortunately, `syncdb` only
 understands one thing and that is a file named `initial_data.json`.  I
 think it would be better if `syncdb` looked for that file, uses it if it
 finds it, otherwise looks for a directory named `initialdata` and loads
 all of the files from that directory.

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