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()
.
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...
Bugfix Release An issue with Scrivito.useDataLocator has been fixed. It prevented filters with reference data attributes from being evaluated properly. We apologize for any inconvenience this issue may have caused! Thanks again for using Scrivito!
Maintenance release This is a maintenance release with minor improvements. As always, we will keep you posted if there is anything interesting to report. Stay tuned! Thanks again for using Scrivito!
Interface Builder improvements LinkTag supports data items The LinkTag component now supports data items as navigation targets. Passing a DataItem to the to prop causes the link to point to the details page of the item concerned. Accessing current data of a specific class The useDataScope and...
Interface builder improvements Data attributes For the application to utilize the attributes selected by content editors, the Scrivito SDK now includes a (beta) API for representing data attributes, DataItemAttribute . A data item attribute can be accessed from a data item via...
Defining custom attributes via the Interface Builder’s data editor The data editor now lets you add custom attributes to data classes. If, for example, you have a “Current user” data class that requires an attribute not specified in the editing configuration of this class, e.g., “email”, you can...
Bugfixes Data integration issue > DataItem#get > no longer requires a loading context, i.e., > Scrivito.load > or > Scrivito.connect > . We apologize for any inconvenience the above issue may have caused! Thank you for using Scrivito!
Interface Builder improvements DataScope#limit() API method The new DataScope#limit() method determines the maximum number of data items a DataScope may contain. It returns either a number indicating this limit, or undefined if no limit is set. Introducing Scrivito.currentLanguage()...
> > As you may have noticed, we have been continuously refining and expanding the Interface Builder. Now the time has come for a correspondingly enhanced data editor. > > The new data editor comes with an intuitive interface that provides a visual representation of a data locator as well as...
Interface Builder improvements Accessing a data scope from the current data It is now possible to access a DataScope from the current data using the new Scrivito.useData hook (which supersedes the Scrivito.useDataItem hook). The new hook always returns a DataScope . In order to check whether this...