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!
Improvements Data is updated when the browser window is focused > As a default, the Web Interface Builder now always refetches the relevant data when the browser window is focused. If, for example, you leave the application and return later, the Interface Builder automatically requests the latest...
Bugfix Release String attribute values are now escaped correctly > There was an issue where string attribute values were rendered without proper escaping, causing the browser to interpret them as HTML markup instead of displaying them as plain text. This issue has now been fixed. We apologize for...
If, in your organization or company, content is created and maintained in teams, the Interface Builder’s workflows are an excellent tool for managing the editorial cycle – from authoring through copyediting and reviewing to publishing. With the latest update, editors who want to see their working...
Improvements Smarter page links Scrivito Web Interface Builder now generates cleaner and easier to grasp URLs for page links. The updated slug generation supports a wider range of international scripts and Unicode characters, adheres to modern latinization standards, including ISO 843, ISO/R 9...
Improvements Filled-in data placeholders in “Changes” mode Data placeholders are now replaced with the actual data in “Changes” mode as well, not just in “Preview” and “Edit” mode. Added support for the "ref" prop The WidgetTag, ContentTag, LinkTag, ChildListTag, and ImageTag components now...
Bugfix Releases An issue has been fixed that prevented link queries from being appended when used in a Scrivito.LinkTag component. Furthermore, an issue that prevented navigateTo from properly navigating when provided with an external Link has been fixed. We apologize for any inconvenience these...
Improvements WYSIWYG abbreviation support To meet the highest accessibility standards (WCAG AAA), abbreviations and acronyms need to be clearly recognizable for all readers. Editors can now mark up abbreviations directly in the content using the new “Abbreviation” button in the text toolbar. With...
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...