Previously js option produced script blocks using verbatim path. Example:
class Document(meta.Model):
# fields
class META:
admin = meta.Admin(
js = (
'/tinymce/jscripts/tiny_mce/tiny_mce_gzip.php',
),
)
produced:
<script type="text/javascript" src="/tinymce/jscripts/tiny_mce/tiny_mce_gzip.php"></script>
New admin produces different string:
<script type="text/javascript" src="/media//tinymce/jscripts/tiny_mce/tiny_mce_gzip.php"></script>
Essentially it is the same js path but it is now prefixed by /media/. It is easy to correct in my case: change symlink, and remove leading '/' in js.
Anyway we have a backward-incompatible difference. We have to decide how to handle it: old way or new way. The final decision should be documented.
New way is not bad. You can argue that it reduces number of entries in .htaccess or whatever non-Django mechanism is used for file serving. But it forces to change existing model files, which use extra JavaScript for Admin interface.