When working on a page, Scrivito lets you compare the current page contents with the version you started off with. Up to now, the changes view that lets you do this had three modes, “Additions,” “Deletions,” and “All changes” of which – according to the feedback we collected – only the latter was used.
So, for less complexity and hence better usability, we combined these modes into one, removed the dropdown, and called this page display mode – guess what: “Changes.”
When hovering over the sidebar, a short delay now prevents it from opening immediately. This way, the mouse pointer can be moved over the edge of the browser window without causing the sidebar to flicker.
It is now possible to drag widgets from one CMS object to another one using their respective handle. This comes in handy if pages are composed of more than a single CMS object.
In the Content Browser’s details view a spinner is now displayed while the details of a CMS object are being loaded.
Scrivito now lets you prevent editors from accessing the publishing history. By default, all users may use the publishing history, but by withdrawing the new read_history permission, exceptions to the default can be made. For details, see: Defining users and their permissions
We fixed a bug that caused URL changes (using BinaryRewrite) to be not applied to binary CMS objects (e.g. images or PDF files) with a permalink.
When using the SDK editing API and applying scrivito("content") to enum attributes, string values with special characters (e. g. ampersands) are now handled correctly. Thus, the default enum editor now always properly reflects the current value.
We fixed a bug related to the preset routes. The preset routes wrongly identified the first component of the URL path as an ID if it was exactly 16 characters long and was made up of letters and digits. Now, it identifies only hexadecimal numbers (consisting of digits and the letters “a” to “f”) as IDs.
If your routes.rb file contains calls to scrivito_route, you are not using the preset routes and are therefore not affected by this bug.
Scrivito now automatically optimizes JPEG and PNG images by removing their metadata and adjusting their size using the default image transformation configuration setting. As a consequence, the Scrivito::BasicObj#apply_image_transformation? hook method no longer needs to be defined for each object class that represents images. In fact, this method has been deprecated because it's not called anymore.
When changes to content cannot be saved (due to network dropouts, for example), Scrivito now displays an alert box instead of showing the “Changes saved” indicator.
We fixed a bug related to restored browser sessions that caused the displayed content to be outdated.
A bug was fixed that caused a filter and the “Last added” view to be selected at the same time. It occurred only after creating a CMS object using the “Create item” button displayed along with the filtered items, not when creating items using drag and drop.
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...