This scheduled release introduces SAML-based user group ‘SSO’ capabilities, removal of all customer-specific references and properties from templates, and fixes some early BTv4 release issues.
Release date: 1 May 2020
Inject ?=queries into URLs so Google Analytics can collate all searches across the Photo and Asset libraries. As well as capturing keywords entered into the search field, the URL should be able to track filtered selections, including:
Remove client-specific wording and styles that appear on templates and move them to content page properties or link them dynamically to existing properties. This allows the templates to be common across all instances.
Revise on the following templates:
Introduce a new search parameter “MediaId” that is only used for specific references like notification emails and not in the search itself. This allows us to send notifications to users when an asset they’ve previously downloaded has been updated or deleted. The ‘MediaId’ then allows us to link directly to that asset.
Hide the “Albums shared with me” table entirely, if there are no shared albums.
After each update, the ‘Contact Sheet’ template is deleted.
The “Filename” column on the “Reporting > Downloads report” page is missing a <div class="col-filename"> element. This will allow it to accept the existing width and word-break css. The <div> must sit inside the <td>.
Rename main UI .LESS/.CSS skin files across all sites to customer-friendly naming convention.
Ensure the following missing template files are included in each update:
The Asset library crashes whenever a non-image based file is added to the “Preview image” property on the AssetVersion media type.
Of course, adding a non-image file shouldn’t occur but client accidentally added the zip file to the preview image property and crashed the Asset library. Therefore, we should add validation to prevent non-images from being saved to the preview property.
The download history is either incorrectly only showing the first version in the list or not respecting unpublished assets.
The Asset library ‘Download’ reveal is sticky (e.g. it doesn’t automatically close) on the following items:
When sharing an asset, you can choose how long the asset share link will remain valid (7days/30days). If the assets haven’t been downloaded within 2 days of the share link expiring, the person will then be sent a reminder to download the asset. This reminder notification isn’t being sent!
Create a status warning message (displayed to the admin/editor) that informs the relevant members that an image or asset that they’ve previously downloaded, has been updated or removed.
The Asset Change Notification email is repeating individual asset changes previously emailed. We need to find a way to alert the system that the image/asset change has already occurred, so it doesn’t send the email again.
Hide the “See Details” link if user has no access (permissions) to the image/asset. This is determined by whether they are a part of a member group that is allowed to download Archived or Unpublished images/assets.
The Asset Change Notification trigger times need to be altered. E.g. The HangFire events, “HangFireEvents.ProcessMediaStatusChangeRecords” and “UtilitiesService.ArchiveAllExpiredMedia” are both set to trigger at 1am. Should “UtilitiesService.ArchiveAllExpiredMedia” trigger first, as the 1st could be half processed while the other is triggering?
The “None” item on notifications is still moving to the next line and is not aligned to the bullet point. This is because <p> tags are introduced.
Update all email template content against Brand Toolbox version 3, as there are some inconsistencies and incorrect [%PROPERTIES%] on the backoffice emails.
The following Data Types are being wiped out and replaced by client data every time we push a change:
Remove values from data types and make them backoffice editable properties.
When attempting to add a Category to an Asset or Image (node) in the Media section, the following error is returned:
Request error: The URL returned a 404 (not found): /umbraco/backoffice/UmbracoApi/Entity/GetById
I suspect that there is an old property tied to this somewhere and we need to consider this in any future migrations.
Note that we normally describe the action required for each of the Features, Tasks and Bugs in our releases. However, as Brand Toolbox v4 is still in early release (and hence in debug mode), the additional tasks below are simply itemised.