On the Ruby gem, we've added the method
#lqip_data_url, which lets you access the SVG blurred up version of your images, like so:
blog_post.cover_image.url(w: 800, h: 600, fm: :jpg)# => "https://www.datocms-assets.com/123/12345-heart.png?w=800&h=600&fm=jpg"blog_post.cover_image.lqip_data_url(w: 800, h: 600, fm: :jpg)# => "data:image/jpeg;base64,/9j/4AAQSkZJRgABAQAAAQABAAD/2wCEAAoHBwgHBgoICAgXFQoLDhUSDhUXDh0eDRUVGRYZGBYTFhUaIi0jGh0oHRUWJDUlKC0vMjIyGSI4PTcwPCsxMi8BCgsLDg0OHBAQHDsoIig7Lzs7Ozs7Ozs7LzsvLy8vLy8vLzsvLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vL//AABEIAA0AGAMBIgACEQEDEQH/xAAYAAEAAwEAAAAAAAAAAAAAAAAAAwQFAv/EABwQAAAHAQEAAAAAAAAAAAAAAAABAgMEBRESQf/EABUBAQEAAAAAAAAAAAAAAAAAAAMB/8QAHREAAQMFAQAAAAAAAAAAAAAAAQAREgITITFCA//aAAwDAQACEQMRAD8AqPMJiF1o6jvlILkhlWU11aMMTU6j50UPHKcCmTJa1aXEnvoBdy3GmTNPgAwfTkpbNJ2F/9k="
For more details on what you can do, please have a look at this blog post.
On the Plugin SDK, we've added a new method
plugin.disableField(...pathChunks, disable) that will let you disable a field so that the editors will be prevented to make changes.
Read all the details on the SDK reference.
We've recently launched a new feature that allows every user to customize the format in which the date and time are displayed.
Under User settings > Localization Settings you can find this screen:
In which you'll be able to pick your date and time format together with the options of showing times in the 24h format.
We hope to have covered all your date/time formatting needs with this.
The improvement is evident, especially when the images are shown particularly large within the web page:
You don't need to make any code changes to your Gatsby project to get the enhancement, just upgrade the
gatsby-source-datocms package using your packet manager of choice (npm or Yarn), making sure you are installing a version higher than or equal to 2.4.0:
npm update gatsby-source-datocmsyarn upgrade gatsby-source-datocms
We have just released a new update of our CMS area where we show usage stats.
Now we are providing a very granular set of statistics about assets, API calls and videos, to help you troubleshoot where you can optimize or better understand where the traffic is coming from.
With all this information we are sure you'll be able to better optimize your sites, in order to get better performance and saving some money! We hope to help you with this.
As a small note, we have also improved our interface to optimize the loading of big projects. This should speed up everyone, but should be felt more by big projects.
Finally, we have upgraded the dashboard to better show the projects on which you are only a collaborator and not the owner and also show who is the owner when you try to do actions restricted to them. Hopefully this will simplify management of the projects.
We have refreshed our documentation at large in the past weeks and also provided more examples for record creation, field creation and role creation. This is just a highlight but more has come already.
If you still think anything is lacking in our documentation, please let us know via Community, thanks!
Unfortunately we need to ask everyone who is using Ruby client with a version older than 0.7.3 to upgrade.
New builds might break as we had to change something in our schema to fix a bug that was allowing old versions of the Ruby client to work.
Version 0.7.3 was released on 2 Jul 2019 so most of you should probably be safe, but please double check.
Some updates about what we've released last month in preparation for our next big feature that is coming very soon: the staging environments!
Let's see the spring cleaning we've done:
The new feature we are going to launch is going to be called "environments", so to avoid confusion and also to give a clearer name to the former "deployment environments", we've renamed them to "build triggers".
In fact they are manual triggers that launch your build in external systems, we hope will make more sense for everyone!
This will unfortunately cause also a change in the CMA:
deployment_environment is now
deploy_event is now
When using the CMA, you can now reference models by using API keys instead of model ids. For now you can only do that when passing the API key in the URL or on filters. It's still a work in progress, soon you'll be allowed to use API keys in payloads as well.
As a nice side note, the usage of API key is also available when filtering webhooks.
We've released a new version of react-datocms (v1.2.2) that fixes a compatibility issue with IE11.
When duplicating an item in a tree structure, the new item will have the same parent of the duplicated one.
When changing link validations we are now providing an extra alert message, as this can potentially lead to data loss.
We'll release in a few days a change in our CDA that will affect some edge cases in filtering.
Please find all the details in our documentation: https://www.datocms.com/docs/content-delivery-api/changelog#20200511---changes-in-graphql-filtering
We've just released a round of updates on the plugin SDK and the plugins that we maintain.
We've added to the SDK the following methods/properties:
scrollToField(...pathChunks) - Plugins can use this method to navigate the record form.
saveCurrentItem() - Plugins can use this method to trigger a record save action without pushing the save button.
alert(message) - Use these methods to display UI consistent notifications and alerts.
itemStatus - Information about the publishing status of the record the plugin is attached to.
isSubmitting - Information about the record's form submitting status.
Read all the details on the SDK in the documentation.
Together with the SDK update we've released a new plugin:
Field anchor menu - A plugin that creates a sidebar menu that link to the fields in your record
and a few updates:
in the Conditional fields plugin - added a new option, invert, that inverts the logic of conditional fields - ie. show slave fields if master boolean is false.
in the Yandex translate plugin - we've fixed a bug that prevented the plugin to work with
all_locales_required = false
Upgraded all dependencies and SDK
Removed localtunnel as default option as it's not maintained anymore and you can do withouth
We are very proud to announce our latest integration, with Vercel!
You can now add Vercel as a deployment environment. You can trigger a build as usual from DatoCMS for static site generators but you can also use that to clear the cache of a Next.JS application.
Read all the details in our blog post about this.