MySource Matrix Developer

MySource Matrix Developer Newsletter Issue 77
Friday 2nd June 2006

covers versions 3.6.8 stable, 3.8.2 stable, 3.9.0 development

News

New MySource Matrix Releases on Monday

Two new stable versions of MySource Matrix, versions 3.6.9 and 3.8.3, will be released on Monday, June 5th. Version 3.8.3 is predominantly a bug-fix release, but also contains performance improvements as well as a minor functionality enhancement in the Remote Content asset. Version 3.6.9 is a bug-fix release only and contains no new functionality.

Keyword Option Reverted

The previous newsletter reported a new feature in the 3.8 stable and development versions, that allowed users to determine on a global level whether or not keywords were to be replaced with an empty string.

This feature has been reverted and a permanent solution has been committed, so that keywords will now behave in the upcoming 3.8.3 release as they do in the version 3.6 releases.

The naming convention for "global keywords" mentioned in the previous issue remains. Keywords starting with "%globals_" are assumed to be global keywords and will be replaced at the global level.

New Features

Group Name Linked Keyword

Added to: 3.9.0 development

A new keyword has been added to the Listing Engine asset for groups based on parent asset only. The keyword is replaced with the name of the asset (as per ), with a link to the parent asset.

Image Variety Constrain By Width & Height

Added to: 3.8.3 stable, 3.9.0 development

A new option has been added to the 3.8 branch and development versions to the Image Variety asset. Previously, image varieties could be constrained by either width or height, but not both. This new option allows a user to set a maximum width AND height that an Image Variety can be, and resizes the image if either constraint is exceeded.

Planned Development

No new generic features are currently scheduled for development.

Upgrading

3.6.8 Stable

Additional queries:

No additional queries are required for upgrades.

Additional comments: 

Systems using rollback ONLY:
To implement bug fixes related to rollback, the rollback triggers must be dropped and then re-created. The recommended procedure is the following:
1. Open a command line and change to the Matrix system root directory.
2. Run the following command line to temporarily disable rollback:
$ php scripts/rollback_management.php -s . --disable-rollback
3. Edit the [SYSTEM ROOT]/data/private/conf/main.inc file and change the line:
define('SQ_CONF_ROLLBACK_ENABLED', '1');
to:
define('SQ_CONF_ROLLBACK_ENABLED', '0');
4. Run the following command line to drop the triggers:
$ php install/step_02.php
5. Edit the [SYSTEM ROOT]/data/private/conf/main.inc file again and change the line:
define('SQ_CONF_ROLLBACK_ENABLED', '0');
to:
define('SQ_CONF_ROLLBACK_ENABLED', '1');
6. Run the following two commands on the command line to recreate the triggers and re-enable rollback:
$ php install/step_02.php .
$ php scripts/rollback_management.php -s . --enable-rollback

Systems not using rollback to not need to perform any additional steps to upgrade their system.

3.8.2 Stable

Additional queries:

Systems using PostgreSQL database ONLY:
Due to performance improvements in a stored procedure, the following query needs to be run:
DROP FUNCTION sq_get_parent_treeids(varchar, int, timestamp);

Systems using Oracle as a database do not require additional queries.

Additional comments: 

Systems using PostgreSQL database ONLY:
After running the above query, the step_02.php install script must be run to install the new version of the above stored procedure.
Systems using rollback ONLY:
To implement bug fixes related to rollback, the rollback triggers must be dropped and then re-created. The recommended procedure is the following:
1. Open a command line and change to the Matrix system root directory.
2. Run the following command line to temporarily disable rollback:
$ php scripts/rollback_management.php -s . --disable-rollback
3. Edit the [SYSTEM ROOT]/data/private/conf/main.inc file and change the line:
define('SQ_CONF_ROLLBACK_ENABLED', '1');
to:
define('SQ_CONF_ROLLBACK_ENABLED', '0');
4. Run the following command line to drop the triggers:
$ php install/step_02.php
5. Edit the [SYSTEM ROOT]/data/private/conf/main.inc file again and change the line:
define('SQ_CONF_ROLLBACK_ENABLED', '0');
to:
define('SQ_CONF_ROLLBACK_ENABLED', '1');
6. Run the following two commands on the command line to recreate the triggers and re-enable rollback:
$ php install/step_02.php .
$ php scripts/rollback_management.php -s . --enable-rollback.

