MySource Matrix Developer

Main Content

MySource Matrix Developer Newsletter Issue 117
Friday 9th March 2007

covers versions 3.10.7 stable, 3.12.2 stable, 3.13.0 development

News

MySource Matrix 3.12.2, 3.10.7 Released

Two new point releases of MySource Matrix were released last Monday. Both are bug-fix releases only, with version 3.12.2 fixing 26 bugs and 3.10.7 fixing fourteen.

There is an upgrade guide for these versions, which should be run if yoursystem uses rollback - there are new indexes to add to improve performance - or your system is affected by bug #2092 ("%metadata_field_XXX% keyword doesn't work when set to "Never" display").

The next releases, 3.10.8 and 3.12.3, will be released on Monday, 2nd April 2007. It is expected at this time that the next branch of MySource Matrix will commence with the release of version 3.14.0 RC1.

Change to get_word_counts() Function

Please note that the get_word_counts() function now considers more characters as a word break than previously - essentially, most non-alphanumeric characters on the keyboard are considered a word break. Note that characters in extended ASCII (0x80-0xFF) are never considered a word break, given their composition between valid letters and other symbols typically varies between character sets.

Change to Form Submissions

Please note that the behaviour of Form Submission assets have changed, so that public read access is explicitly denied. This change has been made to 3.10, 3.12 and development versions.

New Features

Replace File Trigger Action

Added to: 3.13.0 Development

This new trigger action allows the contents of a File asset to be replaced with another file stored on the server at a certain path. Note that if the asset broadcasting the event is not a File asset (or inherited from one), the trigger will always fail.

Planned Development

No new generic features are currently scheduled for development.

Upgrading

3.13.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

Bug ID 3.10.x 3.12.x Dev Description
2210 N N Y undefined index" error in listing engine sorting screen
2212 Y Y Y Errors from empty custom form datetime questions using 'allow blank'
2215 N N Y Fresh install on Oracle 10g - step_02.php breaks
2218 N Y Y Metadata field "use default" checkboxes still shown when field uneditable
2220 N Y N Removing metadata schemas fails
2221 N N Y Fresh install step_03.php generates undefined index errors
Notes:

New Feature Requests Added To Bug Tracker

Bug ID Description
2209 Breaks removed in form submissions
2211 Teleport from front-end to back-end using /_admin should avoid assets in Trash
2213 Search flood prevention
2214 Default Friendly Name For Bulk File Upload
2216 Admin Area History bar should only look forward and show prefs as well
2217 Keyword to print name of parent asset
2219 Change the way Matrix implements Flash
2222 Selectable link type for pages in a multiple page asset
2223 Trigger conditions/actions should show non-instantiable asset types

Bugs Fixed In The Bug Tracker

Bug ID 3.10.x 3.12.x Dev Description
2082 N N Y Editing or Reparsing a Parse file generate warning
2111 Y Y Y Hipo process going nuts for the Structured Asset Report
2179 Y Y Y Incomplete metadata report doesn't show all reported assets as children in asset map
2187 N Y Y Assigning an LDAP user to a role causes sq_vw_ast_role to fail
2194 Y Y Y search min word error
2204 Y Y Y Unable to link metadata fields between sections
2207 N N Y Replace Text tool not showing
2210 N N Y undefined index" error in listing engine sorting screen
2212 Y Y Y Errors from empty custom form datetime questions using 'allow blank'
2215 N N Y Fresh install on Oracle 10g - step_02.php breaks
2218 N Y Y Metadata field "use default" checkboxes still shown when field uneditable
2220 N Y N Removing metadata schemas fails
2221 N N Y Fresh install step_03.php generates undefined index errors
Add a Comment

You must click here to log in before posting comments.

View Comments

There are currently no comments for this newsletter.