Platform 2019.03.04
On production sites
This release gives you more control over error pages and makes GraphQL mutations simpler.
Choose the status for an authorization policy
You can now set http_status on an authorization policy. Before, it was always 403. This lets you show your own 404 page when a policy is not met.
Your own error pages
You can customize the 403, 500 and 503 (maintenance) pages. Create a page with the matching slug: 403, 500 or 503.
Skip the form in GraphQL mutations
The form_name attribute is now optional in mutations such as user_create, user_update and customization_update. You no longer need to repeat the mutation input in a form. You can still use form_name if you want a callback, an async callback or emails from an existing form.
Also in this release
- Fixed a double error message that appeared in some cases when an image failed validation