On 1/17/07, Isaac Alston <[EMAIL PROTECTED]> wrote:
> The problem is most likely with your MEDIA_URL. Make sure it ends with a '/' Thank you very much. That seems to be it fixed :-D. First I had MEDIA_URL set to: ' ' then '127.0.0.1:8000', then '127.0.0.1:8000/' then '/', then finally '/smedia' which got it working. I'm so happy :-). The only thing I'm concerned about is a) why didn't it want a URL and b) what's going to happen when I deploy? How will this change?
'/smedia' is a URL, so I don't understand your first question. To answer you second question, that all depends on how you deploy. For me, I have a "separate" server called media.awwca.ca, so my MEDIA_URL is 'http://media.awwca.ca/site_media/' (I put quotes around "separate" because physically, it's the same server, but this makes it easier on me if I ever want a physically separate server). Although if you're not doing that, then keeping it as '/smedia/' should be fine, assuming you really do serve your media out of there. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
