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.
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.
The useDataScope
and useDataItem
hooks can now be called with a data class name.
When useDataItem
is called with a data class name, then the current data is searched for the first DataItem
with the given class. If no such DataItem
can be found in the current data, a matching global DataItem
(via provideDataItem
) is returned if it exists.
When useDataScope
is called with a data class name, then the current data is searched for the first multi-item DataScope
with the given class.
With the latest Scrivito SDK, the behavior of the useDataItem
React hook changed. Previously, if the closest current data was a single-item DataScope, the hook still returned undefined
. Now, if the current data contains a single-item DataScope
, the hook returns a DataItem
that corresponds to the found scope.
An issue has been fixed that wrongly triggered the initializeCopy
callback when a widget was moved to another container.
Thanks again for using Scrivito!
Improvements Color picker for string values representing a color > As a developer, you can now offer a color picker for string values representing a color to editors. Picking a color graphically directly via the Web Builder’s user interface is a lot more convenient than having to switch tools for...
Bugfix Release Fixed TypeScript errors > This release fixes TypeScript errors related to the InPlaceEditAsPageContent component, ensuring proper typing and a better development experience. We apologize for any inconvenience this issue may have caused! Thank you again for using Scrivito!
Improvements Data is updated when the browser window is focused > As a default, the Web Interface Builder now always refetches the relevant data when the browser window is focused. If, for example, you leave the application and return later, the Interface Builder automatically requests the latest...
Bugfix Release String attribute values are now escaped correctly > There was an issue where string attribute values were rendered without proper escaping, causing the browser to interpret them as HTML markup instead of displaying them as plain text. This issue has now been fixed. We apologize for...
If, in your organization or company, content is created and maintained in teams, the Interface Builder’s workflows are an excellent tool for managing the editorial cycle – from authoring through copyediting and reviewing to publishing. With the latest update, editors who want to see their working...
Improvements Smarter page links Scrivito Web Interface Builder now generates cleaner and easier to grasp URLs for page links. The updated slug generation supports a wider range of international scripts and Unicode characters, adheres to modern latinization standards, including ISO 843, ISO/R 9...
Improvements Filled-in data placeholders in “Changes” mode Data placeholders are now replaced with the actual data in “Changes” mode as well, not just in “Preview” and “Edit” mode. Added support for the "ref" prop The WidgetTag, ContentTag, LinkTag, ChildListTag, and ImageTag components now...
Bugfix Releases An issue has been fixed that prevented link queries from being appended when used in a Scrivito.LinkTag component. Furthermore, an issue that prevented navigateTo from properly navigating when provided with an external Link has been fixed. We apologize for any inconvenience these...
Improvements WYSIWYG abbreviation support To meet the highest accessibility standards (WCAG AAA), abbreviations and acronyms need to be clearly recognizable for all readers. Editors can now mark up abbreviations directly in the content using the new “Abbreviation” button in the text toolbar. With...
Celebrating Scrivito’s 50th update! 🔥 We’re thrilled to announce our 50th update to Scrivito Interface Builder! We couldn’t have achieved this without your continued support and feedback. From the introduction of ReactJS integration in version 1.0 seven years ago to the latest enhancements in our...