Do what has been suggested with using something like live http headers, but in particular pay close attention to the Content-Type header being returned for static files served from your /media directory. When using Apache the content types for such files will be dictated by Apache configuration and/or associated mime type files. It is possible that Django in standalone mode returns something a little different if it is serving up the static files in that case.
Graham On Jun 27, 1:34 am, waylan <[EMAIL PROTECTED]> wrote: > First check your browser settings. Is javascript enabled? Clear your > cache and then see if you can still load the js files directly. When > faced with situations like this I like to use the "Live HTTP Headers" > extension for Firefox to see whats really going on. Of course, you > could always avoid the browser and use wget (or curl) from the command > line to see if you can access the js files directly. If it is, in > fact, not a browser issue, report back and we'll see what we can do. > > Hmm, before sending I reread your message and it occurs to me that as > is works with the dev server but not through apache/mod_pythonthat > you may have some apache setting (cache related??) that's confusing > the browser. Although that doesn't make much sense if the css is > working. Either way, do the checks I suggest above and look closely at > the response headers from both servers. > > On Jun 26, 7:56 am, Eric St-Jean <[EMAIL PROTECTED]> wrote: > > > I have a weird problem where if i run django standalone, i see the > > calendar widget by a DateField entry in the admin form, but when run > > frommod_python, i lose it. (i lose the calendar date picking widget, > > and the "today" shortcut) > > /media *is* working - the css gets loaded properly. I'm using the same > > browser in both instances. If i load firebug, it sees the javascript > > files - i do think they are being served by apache along with the css ( > > i can look at them from the browser as well). But the widget doesn't > > appear, and i have to enter the date by hand. I was using the debian > > testing django (some form of 0.96), but then also tried trunk, with the > > same results (i even removed the deb package to be absolutely sure it > > wasn't used). > > This is django trunk (as of yesterday), with apache 2.2.3-4 and > >mod_python3.2.10-4, python 2.4.4-2 on debian 4.0. > > > Any quick ideas??? > > Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
