Product Updates

You can now change the sort order of the records by the field of your choice:

You can now see the top videos by streaming time in the "Project usages":

Another change in the tracking area is related to the IP address tracking.

You can now disable the IP tracking in the projects settings:

With today's update, we decided to split two permissions in order to give you a more fine grained permission system.

Environment permissions

The Create/edit models, plugins and customize content navigation bar environment permission has been splitted in two separate ones: Create/edit models and plugins and Customize content navigation bar.

That's the before and after:

Assets permissions

The Edit metadata/replace assets permission for assets has received the same treatment, and you can now control the two actions separately:

What happened to existing roles in my project?

This change did not alter what your users were already able to do, or not to do. For instance, if an existing role had the ability to "Create/edit models, plugins and customize content navigation bar", the same role is now be able to "Create/edit models and plugins" and "Customize content navigation bar".

It's no doubt that having a strongly linked content schema helps you find the information you need, when you need it. But what happens when we attempt to (un)publish or delete interconnected resources?

Most CMSs are terrible at handling this sort of thing. Contentful for example simply leaves a ghost references to a records that no longer exists, and calls it a day. Their philosophy seems to be "users will take care of filtering this garbage somehow on the frontend, not our problem!".

What distinguishes us the most from competition is a greater care in keeping the saved contents coherent and always consistent. It is our problem to ensure that, not yours. You've better things to do.

Today, we're happy to introduce additional settings that allow you to specify exactly what behavior to adopt when such events occur. And since different settings may make sense depending on the specific context, you can specify different behaviours for every Link, Links and Structured Text in your project.

If you have ever worked with databases, you will surely notice a similarity with the DELETE CASCADE settings that you can set on the foreign keys of a table:

With this change, editors won't have to guess the right pattern to solve intricate cases of dependencies between records, since the developers have already taken care of that for them. And scheduled publish/unpublish operations will be much more secure and deterministic than before.

The default settings you'll find in the existing fields are the ones that were in place until now, so don't worry, nothing will change unless you decide to do so.

If you want to massively change these settings, you can conveniently do so via the Content Management API and migrations.

In this example, we're changing settings for every Link, Links and Structured field in a project, so that when a publishing is requested and a field references some unpublished records, the resolution strategy is to also publish the referenced records:

module.exports = async (client) => {
  const itemTypes = await client.itemTypes.all();
  for (const itemType of itemTypes) {
    const fields = await client.fields.all(itemType.id);
    const interestingFields = fields.filter((f) =>
      ['link', 'links', 'structured_text'].includes(f.fieldType),
    );
    for (const field of interestingFields) {
      const validatorFor =
        field.fieldType === 'link'
          ? 'itemItemType'
          : field.fieldType === 'links'
          ? 'itemsItemType'
          : 'structuredTextLinks';
      if (
        field.validators[validatorFor]
          .onPublishWithUnpublishedReferencesStrategy !== 'publish_references'
      ) {
        await client.fields.update(field.id, {
          validators: {
            ...field.validators,
            [validatorFor]: {
              ...field.validators[validatorFor],
              onPublishWithUnpublishedReferencesStrategy:
                'publish_references',
            },
          },
        });
      }
    }
  }
};

From version 3.4.5 of our JS client we've improved the importer from Contentful!

We've added support for importing rich-text fields from Contentful to our new structured text field.

Before we couldn't import properly these fields, but now they map nicely to our new field, so the imports should be more straightforward.

For any issues or problem with imports, please reach out at support@datocms.com as we can help with any issues doing the import phase, thank you!

To work around an ambiguity with empty text fields, especially with structured text fields, we have added a new isBlank filter for single-line text, multi-line text and structured text fields.

You can have a look at the details in the documentation page, for example on the structured text.

We have added full support to WebP and HEIC formats in our media area.

Before these assets didn't have the same features as the other images, but now they do. So you can just drag-and-drop them as any other image, see previews and have the same support for responsive images on the GraphQL API.

If you have existing WebP and HEIC images you need to reupload them to have them treated as images rather than plain assets.

Now, together with scheduling a publication, you can schedule an unpublication.

Read all the details in our documentation page.

You can now trigger a new site search without launching an entire deploy. This is very useful for technologies permitting per-page deploys, like Next.js for example.

Read the Content Management API documentation page.

A set of usability improvements, both on the editorial side and on the development side:

• custom locales: you can now add whatever locale you want, just type it out and if it doesn't exist, it will be created for you! No more limits here

• if you have more than 5 items in a dropdown, we'll let you search in there:

• now also fields can be duplicated. This is particularly useful if you have complex fields with lots of validations (say modular blocks, links, etc) that you need to duplicate with some sligth variations

• last but not least, we've add a new parameter when getting a record: nested=true. If you add that, you'll get the modular blocks inlined in the record response and not as IDs that then will need another call to retrieve the content. Read in the documentation all the details and see an example.