Matrix Newsletter - September 2017
30 Sep 2017 By Bartek Banda
This month we just had a single release for the 5.4 branch which just included a few bug fixes.
- 184.108.40.206 (Patch Release) - 10 bug fixes
Check out the release notes for a full list of what bugs have been fixed.
No More 5.3 Releases
On the 28th of August we released version 220.127.116.11, which was the last release in the 5.3 branch.
This branch has now been switched into security and warranty mode, meaning clients who are on this branch will still be able to receive security patches and ad-hoc bug fixes until the warranty of the branch runs out in Nov 2018.
If you are currently on a 5.3 version and looking to upgrade, the best and most recommended path would be to move up to the latest 5.4 version.
A new tutorial was posted this month on how to use Server Side JS to create dynamic and SEO effective title tags for your pages.
Make sure you check it out, as well as the other SSJS tutorial published earlier this year on how to use it with Metadata and Paint Layouts.
Upcoming New Features & Enhancements
We're still hard at work on version 18.104.22.168, which is scheduled to be available sometime in October. Let's have a another sneak peak of what you can look forward to from this version.
Orphaned Assets Tool
A new tool will be added to the System Tools area of the Admin Mode interface that will let users see a list of all assets in the system that don't have a parent link (orphaned assets).
From here, you'll then be able to link selected assets to a new location for further management.
This is similar to the system_integrity_orphaned_assets.php script that you can run on the CLI as a server admin.
Metadata Field Morphing
We're adding Morphing functionality to Metadata Field assets.
This enhancement will let you convert your Metadata Field types to other types. For example, if you need to convert a Text field into a WYSIWYG or a Related Asset field.
LDAP User ID Configuration
A new enhancement is being added to the LDAP bridge where you can use the user's unique identifier as the shadow asset's ID instead of the LDAP entry's DN.
For example, a user's username would then go from something like this:
To something like this:
This means that your LDAP Users in Matrix won't get affected if you change the user groups or DN structure in your LDAP configuration or IDP.
This toggle will also be turned on by default for any new LDAP Bridge assets you create from this version on.