These were added in #3478 to ensure that numeric object IDs would not be affected by local number formatting; however, within widget templates, attrs.id refers to a string identifier, not a numeric ID.
According to a google search I just did, it seems a lot of people have forgotten to add ``Disallow: /admin`` in their robots.txt (or forgot to add robots.txt) at all.
Adding this meta tag into the head of all admin pages should prevent any admin pages being indexed even if this was missed.
The behaviour of `has_usable_password` has changed in Django 2.1, such that `None` is no longer considered a 'non-usable' password: https://docs.djangoproject.com/en/2.1/ref/contrib/auth/#django.contrib.auth.models.User.has_usable_password
As a consequence of the fix applied in Django https://code.djangoproject.com/ticket/28718 , Wagtail users created without a password will now be able to complete the password reset process to gain access to Wagtail. Sites that do not want this behaviour (e.g. because those users should be using an LDAP login instead) should disable password changes via WAGTAIL_PASSWORD_MANAGEMENT_ENABLED and WAGTAIL_PASSWORD_RESET_ENABLED.
In this case we just ignore the renderer; blocks have their own separate rendering mechanism, so it's not meaningful for that to be controlled by Django widget renderer classes.
* Upgrade gulp-sass to 4.0.1 and rebuild package-lock.json with npm 6
The only difference to the generated code appears to be in sourcemap data.
* Run npm audit to fix most vulnerable packages
Generated static files are unchanged by this update.
* Revert package-lock.json to npm 5 format
We currently guess that all OneToOneFields are integers and use string
for everything else.
This is usually not an issue as Elasticsearch coerces between strings an
integers automatically. But this causes issues for the new facet feature
as Elasticsearch returns strings for ID fields that are actually
integers.
The field type changes shouldn't cause any trouble for existing indices
as Elasticsearch will continue to automatically coerce the types. Users
who want to use the new facet feature on related fields will have to
rebuild their index.
