Valo Universal Banner Images not appearing when using CustomImageWidth
Last Updated on 2021-12-21 16:06:03 UTCSummary¶
We are currently aware of an issue that is affecting the Valo Universal Webpart Banner template. Images may not be appearing when used in conjunction with the CustomImageWidth property. The Product Team is actively working on resolution.
The issue is caused by the piece of invalid regex that is supposed to update the size of the image inside the hbs helper. The place where the image width should be replaced is wrongly found and instead of the size the other parameter is changed - in that case it is a part of the access token which contains a timestamp. The problem started to happen as the timestamp now is in the form: '16400XXXXX' and the default width that we replace is '400'.
As a workaround if you set the CustomImageWidth to 400 (not optimal we know) this should make the images appear.
A fastlane fix is being coded and is currently being tested and will be released ASAP
Update: Fastlane release has been deployed for versions 3.1/3.0/2.3
The occurrence of the issue is related on the timestamp having that number 400 in it. It will change to 401 at 17:20 Finnish time and after that the code that causes the issue will replace the width value instead of part of an authentication token of the image URL. The next time this long breakage related to this bug occurs in the year 2025 as then the timestamp will start from 17400XXXXXX.
Latest updates¶
Date (UTC) | Status |
---|---|
2021-10-19 at 20:00 | We are currently aware of an issue that has a direct impact on new installations and update procedures for the Valo Intranet and are working on a fix |
2021-10-19 at 20:58 | A fastlane fix has been developed and is currently being tested and will be released ASAP |
2021-10-20 at 08:40 | A fastlane fix has been released |
Products affected¶
Product name | Version | Comments |
---|---|---|
Valo Intranet | 30 / 3.1 / 2.3 / 2.2 | Images may not be appearing when used in conjunction with the CustomImageWidth property. The Product Team is actively working on resolution. |
Expected availability of fix¶
The fastlane fix has been released for versions 3.0/3.1/2.3