Sections in the article
Inriver is moving towards more incremental, smaller releases to better and faster accommodate our customers. With smaller, more frequent releases, Inriver will be able to increase the quality and transparency of the releases and identify and mitigate any erroneous behavior that may be caused by the release much faster.
NB! To receive notifications when new release notes are published, please ensure you follow this page by clicking the "follow" button above.
Please see below for the deployed bug fixes:
General
We have applied a solution to ensure that the "Select All" checkbox displays correctly when the language is switched to German. This fix addresses long labels by using ellipses and tooltips to maintain UI consistency and readability. The ellipsis effectively truncates the label text, while the tooltip provides the full label on hover, ensuring a smooth user experience in all supported languages.
We have applied a solution to ensure that when retrieving FieldSet data via the REST API endpoint "/api/v1.0.0/model/fieldset", it will now return the latest data after a new FieldType has been added to the FieldSet using the endpoint "/api/v1.0.0/model/fieldset/{fieldSetId}/{fieldTypeId}".
We have applied a solution to ensure that the CVL value selection dropdown in the Portal Query Editor remains open after each selection. Previously, the dropdown closed after every chosen value, requiring users to reopen it multiple times when selecting several CVL values. This improvement streamlines the workflow, reduces repetitive actions, and enhances overall efficiency during query configuration.
We have applied a solution to ensure that fields with no assigned value in the Portal Specification Template are no longer incorrectly flagged as invalid. Previously, empty fields were erroneously marked with messages such as “Invalid value: [null]” or “Unit: Invalid value: []”, causing unnecessary confusion for users when fields were intentionally left blank. This fix now correctly interprets unassigned values and prevents false validation errors.
We have applied a solution to ensure that environments with large FieldSet–FieldType combinations no longer trigger the “Maximum call stack size exceeded” error when opening the Excel Export option.
We have applied a solution to ensure that the Content Store no longer returns a 500 error when triggering a password reset. The system now reliably sends the password reset link via email as intended, restoring proper functionality to the password recovery process.
inriver Implementation Standards
Inriver's ambition is to collaborate with our partners in providing our customers with the safest and most secure PIM system possible. With that in mind, Inriver is improving the information on our Community to help implementation partners ensure quality, optimize implementations, and avoid pitfalls.
Read more about Inriver Implementation Standards
Comments
0 comments
Please sign in to leave a comment.