Webiny 5.39.12 Changelog

For the full list of changes, check out the Webiny 5.39.12 release on GitHub.

Headless CMS

Various UI Improvements (#4255) (#4260)

A couple of improvements were made to the Headless CMS UI.

Updating Lists Automatically

For starters, in the content entry’s Revisions tab, once a revision is deleted, the list of revisions will be automatically refreshed. Previously, users had to manually refresh the page to see the updated list of revisions, leading to a less than ideal user experience.

Content Entry Revisions Section

(click to enlarge)

The same improvement was made in the list of content entries. Previously, when a revision was deleted, the list of content entries was not automatically refreshed. Now, it is.

Content Entries Section

(click to enlarge)

Proper Redirecting After Deleting a Revision

Next, when a user deletes a content entry revision, they will automatically be redirected to the previous revision. Previously, users were not redirected anywhere, and they had to manually navigate back to a different revision.

Also, if the deleted revision was the last one, now, the user will be redirected back to the list of content entries.

Added Success Message

Finally, once a user deletes a content entry revision, a success message (snackbar) will be displayed at the bottom of the screen. This message will inform the user that the revision was successfully deleted and that they are being redirected to the previous content entry revision (or back to list of all content entries if the deleted revision was the last one).

createFromGraphQL Mutation - Previously Published Revision Is Now Correctly Marked as Unpublished (#4258)

Upon programmatically creating a new content entry revision using the createFrom GraphQL mutation, users have the ability to also immediately mark the revision as published. For example:

And while this functionality did work, still, if a content entry already had an existing published revision, upon running the above mutation, the published revision’s status would remain unchanged, when in fact it should’ve been changed to unpublished.

With this release, we’ve addressed this issue. Now, when creating a new revision using the createFrom mutation, if the status field is set to published, the previously published revision will be automatically marked as unpublished.

Ensure Field Values Are Preserved When Deleting Latest Revision (#4253)

When deleting the latest revision of a content entry, the field values of the previous revision were not being preserved. This was a bug, and with this release, we’ve fixed it. Now, when deleting the latest revision of a content entry, the field values of the previous revision will be preserved.