MySource Matrix Developer

MySource Matrix Developer Newsletter Issue 84
Friday 21st July 2006

covers versions 3.8.4 stable, 3.10.0 RC1, 3.11.0 development

News

Data Directory Restructure: An Update

In newsletter #82 there was a change to the data directory structure in the development (3.11.0) version to ensure that more than 32,000 of a specific asset type could be created on Ext2/Ext3 file systems. A reminder that since this changes the paths of any live and publicly readable assets (ie. those that have a __data URL on the front-end), any designs referencing those types of assets MUST be reparsed or the asset will not display.

If you are having problems with images not displaying in a design on 3.11.0, try re-parsing the design first before reporting a bug.

Also, in the previous newsletter, there were instructions on how to fix a system that had gained file versioning entries with double slashes. This fix is now integrated into the data directory upgrade script via a command-line option (this example should be run from your MySource Matrix system root):

$ php scripts/upgrade_data_dirs.php -s . --fix-lookups --show-details

As with the previous upgrade, if you are not having file versioning problems then it is not necessary to run this script.

Changes To Sending Files to the Front-End

There was a bug found in the sending of File assets, where the readfile() function in PHP - normally used to read the contents of the file - occasionally fails to read the entire file. Now, the sending of files to the front-end is handled by sending it in 8-kilobyte chunks, rather than all at once through readfile(). This is handled in a new function called _printFrontendFile(), which was originally created as PDF File assets were originally believed to be the sole source of the problem.

Note that this does not apply to file and publicly readable assets, whose sending is controlled by Apache and not MySource Matrix. The 8-kilobyte chunk size is also subject to change if performance issues are found.

New Features

WSDL Schema Assets

Added to: 3.11.0 development

A set of assets relating to the implementation of WSDL Schemas were initially committed to the development version this week. These new assets are part of the new Web Services package, that will enable MySource Matrix to interface with web services in a generic way.

The WSDL Schema asset allows you to import a WSDL (Web Services Description Language) file into MySource Matrix. A WSDL file is an XML file which describes what can be called from a web service, and how (by defining inputs and outputs).

Creating a WSDL Schema asset will in turn generate shadow assets for services, bindings, ports, and finally operations exposed by the web service.

These assets are still a work in progress, and further developments will be covered in future newsletters.

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: 

If you have not yet done so, re-parse any designs that reference a live and publicly readable asset (ie. one that uses a __data path on the front-end).

New Bugs Added To Bug Tracker

Notes:

Bug #1507 (Last tag cannot be removed) was submitted by Elden McDonald but was marked as Can Not Replicate after the original reporter and another developer were both later unable to reproduce the bug.

Bug #1511 (Assets with deny public read access appear in search results run by public user) was submitted by Anthony Barnes but was marked as not being a bug in current versions of MySource Matrix. The bug was reported as in version 3.8.1, however the bug had been fixed in versions 3.8.2 and higher.

Bug #1512 (Thesaurus Metadata Field Details Screen - missing fields) was submitted by Deborah Braithwaite but was marked as a duplicate of bug #1412 (Friendly title missing for thesaurus metadata fields) submitted by KateN on 6th June 2006. The duplicate bug was reported in version 3.8.2, but was already fixed in versions 3.8.4 and 3.10.0 RC1. The bug has been closed.

Bug #1518 (Using simple edit with no design applied initialises acquire locks hipo but doesn't process) was submitted by Elden McDonald but was marked as not being a bug because using the Simple Edit interface without a design applied is an unsupported configuration.

Bug #1520 (Custom Form Field validation with Regex does not work with the length constraint) was submitted by Scott Kim (on behalf of implementation) but was marked as not being a bug because the required metacharacters for marking the start and end of a string were not specified in the regular expression.

New Feature Requests Added To Bug Tracker

No new feature requests were added to the MySource Matrix bug tracker.

Bugs Fixed In The Bug Tracker

View Comments