MySource Matrix Developer

MySource Matrix Developer Newsletter Issue 103
Friday 1st December 2006

covers versions 3.8.8 stable, 3.10.3 stable, 3.11.0 development

News

New Releases Next Monday

Next Monday, 4th December will see the stable releases of versions 3.10.4 and 3.8.9. These will be bug fix releases only. Clients running previous versions of these branches are strongly encouraged to upgrade to these versions when released.

Cron Script Changes

The script that runs MySource Matrix's Cron jobs (core/cron/run.php) in versions 3.10 and 3.11 has been changed to better support symlinked Solaris systems. Now it will not automatically attempt to determine the Matrix system root, and the script now accepts a parameter allowing administrators to explicitly specify the system root - such as the following:

0,15,30,45 * * * * /path/to/matrix/core/cron/run.php /path/to/matrix

(Note that on Solaris and some other systems, the "*/15" format for minutes will not work, as this is an extension to GNU crontab on Linux-based systems. The minutes have to be explicitly specified, like in the above example.)

If you are having problems with the Cron script, upgrade to a current branch version and explicitly specify your system root.

Oracle Search Indexing Erratum

In issue #97, there was a query in the upgrading instructions section for creating a job to automatically re-sync the index. This query was slightly incorrect. The DECLARE line should be above the BEGIN line, rather than below. The amended query (to reindex every half an hour) reads as follows:

    DECLARE JobID NUMBER;
    BEGIN
        SYS.DBMS_JOB.SUBMIT
            (
                job         => JobID,
                what        => 'CTX_DDL.SYNC_INDEX(''sq_sch_idx_value'');',
                next_date   => SYSDATE+5/86400,
                interval    => 'SYSDATE+30/1440',
                no_parse    => TRUE
            );
        COMMIT;
    END;

New Features

Backend-Configurable PHP Memory Limits

Added to: 3.11.0 development

Previously, to modify the maximum amount of memory PHP used to run MySource Matrix, or its Cron run script, you needed to modify certain files (core/web/index.php or core/cron/run.php, respectively).

These options are now configurable in the System Configuration screen inside Matrix, or in the main.inc configuration file. The constant SQ_CONF_WEB_MEMORY_LIMIT ("Web Memory Limit" in the backend interface) specifies the memory allowed for the Matrix front-end and back-end, while SQ_CONF_CRON_MEMORY_LIMIT ("Cron Memory Limit") specifies the amount of memory allowed for the Cron run script.

Note that if you use Squiz Server, these updates cannot change the amount of memory allocated to it for running HIPO jobs. This must still be done in the same way as before.

Content Encoding Sent to HTML Tidy

Added to: 3.11.0 development

The HTML Tidy plugin for the WYSIWYG Content Type now automatically sends MySource Matrix's default character encoding to the HTML Tidy program as a parameter, instead of letting Tidy default to ISO-8859-1 encoding.

Also, the External Tools Configuration screen now shows a warning if the default character encoding is not supported by Tidy.

Planned Development

No new generic features are currently scheduled for development.

Upgrading

3.11.0 Development

Additional queries:

Additional comments: 

- If you are having problems with the Cron run script, add the path of your Matrix installation as the first argument passed to the script.

- Run the following command line from your Matrix system root:
$ php scripts/system_integrity_clean_old_files.php .
This will display any files that have been orphaned from File assets as a result of bug #1875 (Files not being deleted when new file is uploaded over it). Note that you will need root user access to the Matrix system.

- If there are orphaned files on the system, you should delete them from the filesystem by using the following command line (run from your Matrix system root):

$ php scripts/system_integrity_clean_old_files.php . --delete-orphans

- The memory limit of your Matrix system and Cron run script is now contained in the main.inc configuration file, or the System Configuration screen in the Matrix admin interface. If you modified the memory limits of either (in core/web/index.php or core/cron/run.php respectively) from the default 16MB, please make changes in the appropriate places.

3.10.4 Stable

Additional queries: No additional queries are required for upgrades.

Additional comments: 

- If you are having problems with the Cron run script, add the path of your Matrix installation as the first argument passed to the script.

- Run the following command line from your Matrix system root:
$ php scripts/system_integrity_clean_old_files.php .
This will display any files that have been orphaned from File assets as a result of bug #1875 (Files not being deleted when new file is uploaded over it). Note that you will need root user access to the Matrix system.

- If there are orphaned files on the system, you should delete them from the filesystem by using the following command line (run from your Matrix system root):
$ php scripts/system_integrity_clean_old_files.php . --delete-orphans

3.8.9 Stable

Additional queries: No additional queries are required for upgrades.

Additional comments: 

- Run the following command line from your Matrix system root:
$ php scripts/system_integrity_clean_old_files.php .
This will display any files that have been orphaned from File assets as a result of bug #1875 (Files not being deleted when new file is uploaded over it). Note that you will need root user access to the Matrix system.

- If there are orphaned files on the system, you should delete them from the filesystem by using the following command line (run from your Matrix system root):
$ php scripts/system_integrity_clean_old_files.php . --delete-orphans

New Bugs Added To Bug Tracker

Notes:

Bug #1837 (Search custom form logs by ID) was submitted by Deborah Sherwood but was marked as not being a bug. This functionality is already available through the Quick Search feature in the backend interfaces.

Bug #1840 (Automatically assign a thumbnail to an asset type) was submitted by Deborah Sherwood but was marked as not being a bug. This functionality is able to be replicated using the trigger system.

Bug #1904 (Fields to retain data if submitted with an error) was submitted by DCITA but was marked as Can Not Replicate after a developer could not replicate the issue in the reported version, and the reporter was able to generate a form without this issue in their system.

New Feature Requests Added To Bug Tracker

Bugs Fixed In The Bug Tracker

View Comments