With this new feature, users now have the ability to clone existing content models into the same or even a different locale. Manual re-creation of the same content model in a different locale is now a thing of the past!
Programmatically Created Content Models - Fixed "List-Entries" GraphQL Query (#2133)
We’ve resolved an issue that would occur when a user created a content model programmatically (via the
CmsModelPlugin plugin), and then tried to issue its respective GraphQL query that lists all entries. This issue was occurring only on the DynamoDB + Elasticsearch setup of Webiny.
To learn more about creating content models via code, check out the Define Content Models via Code guide.
Fixed Marking a Nested Object's Field as Title Field (#2127)
While defining a content model via the Content Model Editor, if a nested object’s field ended up with the same
fieldId property as the content model’s
titleFieldId property, an unexpected error would be thrown. This particular edge case has now been addressed.
Fixed an Admin Area Bug Where Date Field Value Was Set as Null (#2126)
Prior to this release, saving a new content model entry that includes one or more date fields whose values haven’t been changed (default values were used) would result in an unexpected error. This has now been addressed.
Headless CMS GraphQL API - Resolved Search Issue (#2125)
In some cases, when using the Headless CMS GraphQL API to search for a content model entry via its
entryId field would result in an unexpected error. The issues has been resolved.
Headless CMS GraphQL API - Broken GraphQL Schema (#2120)
Prior to this release, defining an empty nested object field as the initial field of a content model would break the Headless CMS’ GraphQL schema, effectively making the GraphQL API unusable. A set of additional checks has been implemented, so this issue should now be resolved.
Added Ability to Re-Render an Existing Published Page (#2092)
From time to time, users may need to re-render a particular page they’ve previously created and published. This can now be done easily via the built-in API Playground, by executing a simple
rerenderPage GraphQL mutation. For example:
More information about this GraphQL mutation can also be found in the Docs tab, in the API Playground in your Admin Area application.
Replaced Lifecycle Hooks With Publish and Subscribe Methods (#2136)
In order to provide a more unified developer experience, within your GraphQL API, hooking onto Page Builder’s key lifecycle events is now done via a simple
ContextPlugin. No need to import the separate
PagePlugin plugin to achieve this anymore.
The following is a simple example that shows how you can hook onto the
onBeforeMenuUpdate lifecycle event:
For more details on all of the available events, please see the dedicated Lifecycle Events guide.
PagePlugin plugin that was previously used is no longer supported. If you’ve already used it your project, please replace all occurrences with the new
ContextPlugin approach, as demonstrated above.
-r) Argument (#2124)
In a couple of scenarios, upon running the
webiny watch command, adding the
-r) argument would not properly return runtime logs in user’s terminal. This has now been addressed.
Fixed React Component Scaffold's
webiny deployHooks (#2079)
You can now hook onto the pre-build and post-build events that are emitted during the
webiny deploy command. More information about all related hooks can be found in the new Build and Deploy Hooks guide.
Updated All Mentions of
All occurrences of
webiny.config.ts configuration files have been updated to reflect the changes done in the recent 5.18.0 release.