Like on the “Hierarchy” sidebar, the pages listed on the “Changes” panel now also feature a menu command for opening their respective properties, meaning that you no longer need to navigate to a page just to open its properties.
Furthermore, the items on the “Changes” sidebar now also include a lock icon if their visibility is restricted.
Especially editors who frequently review content that has been extensively changed will benefit from the new possibility to discard changes to page and widget properties individually. Now you no longer need to restore a page or widget as a whole and then reapply the improvements.
Those little “Discard” buttons show up where content was altered in properties views, and are available in all three view modes.
For more convenience, pages can now also be duplicated from within the hierarchy sidebar. This eliminates the need to open the page before it can be duplicated in a second step using the corresponding item from the main menu.
In addition to making properties or their groups available dynamically, they can now be made conditionally read-only. This way, as an example, currently irrelevant attribute values remain visible for editors, but are at the same time protected from being changed. See the documentation for details.
In the editing interface, the file sizes of binaries such as images are now consistently displayed in accordance with the corresponding SI standard (1 kB equals 1,000 bytes, etc.). Also, the aspect ratio of images is now displayed in a more common format, e.g. 3:2 (1.5).
For migrating content, generating sitemaps, and similar use cases, the attribute definitions of CMS object or widget classes can now be retrieved using the Obj#attributeDefinitions and Widget#attributeDefinitions instance methods.
For the purpose of customizing the editing tools available in details views, extensions can be provided. The React component for rendering an extension can now be specified directly instead of registering it and referencing it by its name. This way, props can be passed to the component, for example. See the documentation for details.
TypeScript now automatically infers the type of the return value of Obj#get as it is aware of the object class used. See Getting Started with TypeScript for details.
adoptUi.Scrivito.ContentTag, editing string attributes in place caused unexpected results or crashes. In-place string editing now works as expected again.Thank you for using Scrivito!
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...