sections in the article
inriver is moving towards more incremental, smaller releases to be able to accommodate our customers in a better and faster way. With smaller, more frequent releases, inriver will be able to increase the quality and transparency of the releases and be able to identify and mitigate any erroneous behavior that may be caused by the release much faster. Please note that larger features and/or changes that deem to have a strong impact on customers and partners will of course be communicated in advance.
On May 27th - May 28th, the following patches were deployed to all stacks:
Improvements and/or enhancements for Enrich:
- Correction for when performing a mass update on a locale string to no value (i.e. empty) to ensure that the update only affects the specific locale string field
- Correction for Creating a query for products with related items having criteria on datefield fails
Improvements and/or enhancements for Control center:
- Correction for temporary slowness when clicking on the "Save" button in the "Fields" expanded view of the Model section
- Correction for Control center logs where the error message intermittently is missing making it hard for customers and partners to investigate some issues on their own.
- Proper CVL validation to only accept String/LocaleString according to this community page:
Identifier restrictions – inriver community - Since there has been push-back on this from several customers, the previous change enforcing restrictions on specific strings in HTML templates have been temporarily reverted during the investigation to determine at which level we can realistically restrict the use of certain keywords in the templates.
Improvements and/or enhancements for Extensions:
- Correction for connect messages where ChannelLinkDeleted event not triggered when the resource is deleted through Media Tab
Improvements and/or enhancements for Remoting:
-
- Correction for error handling when calling UpdateCalendarUrlForPlannerView(UtilityService) with calendarUrl equal to null
- Correction for error handling when calling GetAttributeSet if the attribute set doesn't exist
Comments
0 comments
Please sign in to leave a comment.