MySource Matrix Developer

MySource Matrix Developer Newsletter Issue 20
Friday 22nd April 2005

covers versions 3.4.1 stable, 3.5.0 development

News

New Developer Starting

A new PHP developer, Darren McKee, will be starting in the MySource Matrix team on Wednesday. Please make him feel welcome.

New Features

Dynamic Asset Builder Create Locations

Added to: 3.5.0 development

There is a new type of create location interface available for the Asset Builder. When creating an asset, a user can now select one or more create locations from a list dynamically generated from part of the asset tree.

For example, if you have an Images folder with a series of image category folders under it (eg. General, Holiday, Corporate etc), you could produce a drop down list in an asset builder that lists Folder assets under the Images folder and allows the user to select one or more of these in which to place the new asset. As you add new categories under the Images folder, the Asset Builder will allow them to be selected as create locations

The drop-down can also be displayed as a checkbox or radio button list and the list can optionally have structure shown through a stalk-like interface.

The new drop-down can be created in a set, like the existing optional create locations, so you can have multiple dynamic create locations. The keywords are the same as existing location sets:

Set Attribute Value Trigger Action

Added to: 3.5.0 development

A new trigger action has been created that allows you to set the value of an asset's attribute when an event is fired on the asset. This action has the ability to set serialised values, such as arrays, so it can be used to add default values to some assets when they are created.

Other New Trigger Actions

Added to: 3.5.0 development

Two other trigger actions have also been added, one to set a web path and one to create an asset. Both are unlikely to be used commonly and will mostly be used during imports or scripts. The create asset trigger action is especially useless as almost assets require some values to be entered before they can be created, so this trigger action will almost always fail (unless you have built an asset that requires no data for creation).

Planned Development

Backend Translation (stage 3)

To be added to : 3.5.0
Estimated start date: already in development
Estimated end date : 26th Apr 2005

Backend Translation (stage 4)

To be added to : 3.5.0
Estimated start date: already in development
Estimated end date : 29th Apr 2005

Sort Listings By Attribute Value

To be added to : 3.5.0
Estimated start date: already in development
Estimated end date : 26th Apr 2005

Upgrading

3.5.0 Development

Run step_02.php: no Run step_03.php: yes Run step_04.php: yes

Additional queries:

UPDATE sq_internal_msg SET type = 'inbox.message' WHERE type = 'hipo.some'; UPDATE sq_internal_msg SET type = 'inbox.sent' WHERE type = 'hipo.sent';

-- run the following queries as the postgres user of the database

BEGIN;
update pg_trigger SET tgenabled = 'f' WHERE tgname LIKE 'sq\\\\_%';

UPDATE sq_trig_hash SET treeid = REPLACE(treeid,'_','=');
UPDATE sq_ast_lnk_tree SET treeid = REPLACE(treeid,'_','=');
UPDATE sq_rb_ast_lnk_tree SET treeid = REPLACE(treeid,'_','=');

UPDATE pg_trigger SET tgenabled = 't' WHERE tgname LIKE 'sq\\\\_%';
COMMIT;

New Bugs Added To Bug Tracker

Notes:

Bug #583 (Custom Form / CMS Package - Tickbox error) was submitted by Richard Johnson but was found to not be a bug. The problem was caused from a bad upgrade where the database schema had not been correctly updated.

Bug #588 (Doco: Missing workflow keyword) was submitted by Chris N but was marked as not being a bug because it relates to missing documentation for the new features of 3.4.0, of which there are many. Plus, the bug tracker is not meant for documentation requests.

New Feature Requests Added To Bug Tracker

Bugs Fixed In The Bug Tracker

View Comments