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!
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...
Sometimes, a section or subsection of a website becomes obsolete, for example, if a product is no longer sold, or part of the documentation isn’t needed anymore. In this situation, you can still delete the pages one by one, starting at the lowest hierarchy level of the section concerned, but you...
We made the editing interface more attractive and user-friendly by brushing up its icon set. The icons are now easier to distinguish and more consistent in style. Some details have been removed from them so that the buttons work better for more editors, especially those with lower resolution...
Adding users to a working copy has become easier. The “Collaborators” selection box now also includes editors whose email address matches the search term. In the German-language Scrivito UI, you can now enter floating numbers in the standard German format, in which a comma instead of a period is...
Server-side access to restricted content via Node.js You can now also access restricted Scrivito content on a server, e.g. for archiving your website content. For this, the apiKey option was added to Scrivito.configure . See also Using Scrivito with Node.js. Scrivito = require("scrivito")...
The behavior of the “Publish” buttons in Scrivito’s editing interface has been improved and aligned: All of these buttons now directly open the confirmation dialog which now also includes a button for opening the “Changes” list and getting an overview of the content that was altered. Thank you...
The active Content Browser tab is preserved The Content Browser sometimes prevented editors from quickly inspecting the properties of multiple objects one after the other. When the user selects another object of the same type, the active tab now remains open. Thank you for using Scrivito! Please...