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!
Celebrating Scrivito’s 50th update! 🔥 We’re thrilled to announce our 50th update to Scrivito Interface Builder! We couldn’t have achieved this without your continued support and feedback. From the introduction of ReactJS integration in version 1.0 seven years ago to the latest enhancements in our...
Added support for Ruby on Rails 7.2 The Scrivito for Rails SDK now supports Ruby on Rails 7.2. It requires Ruby 3.1 or later. Earlier Rails versions are no longer supported by Scrivito. For instructions and details on updating your application to Rails 7.2, see: Ruby on Rails Guides – Upgrading...
Bugfix Release Editing interface issue with ImageTag An issue where using ImageTag with the loading="lazy" attribute could prevent image selection has been resolved. Adding an image widget without a preselected image now displays the clickable placeholder again. We apologize for any inconvenience...
Interface Builder improvements Layout editing mode This new editing mode separates content editing from layout adjustments. In content editing mode, layout elements can only be viewed. To modify them, simply switch to layout editing mode. This clear distinction between content and layout...
Tailoring page visibility to teams and visitor groups With Scrivito Web Interface Builder, editors have visibility categories available to restrict who can access which pages. As an editor who has been granted permission to manage custom visibility categories, you can now create such categories...
This is a bugfix release. Fixed bugs Binary upload API is less strict again Regarding undefined option values, the Binary.upload API method now works as it did prior to version 1.48.0 of the JS SDK. Such undefined values no longer produce an error. We apologize for any inconvenience this may have...
Interface Builder improvements Retrieving data classes by their name A new API method, Scrivito.getDataClass , has been added as a native method for retrieving data classes by their name, obviating the need for custom lookup code. This method complements Scrivito.getClass for accessing object and...
Interface Builder improvements Filtering dates and numbers The filtering options of the data editor have been extended. You can now filter dates and numbers using the following operators: gt (greater than), lt (less than), gte (greater than or equal to), and lte (less than or equal to). These new...
Interface Builder improvements Using attributes of the current page context Attributes of the current page and its ancestors are now available to editors as placeholders and as a data source (datalocator). Note that only attributes of the string type that are also included as attributes in the...
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...