#24105: When upload_to is callable, storage.get_valid_name() does not get called
-------------------------------------+-------------------------------------
     Reporter:  jbowen7              |      Owner:  nobody
         Type:  Bug                  |     Status:  new
    Component:  Database layer       |    Version:  1.7
  (models, ORM)                      |   Keywords:  upload_to,
     Severity:  Normal               |  get_valid_name
 Triage Stage:  Unreviewed           |  Has patch:  1
Easy pickings:  0                    |      UI/UX:  0
-------------------------------------+-------------------------------------
 == Module: db.models.fields.files.py ==

 Present in recent commits of versions 1.8 and 1.7
 Commit: c1493879d98328040b36ad93cd104c0b3b546772
 Commit: bbcbacf0ad4fc9aa89d13c35f4b084185b284a49

 Summary summed it up. But maybe the Storage class should be calling
 get_valid_name like the docs suggest. -see (_save)
 [https://docs.djangoproject.com/en/1.7/howto/custom-file-storage/]
 {{{
 "_save(name, content)ΒΆ
 Called by Storage.save(). The name will already have gone through
 get_valid_name() and get_available_name(), and the content will be a File
 object itself."
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/24105>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.30336234a7307f30dfcb2d298cea4eef%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to