MySource Matrix Developer

MySource Matrix Developer Newsletter Issue 134
Friday 6th July 2007

covers versions 3.12.6 stable, 3.14.2 stable, 3.15.0 development

News

Two New MySource Matrix Releases

Last Monday saw the release of two new point releases of MySource Matrix (3.12.6 and 3.14.2). Both are predominantly bug-fix versions, with a couple of small changes and new features. For a full list of changes for each new release, view the Changelogs online at the MySource Matrix web site.

New Features

LDAP Authentication: Log In as Local User

Added to: 3.15.0 development

This new setting, added to the LDAP Authentication System asset (found in the System Administration > Authentication Systems folder of systems with the LDAP package installed), provides the ability to be authenticated by the LDAP bridge(s) provided, but log in as a local (to Matrix) user.

If this setting is enabled, once the LDAP system has successfully authenticated a user name and password, the authentication system will then look for a standard user in the Matrix system with the same user name, then log in with that if found. If such an asset cannot be found, the login will fail.

Since this setting is made available at the authentication system level, exceptions cannot be made for individual LDAP bridges, in the case of multiple LDAP login sources. The default setting is to log in using the LDAP user, which maintains the status quo.

Shadow Asset Support Improvements

Added to: 3.15.0 development

A few minor changes and fixes were made to improve the support of shadow assets and bridges throughout parts of Matrix. In point form: they include:

• MySource Matrix now supports bridges providing the getAllChildLinks() function on behalf of their shadowed children.
• The %asset_contents% and %asset_contents_raw% keywords now work correctly for shadow assets listed by a Listing Engine-type asset: ie. the former will paint the shadow asset with the current paint layout.
• Shadow assets should now work as create locations in the Asset Builder asset.

Planned Development

Multiple-Date Calendar Event Asset Type

To be added to : 3.15.0 development
Estimated start date: 6th July 2007
Estimated end date: 16th July 2007

This development will allow for the provision of a "multiple-date" Calendar Event asset type, which will be comprised of one or more single/recurring calendar events, that will display a common name and description.

Set Future Lineage Trigger: Dynamic Date/Time

To be added to : 3.15.0 development
Estimated start date: 11th July 2007
Estimated end date: 16th July 2007

The "Set Future Lineage" trigger component will allow specification of a date/time sourced from an asset type.

For example, a trigger configured to fire upon creation of Calendar Event assets could be scheduled to move to a new location (lineage) at a time specified by an attribute in the asset (eg; event start date/time).

Upgrading

3.15.0 Development

Additional queries: No additional queries are required for upgrades.

Additional comments: No additional upgrade steps are required.

New Bugs Added To Bug Tracker

Notes:

Bug #2505 ("Delete a workflow which is being applied on an asset cause error", reported by Huan Nguyen on 4th July) was marked as Will Not Fix. Resolving this issue would require a significant architectural overhaul of Matrix's workflow system, which would significantly affect its stability.

Bug #2508 ("Image keywords not working", reported by KateN on 5th July) was marked as Can Not Replicate. The bug was reported in version 3.10.3, which is no longer supported for bugs, and the bug could not be replicated in a 3.12 branch system, the oldest major version currently supported.

New Feature Requests Added To Bug Tracker

Bugs Fixed In The Bug Tracker

View Comments