MySource Matrix Developer

MySource Matrix Developer Newsletter Issue 93
Friday 22nd September 2006

covers versions 3.8.6 stable, 3.10.1 stable, 3.11.0 development

News

Upgrade Note for Versions 3.8.6 & 3.10.1

There was an upgrade script added to the design CSS File asset in the most recent releases of MySource Matrix (versions 3.8.6 and 3.10.1) - especially upgrades directly from the 3.6.x versions to 3.8.6. There have been reports of problems where "undefined index" errors - representing a missing attribute - are being reported in the CSS File Customisation asset.

This was due to an issue with the upgrade script which did not call the base upgrading functions - therefore, CSS File was never actually upgraded properly, causing problems down the track.

This should not have caused problems for users upgrading from a 3.8.x version or later, as the "missing" attribute has been defined in the parent Design Area asset since version 3.8.0. However, if any similar issues are found, then this news item also applies to you.

Those with access to branch versions should upgrade to the 3.8.x branch version instead. Otherwise, the issue will be addressed in the next releases of MySource Matrix (3.8.7 and 3.10.2), due to be released on 9th October.

'Unformatted Speed Check' Debug Feature

Placed in news because it's not really a feature any front-end user will use. The speed_check() function, used to debug the time taken to execute a certain piece of code, has traditionally been printed on the front-end using a red-on-yellow colour scheme.

This can now be modified in the development version to remove the formatting by adding a second parameter of FALSE to the function. Also, suppression from front-end printing is now possible using a third parameter of FALSE (which requires the second parameter to be FALSE also) - in this case, the speed check will be written to the error log instead.

New Features

Asset Sorting Tool

Added to: 3.11.0 development

A new System Tool has been added to the development version, allowing users to permanently re-order the immediate children of a specified parent asset by a standard asset field (such as Asset ID, Last Updated Time, or so on).

Selection Form Question: 'Leave Empty'

Added to: 3.11.0 development

Previously there was no way to specify a blank key value for a Selection Form Question option. There is now an "Allow Empty Option?" attribute that will return a key value of an empty string ('') when the Custom Form is submitted. The text of the empty option is customisable.

Delete All Option for Form Questions

Added to: 3.11.0 development

A new 'Select All' feature has been added to the Custom Form and Form Section to allow all questions in a form or form section to be deleted in one go.

Asset Listing: 'All Root Nodes' Option

Added to: 3.11.0 development

A new feature has been added to the Asset Listing Page, adding a setting affecting listings using multiple root nodes. A new option called "Root Node Logic" determines whether assets will be listed if they match at least one root node (the previous and default behaviour) or if they match ALL root nodes.

Design Customisations Have a Usage Screen

Added to: 3.11.0 development

The Usage screen of a Design or Paint Layout, which shows the top-level assets where they have been applied, has also been added to the Design Customisation asset. For further information on the Usage screen, please see newsletter 91 from two weeks ago.

Import Thesaurus Terms Trigger Action

Added to: 3.11.0 development, 3.10.2 stable

A new trigger action has been added to import an XML file of terms into a Thesaurus asset. The path to the XML file on the server's filesystem can be specified in the action's options.

Planned Development

No new generic features are currently scheduled for development.

Upgrading

3.11.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 #1701 ("use default" JavaScript not working properly on Metadata Screen) was reported by Christophe Olivar but was marked as not being a bug because the reason for the behaviour reported was that sections of a screen were being printed twice on a Simple Edit interface (by using an entire screen keyword, along with a keyword for a certain section), which is not supported.

Bug #1703 (Can't link files from one design to another) was reported by Jeff Van Campen but was marked as a duplicate of bug #1690 (can not link/move/clone div from one page to another page) reported by Christophe Olivar this week, which has been fixed. The duplicate bug has been closed.

New Feature Requests Added To Bug Tracker

Bugs Fixed In The Bug Tracker

View Comments