Scrivito JS 1.9.0 Released – Featuring Refined Content Validation

Improvements

Finer grained content control through validation levels

In version 1.7 of the Scrivito SDK, we introduced validations, a means for programmatically checking whether content meets specific requirements. The consequence of a single failing validation was that the working copy could not be published until the error was fixed. However, we and some of our customers noticed that some content-related peculiarities are just that, far from critical, so we complemented validation errors with two more severity levels, warnings and informational messages.

When defining a validation, a failing check can now be categorized as error, warning or info, with error being the default (the latter means that existing validations still work). To editors, severity levels are indicated by colors and labelled sections on the notifications sidebar. For further details, take a look at our Overview of Scrivito’s Content Validation.

We hope, you find this extension as useful as we do.

Validation messages for custom components

When providing editors with custom editing tools, for example in properties dialogs, Scrivito can still validate the respective content but cannot display the validation results because such components aren't under its control. This is where the new validationResultsFor function comes into play. It allows developers to render the messages returned by the validation function.

Improved up-to-dateness of prerendered content

Scrivito’s prerendering improves the loading speed of your web application – for a better visitor experience. For covering rapid changes to the published content, Scrivito.updateContent is now available. If called in the app’s startup phase, this function updates the content to prerender causing the first meaningful paint to be in sync with the published content again.

Determining the creation date of a CMS object

CMS objects now expose their creation date. To retrieve this date, the createdAt instance method is available, allowing you, for example, to output Dublin Core metadata for “Date Created”.

Bugfixes

  • In HTML markup, links pointing to PDF files are no longer replaced with garbage when editing the text again.

  • The edit mode switch is displayed correctly in all browsers

    With Chrome 76, the editing mode buttons at the center of the top bar are now properly aligned again.

More great blog posts from Andreas Viebke

  • Scrivito Enterprise CMS - Product Illustration

    Scrivito JS SDK 1.45.0 Released

    Interface Builder Supports Further Attribute Types for Filtering

    Interface Builder improvements Filtering data by enum, boolean, date, and number attributes The Interface Builder’s data editor now also lets you filter data by attributes of the enum , boolean , date , and number types. This makes it much more convenient and intuitive to select and present data...

  • Scrivito Enterprise CMS - Product Illustration

    Scrivito JS SDK 1.44.2 Released

    Bugfix Release An issue with Scrivito.useDataLocator has been fixed. It prevented filters with reference data attributes from being evaluated properly. We apologize for any inconvenience this issue may have caused! Thanks again for using Scrivito!

  • Scrivito Enterprise CMS - Product Illustration

    Scrivito JS SDK 1.44.1 Released

    Maintenance release This is a maintenance release with minor improvements. As always, we will keep you posted if there is anything interesting to report. Stay tuned! Thanks again for using Scrivito!

  • Scrivito Enterprise CMS - Product Illustration

    Scrivito JS SDK 1.44.0 Released

    Interface Builder improvements LinkTag supports data items The LinkTag component now supports data items as navigation targets. Passing a DataItem to the to prop causes the link to point to the details page of the item concerned. Accessing current data of a specific class The useDataScope and...

  • Scrivito Enterprise CMS - Product Illustration

    Scrivito JS SDK 1.43.0 Released

    Interface builder improvements Data attributes For the application to utilize the attributes selected by content editors, the Scrivito SDK now includes a (beta) API for representing data attributes, DataItemAttribute . A data item attribute can be accessed from a data item via...

  • Providing Data Classes with Custom Attributes

    Latest updates to edit.scrivito.com

    Defining custom attributes via the Interface Builder’s data editor The data editor now lets you add custom attributes to data classes. If, for example, you have a “Current user” data class that requires an attribute not specified in the editing configuration of this class, e.g., “email”, you can...

  • Scrivito Enterprise CMS - Product Illustration

    Scrivito JS SDK 1.42.1 Released

    Bugfixes Data integration issue > DataItem#get > no longer requires a loading context, i.e., > Scrivito.load > or > Scrivito.connect > . We apologize for any inconvenience the above issue may have caused! Thank you for using Scrivito!

  • Scrivito Enterprise CMS - Product Illustration

    Scrivito JS SDK 1.42.0 Released

    Interface Builder improvements DataScope#limit() API method The new DataScope#limit() method determines the maximum number of data items a DataScope may contain. It returns either a number indicating this limit, or undefined if no limit is set. Introducing Scrivito.currentLanguage()...

  • Introducing the ​New Data Editor

    Latest updates to edit.scrivito.com

    > > As you may have noticed, we have been continuously refining and expanding the Interface Builder. Now the time has come for a correspondingly enhanced data editor. > > The new data editor comes with an intuitive interface that provides a visual representation of a data locator as well as...

  • Scrivito Enterprise CMS - Product Illustration

    Scrivito JS SDK 1.41.0 Released

    Interface Builder improvements Accessing a data scope from the current data It is now possible to access a DataScope from the current data using the new Scrivito.useData hook (which supersedes the Scrivito.useDataItem hook). The new hook always returns a DataScope . In order to check whether this...