Native lazy-loading is a modern web technology that has been implemented by all major browser vendors in the recent years. It defers loading images until they are scrolled into view and thus reduces the bandwidth needed for a page to be displayed in full.
The Scrivito.ImageTag component is now compatible with browser-level lazy loading by respecting the loading=“lazy” property.
Over the years, Scrivito’s in-place HTML editor has become a bit rusty and has accumulated several small issues so we modernized it!
Editors will notice the new link toolbar for opening the destination of an HTML link even while editing in-place. The second noticeable change is the paragraph format drop-down menu, which combines the mutually exclusive options for headings and pre-formatted text.
We preserved the overall look and feel of the tool so that the editing experience remains the same. Under the hood, however, the new editor rectifies the issues listed below. Note that the new in-place editing features are only available to users of edit.scrivito.com.
As an editor, you can now instantly see how many pages (or images, etc.) have been changed in a working copy simply by opening the “Working Copies” sidebar. Each element on this sidebar is now equipped with such a counter, enabling you to estimate the effort associated with the corresponding working copy.
For more convenience, pages can now also be duplicated from within the hierarchy browser. 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.
The properties of a page or widget can be grouped by means of a propertiesGroups definition in the call to Scrivito.provideEditingConfig. The tabs representing such properties groups in properties views can now be rendered faster by following the React recommendation to make such lists individually identifiable using a unique key. For details, see the documentation.
For improved ease of use, when collaborating using workflows, the editing interface now displays buttons only for those actions that are available to the editor or reviewer.
For enhancing HTML markup as it can be found in attributes of the html type (used by text widgets, for example), the Scrivito.resolveHtmlUrls API method has been provided. It returns the markup passed in from such attributes, but with all internal URLs (pointing to content managed by the same Scrivito CMS) transformed to fully qualified URLs, allowing you to customize, i.e. further process, the markup before rendering it. This way, text fragments can be replaced, special highlighting can be applied, etc., to optimize the usability of your content for editors or visitors.
On properties views of pages (and other types of content) as well as widgets, the attributes to be displayed or made available for editing can now be determined dynamically. If, for example, selecting a specific option using an enum attribute causes other attributes to become irrelevant, they can now be hidden. For this, the list of properties (and also properties groups) to include on properties views can now be provided by means of a callback in the editing configuration concerned.
Custom components can show up either on a sidebar panel or in properties dialogs. Both use individual themes, dark and light respectively. Using the new Scrivito.uiContext method, such components can adapt their styles to their respective environment.
In some cases, HTML attributes in properties dialogs unexpectedly appeared as read-only. Editing rich text in properties dialogs now always works as expected.
Scrivito.ContentTag now handles clicks on links properly even if dangerouslySetInnerHTML has been passed in.
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...