MySource Matrix Developer

Main Content

MySource Matrix Developer Newsletter Issue 61
Friday 10th February 2006

covers versions 3.6.5 stable, 3.8.0 RC1, 3.9.0 development

News

New Release Candidate Out

MySource Matrix 3.8.0 RC1 was released on Monday for internal client preview only. 3.8.0 RC1 contains almost 100 new features and focuses on improved scalability, performance, searching and listings. The current development version of MySource Matrix is now 3.9.0.

3.4 Branch Support Dropped

With the impending release of 3.8.0 stable, support for the 3.4 branch of MySource Matrix is being dropped by the development team. Stable bug fixes and testing will be performed on the 3.6 and 3.8 branches only. Critical bug fixes will only be made to the 3.4 branch for clients unable to upgrade to 3.6.

Configuring a 3 User Setup

From version 3.8.0 RC1, MySource Matrix has 3 database connection strings that can be configured. Installations that do not need to take advantage of PostgreSQL database replication can be installed as normal 2 user setups, configuring connections strings DB and DB2 with the same primary user.

For systems with 3 connection strings, the installation procedure needs to change a little. When creating the master PostgreSQL database, assign ownership to the secondary user (the user in the DB2 connection string). All database writes will go through this secondary user, so they need access to the database in order to configure the schema.

New Features

Next & Previous HREF Listing Keyword

Added to: 3.9.0 development

Listings have always had keywords to print a link to the next and previous page of the list, but this keyword always printed hyper-linked text. Customising the next and previous page links was not possible. For example, you couldn't use images for next and previous buttons. Two new keywords have now been added to all listings allowing you to print the URLs to navigate to the next and previous page of the list. The keywords are and .

Custom Form Submission ID Keyword

Added to: 3.9.0 development

A new keyword has been added to the Custom Form, allowing you to print the ID of the form submission on the Thank You screen. The new keyword to include on the thank you bodycopy is .

Trigger Action to Send Email

Added to: 3.9.0 development

A new trigger action has been developed to send an email when an event occurs. A list of recipients (either users or custom email addresses), a from address, a text only email and a HTML email can be specified. If the event is fired on a user asset, the keywords , , and can be used.

A nice use of this new trigger action is to send a user an email notification when their account changes status. The keywords allow you to personalise the email for them.

Planned Development

Re-request Validation Email

To be added to : 3.9.0 development
Estimated start date: already in development
Estimated end date: 13th February 2006

The Account Manager page currently has a feature to validate the email addresses of new users by sending them a validation link. The user must click a link in an email to activate their account. If that email goes missing, the validation process has to be performed manually. A new feature is being added to the Account Manager page that allows a user to re-request their validation email if they have lost it.

Upgrading

3.9.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.6.x 3.8.x Dev Description
1120 N Y N Paint layouts in safe edit broken
1123 N Y Y Configuring a default Thesaurus on the Global Preferences screen causes an error
1126 N Y Y Datetime attribute doesn't handle early dates well
1127 N Y Y Public deny access causes menu area to disappear for all users except sys admins
1128 N N N Deleted items still show sometimes (not confirmed)
1130 N N N Bad types sent with getAsset not allowing inheritance (not confirmed)
Notes:

Bug #632 (Firefox crashes when repeatedly linking) was submitted by mkeehan on the 17th of May 2005 but has now been marked as Will Not Fix after it was found that the crash is caused by a memory leak in the JVM. A bug has been submitted to Sun about this problem but has not been fixed. We are unable to fix this within MySource Matrix.

Bug #911 (Live/Public Read File assets cannot be purged on Oracle) was submitted by Avi on the 7th of September 2005 but was marked as Can Not Replicate after testing on the latest 3.6.0 branch code indicates that this problem does not occur and may have been fixed.

Bug #1099 (WYSIWYG editor have to be able to handle identificators) was submitted by coolvik on the 20th of January 2006 but was marked as not being a bug as this actually appears to be a missing feature and the WYSIWYG can handle manually entered IDs.

Bug #1122 (Changing 'Allow Unrestricted Access' breaks webpath) was submitted by davent but was marked as Can Not Replicate after 3 developers could not replicate the problem in either the 3.6 or 3.8 branches.

Feature request #1131 (New keyword for parent asset url/href for grouped asset listings) was submitted by Anthony Barnes but was marked as Not A Bug because the feature already exists in 3.8 and will not be back-ported to 3.6.

New Feature Requests Added To Bug Tracker

Bug ID Description
1121 Add keyword to listings by default
1124 Lookup Settings Screen: Paint Layout not using new Asset format
1125 Placeholders in asset map
1129 New keyword to expose created assetid of submission in custom form

Bugs Fixed In The Bug Tracker

Bug ID 3.6.x 3.8.x Dev Description
1088 Y N N Complex Validation Rules not saved
1119 N Y N Mulitple page safe edit not working
1120 N Y N Paint layouts in safe edit broken
1123 N Y Y Configuring a default Thesaurus on the Global Preferences screen causes an error
1126 N Y Y Datetime attribute doesn't handle early dates well
1127 N Y Y Public deny access causes menu area to disappear for all users except sys admins
Add a Comment

You must click here to log in before posting comments.

View Comments

There are currently no comments for this newsletter.