Changes

Headless CMS

Introducing the Ability to Clone Existing Content Models (#2131 ) (#2132 )

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!

Cloning of Existing Content Models

(click to enlarge)

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.

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 id or 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.

Page Builder

Added Ability to Re-Render an Existing Published Page (#2092 )

mutation {
  pageBuilder {
    rerenderPage(id: "xyz") {
      data {
        id
        path
      }
    }
  }
}

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:

import { Context } from "~/types";

new ContextPlugin<Context>(context => {
  context.pageBuilder.onBeforeMenuUpdate.subscribe(async ({ menu, original }) => {
    // Do something here.
  });
});

Development

Fixed webiny watch Command's --remoteRuntimeLogs (-r) Argument (#2124 )

Fixed React Component Scaffold's webiny.config.ts File (#2123 )

webiny.config.ts

Two New webiny deploy Hooks (#2079 )

Documentation

Updated All Mentions of webiny.config.ts Files (#366 )