jsi18n loading from templates within django/contrib/admin/templates/ shouldn't use "../"s

[greatlemer <greatlemer+django@…>]

When creating a custom change_form.html for use on a different url to the usual create item locations I discovered that the jsi18n scripts were failing to load (side effecting various elements on the page such as many to many selectors collapsable fieldsets). I tracked this down to the fact that the javascript was being loaded relative to the location of the page. After further investigation I noticed that the following templates also used the same style of importing for javascript (all within the django/contrib/admin/templates directory).
admin/auth/user/change_password.html
admin/change_form.html
admin/change_list.html

Is it possible that these imports could be altered to use some sort of url reversal?

The svn version I have checked this against was 11231 although it seems to be there in 1.0.2 also.

[Ramiro Morales]

Patch for this issue, it depends on recent patch for #10061 from Russell being applied first

[Ramiro Morales]

With #10061 fixed on r11250, now the patch should work when applied to trunk after hat revision. Please report back your experiences with it if you manage to give it a try.

[greatlemer <greatlemer+django@…>]

That patch seems to do the job. The javascript is now loading fine for me wherever I access it from.

Thanks!

[Jannis Leidel]

(In [12138]) Fixed #11478 - Use namespacing for URLs to i18n JavaScript in admin.

[Jannis Leidel]

(In [12238]) [1.1.X] Fixed #11478 - Use namespacing for URLs to i18n JavaScript in admin.

[philomat]

Could/should the i18n_javascript() method of AdminSite be improved to include JS catalogs from all or selected INSTALLED_APPS? The way it is now, you can easily create the appropriate JS message files as desribed in the Django manual, but only the package "django.conf" is loaded by said method.

Actually loading your custom catalog for the admin is a bit tedious now. You basically have to duplicate said method and add a custom URL to your ModelAdmin and put a script tag in the corresponding admin template.