Actually, a widget required a js file that required core.js, but did not specify it. So I added core.js to the form's media list - but apparently it renders the widget media, then the form media - so no good.
Your second suggestion was the best - I now just include the jsi18n and core.js on every page as part of the base template. So far so good. Hopefully I won't find any more widgets with surprise dependencies. -Todd Blanchard On Nov 25, 2009, at 12:14 PM, Tim Valenta wrote: > Is it a widget that has the "core.js"? I'd suggest putting that on > the form instead, if that's the case. Alternatively, if the page > should always have this JS anyway, you could always insert it directly > to the template, to avoid any ambiguity for any future eyeballs > wondering how it all works. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
