#13151: If ADMIN_MEDIA_PREFIX is not assigned, things don't work...documentation
should be updated
-----------------------------------------------------+----------------------
Reporter: [email protected] | Owner: nobody
Status: reopened | Milestone:
Component: Documentation | Version: 1.1
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------------------------+----------------------
Changes (by mlissner):
* status: closed => reopened
* resolution: wontfix =>
Comment:
It's not met b/c the documentation doesn't say that if the variable isn't
set, that it defaults to /media/. In my case, I didn't have the variable
(no idea why), and therefore things didn't work. It's a leap to go from
the sentence that's there to the realization that not having the variable
set will cause permission denied errors. Perhaps a reasonable (and minor)
change would be to change this sentence:
"Be careful not to use the same path as your ADMIN_MEDIA_PREFIX (which
defaults to /media/) as this will overwrite your URLconf entry."
To:
"Be careful not to use the same path as your ADMIN_MEDIA_PREFIX (which
defaults to /media/ if it is not set) as this will overwrite your URLconf
entry."
I guess in hindsight, I see that the sentence above clarifies the issue I
was having, but checking google does indicate that I'm not alone in this:
http://www.google.com/search?hl=en&hs=ebV&q=admin_media_prefix+%22permission+denied%22
--
Ticket URL: <http://code.djangoproject.com/ticket/13151#comment:4>
Django <http://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 post to this group, send email to [email protected].
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.
