MySource Matrix Developer

MySource Matrix Developer Newsletter Issue 16
Thursday 24th March 2005

covers versions 3.4.0 stable, 3.5.0 development

News

More On Design Customisations

It was reported last week that design customisations now seem to purge correctly. Chris N has since confirmed this during the last week on 3.4.0.

Run Levels

A new run level system has been added to MySource Matrix that developers should be aware of. Run levels allow certain security sub-systems (permissions, locking, data integrity etc) to be enabled or disabled for periods of time during the execution of a script. They allow for actions to be performed that the currently logged in user would not normally have access to perform. While we have always been able to do this, the new system allows for greater control.

Where we used to use the $GLOBALS['SQ_INSTALL'] flag to set security on or off, we must now use a function to set the run level to either a predefined level (OPEN, FORCED, or SECURE) or our own custom level using one or more of the SQ_SECURITY_* constants (see init.inc for the list).

Essentially, we set the run level to tell MySource Matrix what security sub-systems we want enabled. Then we can check if a system is enabled by asking MySource Matrix. We can also revert to the previous run level.

Here is an example:

<?php
$GLOBALS[&#39;SQ_SYSTEM&#39;]-&gt;setRunLevel(SQ_RUN_LEVEL_FORCED);

// do some code as if the SQ_INSTALL flag was set
$GLOBALS[&#39;SQ_SYSTEM&#39;]-&gt;restoreRunLevel();

// check if the permissions security sub-system is running
if ($GLOBALS[&#39;SQ_SYSTEM&#39;]-&gt;runLevelEnables(SQ_SECURITY_PERMISSIONS)) {
    // do some permission code
}
 ?>

New Features

Asset Map Support For Java 1.5

Added to: 3.5.0 development

The Java asset map now supports version 1.5 of the Java Virtual Machine. Existing support for JVM 1.4.2 has been maintained. This change has only been made to the development version of MySource Matrix so far, but will be made to the stable branch and released with 3.4.1.

Trigger To Set Permission

Added to: 3.5.0 development

A new trigger action has been added that can grant or deny a permission for an asset when an event is fired. You could use this trigger action to develop a rule where all files created under a site have write access for an editors group regardless of the permissions of the parent asset or the site.

Log Manager

Added to: 3.5.0 development

A new log manager system asset has been created to help manage the rotation of system log files. Future plans for development will allow users to use the log manager to configure custom log rotation schedules as well as view existing system logs from the administration interface. More details of the new log management system will come shortly due to changes in search logging that are currently in development.

Planned Development

Search Logging

To be added to : 3.5.0 development
Estimated start date: already in development
Estimated end date : 31st Mar 2005

Oracle Support

To be added to : 3.5.0 development
Estimated start date: already in development
Estimated end date : 31st Mar 2005

Backend Translation

To be added to : 3.5.0 development
Estimated start date: already in development
Estimated end date : 31st Mar 2005

Upgrading

3.5.0 Development

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

Additional queries:
No additional queries are required for upgrades.

Additional comments:
No additional upgrade steps are required.

New Bugs Added To Bug Tracker

New Feature Requests Added To Bug Tracker

Bugs Fixed In The Bug Tracker