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 Accessing the current user’s picture The Scrivito.currentEditor API now seamlessly integrates with IAM, allowing developers to access the picture URL associated with the current editor’s IAM profile. Easier attribute type migration There are situations in which a developer needs to...
> After introducing details pages for data items in version 1.36.0 of the Scrivito SDK, the editing interface now offers you to create such a page for a given data class directly from within a data item. If, for example, you have a card widget in your data list widget, and this card widget has a...
Improvements Updating data items using custom logic By defining the update callback of Scrivito.provideDataItem , you can now smoothly update data items using your own logic. This gives you greater control and flexibility in managing your data within your Scrivito app. Prerendering fails early...
This release fixes a bug found in version 1.36.0 of the Scrivito JS SDK: Under certain conditions, the renderChild prop of Scrivito.ChildListTag received an argument that was not a child object. This could lead to unexpected app crashes. We apologize for any inconvenience this may have caused!
Scrivito’s user management has moved to the Console After introducing the JustRelate Console in April this year and announcing that authorized Scrivito users would be able to manage their account’s users and teams there, we finally did it: Clicking “Manage users” in the main menu now opens a new...
Bugfixes All API keys now work properly in Node.js environments In the Scrivito JS SDK, version 1.35.0, we added support for private API keys in a Node.js environment. Due to an encoding error when passing the credentials to the Scrivito backend, some keys didn’t grant access to restricted...
In an earlier Scrivito JS SDK release, we introduced data lists for seamlessly integrating not only individual data items but also collections of such items into your Scrivito app. Now, we are happy to present an even more powerful feature for data integration: Data details pages that can display...
Logged-in editors can now see their profile image If you have added a profile picture to the IdP (identity provider) account you use to log in, it is now displayed on the sidebar instead of your initials. For example, if you log in with your enterprise account, Scrivito uses the image from your...
This release introduces multi-line editing for string attributes, and improves several development-related aspects, also in the context of Node.js. Improvements Multi-line editing for string attributes As a developer, you can now enable multi-line editing for string attributes in the “Properties”...
Placeholders in lists In the previous Scrivito JS SDK release, we had introduced placeholders as a means to incorporate personalized data into textual content. Building upon that, we are excited to announce that in this release, we have expanded the functionality of placeholders so that they can...