On Mon, 2006-08-28 at 13:55 -0700, [EMAIL PROTECTED] wrote:
[...]
> MEDIA_URL and MEDIA_ROOT still confuse me. For a FileField you are
> required to specify the "upload_to" path. Do you specify
> upload_to=settings.MEDIA_ROOT and use MEDIA_URL in the get_absolute_url
> method?
The upload_to set
> I think you are arriving at an understanding of why universally exposing
> MEDIA_URL is not always the right thing.
Yes. My big assumption was that it was intended for static media only.
Which I think a lot of new Django users make based on the name of the
setting.
MEDIA_URL and MEDIA_ROOT s
On Mon, 2006-08-28 at 11:58 -0700, [EMAIL PROTECTED] wrote:
[...]
> In that case, where would I put my media setting so I could refer to it
> from the templates? Make up my own setting in settings.py and write a
> context processor to make it available to the templates?
If it was something that
Malcolm Tredinnick wrote:
> Yes. Exactly. Or use one that somebody else wrote and posted to the Wiki
> or made available elsewhere. We just don't want to put a "retrieve
> settings" processor in core because we are making a judgement call about
> the security and usability implications (if it's in
On Mon, 2006-08-28 at 11:27 -0700, [EMAIL PROTECTED] wrote:
> I posted a reply to a wontfix bug and thought I'd also post it here for
> discussion.
> See bug: http://code.djangoproject.com/ticket/2532
>
> Here's the copy/paste of my argument:
>
> I agree that this should be there by default. I c
I posted a reply to a wontfix bug and thought I'd also post it here for
discussion.
See bug: http://code.djangoproject.com/ticket/2532
Here's the copy/paste of my argument:
I agree that this should be there by default. I can understand the
slippery slope argument, but this makes sense. Other set
