Editors can now specify the language in which the text on a web page is written.
Editors can now specify the language in which the text on a web page is written.
Whether a visitor uses your site search, or an editor uses the search sidebar, Scrivito now takes the language of the documents into account. As a result, language-specific common words (stop words) are ignored, preventing unrelated hits from showing up. Also, stemming is now applied based on the language of the pages, meaning that, for example, singular and plural forms are treated equally, increasing the quality of the search results.
The JavaScript API now also includes an according language()
method as well as the _language
attribute.
Are you managing multiple websites with Scrivito?
Your sites are now accessible via a dedicated sidebar and no longer via the hierarchy. This helps you keep track of your sites and always have the most recently used ones at your fingertips.
Adding a subpage using the main menu or the submenu in the hierarchy sidebar usually first opens the dialog for selecting the page type. Now, if, due to page type restrictions, only a singe type is available, the dialog is not opened anymore but, for your convenience, the menu item lets you add such a page directly.
In previous versions, the editing configuration of an object or a widget class allowed you to customize the title their instances should have in the Content Browser and in properties views. For this, the titleForContent
callback can be provided.
Sometimes, for example with homepages, a label meaningful to editors cannot be derived from the visible content alone. For handling such cases, Scrivito introduces a new attribute convention: contentTitle
.
As a default, i.e. if no callback has been provided, titleForContent
now first looks for a contentTitle
, and then, if it’s empty, for a title
string attribute. This makes it possible to provide a custom title for editors (contentTitle
) as well as the regular title to be displayed to visitors (title
).
To better support customizing Scrivito’s editing interface, the SDK now includes an API for retrieving the ID and the title of the current working copy, Scrivito.currentWorkspace()
.
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...