Systems using Oracle as a database and not using rollback to not need to perform any additional steps to upgrade their system.

3.9.0 Development

Additional queries:

No additional queries are required for upgrades.

Additional comments: 

Systems using rollback ONLY:
To implement bug fixes related to rollback, the rollback triggers must be dropped and then re-created. The recommended procedure is the following:
1. Open a command line and change to the Matrix system root directory.
2. Run the following command line to temporarily disable rollback:
$ php scripts/rollback_management.php -s . --disable-rollback
3. Edit the [SYSTEM ROOT]/data/private/conf/main.inc file and change the line:
define('SQ_CONF_ROLLBACK_ENABLED', '1');
to:
define('SQ_CONF_ROLLBACK_ENABLED', '0');
4. Run the following command line to drop the triggers:
$ php install/step_02.php
5. Edit the [SYSTEM ROOT]/data/private/conf/main.inc file again and change the line:
define('SQ_CONF_ROLLBACK_ENABLED', '0');
to:
define('SQ_CONF_ROLLBACK_ENABLED', '1');
6. Run the following two commands on the command line to recreate the triggers and re-enable rollback:
$ php install/step_02.php .
$ php scripts/rollback_management.php -s . --enable-rollback

Systems not using rollback to not need to perform any additional steps to upgrade their system.

New Bugs Added To Bug Tracker

Bug ID	3.6.x	3.8.x	Dev	Description
1391	Y	N	N	URLs with % in the are being parsed
1392	Y	Y	Y	Regenerate metadata fails when schema is not applied to any asset
1393	Y	Y	Y	Images in wysiwyg div don't show in simple edit
1394	Y	Y	Y	Cannot deselect all WYSIWYG Plugins
1395	Y	Y	Y	Remap manager unable to match an entry if original URL contains a trailing slash
1397	N	Y	Y	screen_menu% keyword not showing correct page
1398	N	Y	Y	Cannot link LDAP User with space in DN to Matrix group
1399	N	Y	Y	Reindex hipo job error when squiz server is on
1400	Y	Y	Y	Session expiry settings are ambiguous when no checkbox is selected
1402	N	Y	N	Anchor are not a valid asset id
1403	Y	N	N	Metadata_X doesn't work in Asset Listing if X contains a space
1406	Y	Y	Y	Rollback mode shows entries one version earlier than intended

Notes:

Bug #1396 (some references are symlink unfriendly) was submitted by Raena (on behalf of Wombat) but was marked as not being a bug because the reporter was using a setup that symlinked the data directory to another location in the filesystem, which is currently unsupported.

New Feature Requests Added To Bug Tracker

Bug ID	Description
1401	Single page A-Z Listing mode
1404	Apply metadata key and metadata value on different screens
1405	Current Site option for dynamic root node

Bugs Fixed In The Bug Tracker

Bug ID	3.6.x	3.8.x	Dev	Description
1378	N	Y	Y	Black, undecorated links = poor usability
1389	Y	N	N	Backend users sent to login screen after changing status in Simple Edit mode
1392	Y	Y	Y	Regenerate metadata fails when schema is not applied to any asset
1393	Y	Y	Y	Images in wysiwyg div don't show in simple edit
1394	Y	Y	Y	Cannot deselect all WYSIWYG Plugins
1395	Y	Y	Y	Remap manager unable to match an entry if original URL contains a trailing slash
1397	N	Y	Y	screen_menu% keyword not showing correct page (partially fixed)
1398	N	Y	Y	Cannot link LDAP User with space in DN to Matrix group
1399	N	Y	Y	Reindex hipo job error when squiz server is on
1400	Y	Y	Y	Session expiry settings are ambiguous when no checkbox is selected
1406	Y	Y	Y	Rollback mode shows entries one version earlier than intended

View Comments