Editors can now enable or disable content properties with a single click on a toggle switch.
In addition to the enum attribute type, which allows for any number of options (e.g. the color of a button), Scrivito now also has two-valued options built in. For adding a yes/no switch, developers have the new boolean attribute type available.
Examples for yes/no properties are activating and deactivating a specific style of a widget or page, or turning page indexing on and off.
As an editor uploads a file, for example a video, to the CMS using the Content Browser, an object class matching the content type of this file needs to be determined. Instead of always having a “Download” object created from such files, Scrivito now lets you register default object classes for the content types you work with. For this, the Scrivito.configureObjClassForContentType API has been made available. This method allows you to provide a mapping between content types and the respective object classes to be applied to uploaded files.
We further improved Scrivito’s multi-site capabilities. Visitors will no longer see blank pages after content migrated to a different site has been published but not yet fully prerendered.
Scrivito provides a new API method, Obj updateReferences. It allows you to change a CMS object’s links pointing to any other CMS object. The replacement link destinations can be freely defined using a mapping function. For example, you can change all links referencing an outdated imprint so that they point to the revised version.
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...
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!
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!
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...
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...
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...
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!
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()...
> > 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...
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...
