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!
Weaving data into website content using placeholders Editors can now insert placeholders representing specific pieces of data into textual website content, e.g., for personalization purposes. When the website is then visited, these placeholders are dynamically replaced with data provided by the...
Editing widget properties on the sidebar For more convenience and uniqueness, the properties of any widget can now also be edited on the sidebar after clicking the “Widget properties” menu item of the widget concerned. The editing interface uses the sidebar that originally was dedicated to the...
Selecting the published content versions to compare The publishing history now lets you compare pages in any version of the published content with the corresponding page in any other version. Several of our customers had asked for this to be made possible. In more detail, determining the changes...
Improved “Sites” sidebar The “Sites” sidebar panel is now clearer, so you can more easily access the language versions of the currently selected website. The order of the language groups in the “All Sites” section is now fixed, which makes it easier to navigate the list and pick a site. The...
Switching to Neoletter made easy The Scrivito editing interface now features a sidebar button for conveniently opening the Neoletter UI associated with the Scrivito CMS concerned. Thank you for using Scrivito! Please let us know what you would like to see improved.
As a Scrivito customer, you will know of – or even have already used – the website-specific “Users” section on the Dashboard at my.scrivito.com that authorized users can access in order to invite people as editors, for example. We are discontinuing this user management section as we’ve replaced...
Selecting all changes in a working copy Selectively publishing changed content has become more efficient in situations where an editor needs to move all or almost all pieces of content to a different working copy. For example, if you need to publish just a couple of pages and move the majority of...
Selectable date display format Editors can now choose whether dates such as the publishing date of working copies in the “History” sidebar are displayed as absolute or relative values, e.g., as “Feb 23, 2023, 11:15 AM” or “Three days ago”, respectively. For this, a corresponding item was added to...
SDK uses edit.scrivito.com exclusively Scrivito’s always up-to-date editing interface, edit.scrivito.com, is now always used for editing. It lets editors benefit from improvements from the moment they are made available. If your app already uses edit.scrivito.com, you can skip this point, of...
After receiving feedback from power users, we’ve extended the date and time editing options. Manual date input Some editors need to provide many dates in their daily work. For these users, pointing and clicking again and again becomes tiresome after a while. With the new option to specify a date...