[Django] #27786: Uploading dependent on the user

5 views
Skip to first unread message

Django

unread,
Jan 27, 2017, 11:03:34 AM1/27/17
to django-...@googlegroups.com
#27786: Uploading dependent on the user
------------------------------------------------+------------------------
Reporter: Victor Porton | Owner: nobody
Type: New feature | Status: new
Component: File uploads/storage | Version: 1.10
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
I want uploading files to depend on the user ID in the session.

I need it to make files uploaded by a user not accessible by other users
(without a special permission).

I realize this requires massive changes in Django API. Particularly, we
need to associate a user (or a session) with every ModelForm (in order
that the `save()` method could be able to behave differently for different
users.

It also requires changes in storage API itself.

Please discuss the details of the API.

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

Django

unread,
Jan 27, 2017, 12:27:22 PM1/27/17
to django-...@googlegroups.com
#27786: Uploading dependent on the user
-------------------------------------+-------------------------------------

Reporter: Victor Porton | Owner: nobody
Type: New feature | Status: closed
Component: File | Version: 1.10
uploads/storage |
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 Claude Paroz):

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


Comment:

What you describe are the general requirements of your application. We are
not going to specifically tailor Django to your needs.

However, if you can describe a generic use case which might require some
change in Django itself, feel free to discuss it on mailing lists, then
create a ticket with the proposal if you can get some common agreement on
that new feature.

--
Ticket URL: <https://code.djangoproject.com/ticket/27786#comment:1>

Reply all
Reply to author
Forward
0 new messages