Upgrading to wagtail 1.6 breaks, with DEBUG=False and ManifestStaticFilesStorage as STATICFILES_STORAGE

After upgrading to wagtail 1.6 wagtail admin fails to load a bunch of JS scripts. None of the files specified in wagtailadmin/templates/wagtailadmin/pages/_editor_js.html is rendered on to the edit or create page HTML.

Found that this Django setting was causing it

DEBUG=False
STATICFILES_STORAGE = 'django.contrib.staticfiles.storage.ManifestStaticFilesStorage'

Switching to a normal Django static storage works. but we would like to fingerprint our assets. This also prevents us from using custom static files storage like whitenoise. This was not an issue with the previous versions of wagtail (1.5.3).

Setup

• Python 3.4
• Django 1.8.13
• Wagtail 1.6

Steps to reproduce

pip install django==1.8
wagtail start clean
python3 manage.py migrate

Edit the settings to

DEBUG=False
STATICFILES_STORAGE = 'django.contrib.staticfiles.storage.ManifestStaticFilesStorage'

python manage.py collectstatic --clear
python manage.py runserver 8000

@gasman @alexgleason @m1kola can you guys take a look ?

[gasman]

As an immediate workaround, creating a blank admin/js/vendor/xregexp/xregexp.min.js file in one of your app’s static directories would probably work. That way, _editor_js.html will render correctly, but the JS code will still fall back on the non-Unicode Django 1.8 version, as it would if xregexp.min.js was a 404.

[m1kola]

Fixed in #2937

Thanks for reporting!