Use staticfiles_storage to generate static files urls for widgets.
Hi,
Currently the urls for the widgets assets aren't processed by the project's defined static file storage (STATICFILES_STORAGE in the settings) and so, when using a custom static file storage (like django-s3-storage), the generated urls results in 404.
I sent these file paths through django.contrib.staticfiles.storage.staticfiles_storage.url to address this issue.
This fixed a bug I had where the assets for the admin widget would point to /admin/app/model/id/django_markdown/... instead of https://s3-eu-west-1.amazonaws.com/bucket/static/django_markdown/... (I use S3 storage) and thus the widget would render as a simple textarea.
@klen any thoughts on this pr ?
Also, I don't really know why Travis crashes during the coverage test (https://travis-ci.org/klen/django_markdown/jobs/86011076), any idea ?
Same problem here I ended up creating my own AdminMarkdownWidget with support for django-storages and extending the package class.