For security reasons, we have decided to remove any previously saved Netlify/Vercel token information from all existing build triggers. This change no longer allows you to view build logs directly from within the DatoCMS interface.
The reason for this change is that a project's read-only token API has read access to build triggers, but these were exposing third-party tokens that potentially allowed destructive operations to be performed. If you have publicly shared any DatoCMS key and you have build triggers pointing to Netlify/Vercel, we recommend rotating the keys of these these services.
Another day, another improvement to DatoCMS!
Building up from our recent addition of MD5 metadata to assets, we can now warn the user when there's an asset in the Media Area with the same signature as the file they're trying to upload:
Today we're really happy to announce a small, nifty addition that we're sure a lot of people will find useful! We called it Quick Search, and it allows to find all records matching a specific criteria around your whole project.
You can launch Quick Search using the little "magnifying glass" icon that's always present at the top-right or, even faster, using the ⌘+P (or Ctrl+P) keyboard shortcut:
Small, great addition today. You can now see which records point to the current record via Link fields! Some plugins were already available to perform the same job, but the need is so common that we decided to add it everywhere 😉
This is a nice addition to the Media Area: you can now see the MD5 hash of any asset you upload to DatoCMS. You can also search for MD5 in your Media Area, to see if the same asset is already present!
This is especially useful in automated scripts: the same information/query is also available both on our Content Management API and Content Delivery API:
This was long overdue, but we finally found some time to update our Yeoman Plugin generator to make use of the latest React version, and improved the default React skeleton with hooks!
npm update -g generator-datocms-plugin
We made some improvements to webhooks! You can now "pause" webhooks by temporarly disabling them, and use Mustache templates not only to compose a custom HTTP payload, but also to personalize the URL:
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.
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:
The Edit metadata/replace assets permission for assets has received the same treatment, and you can now control the two actions separately:
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".