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.
As part of ongoing improvements to the new media experience, we've fixed the following issues. These fixes apply only to the new media experience and affect only customers who have opted in. The classic Media UI is unaffected.
Media (new media experience)
Bug fixes
This release fixes four issues in the new media experience, bringing it in line with classic Media behavior.
| # | Area | Fix |
| 1 | Field Revision History | Replacing a file in the new media experience now records the change in Field Revision History. The previous and new values for revisioned fields, like field name or file id, now appear in the Details tab. |
| 2 | Configuration | Expression fields on Resource entities are now evaluated when a Resource is created or updated in the new media experience. Previously they stayed empty after upload or were not recalculated after a change. |
| 3 | Configuration | Resource field types marked as hidden are no longer shown in the asset details view of the new media experience, matching the behavior of the classic Media UI. |
| 4 | Upload Media | Configured default values are now applied to Resource fields when a file is uploaded in the new media experience, matching the classic upload behavior. Previously these fields were left empty. |
Comments
0 comments
Please sign in to leave a comment.