MySource Matrix Developer

Main Content

MySource Matrix Developer Newsletter Issue 24
Friday 20th May 2005

covers versions 3.4.2 stable, 3.5.0 development

News

Search Exact Phrase Matching

It was reported in last week's newsletter that exact phrase matching was being added to the MySource Matrix search engine. Further development work as uncovered problems with PostgreSQL text indexing that has resulted in this feature having to be postponed for PostgreSQL installs of MySource Matrix.

Oracle has a much advanced text indexing system, so exact phrase matching may be available to Oracle clients in the future. Custom exact phrase matching will be built for the BLIS project using Oracle, but this will not be available to other Oracle based clients without additional development work.

New Features

Metadata Thesaurus Field Improvements

Added to: 3.5.0 development

The thesaurus metadata field has been changed to allow an editor to select multiple terms for the field using the thesaurus browser. The metadata field can be configured to set a maximum number of terms that can be entered. Each selected term also shows the category lineage from the top of the thesaurus to help editors understand the context of the term when selecting additional fields.

It should be noted that the category lineage will only work correctly if the built-in "category" relationship is used to categorise terms in a thesaurus. Custom relationships cannot be used to determine lineage.

Backend Translation (stage 4)

Added to: 3.5.0 development

All remaining strings within MySource Matrix have now been translation enabled. The translation project now requires a full translation of the MySource Matrix strings to be completed in a language other than English. A script has been prepared to aid in this translation effort by combining all translation files into 4 main files. These 4 files can be given translated and returned back to us.

Advanced Asset Caching For Scripts

Added to: 3.5.0 development

The asset cache of the Asset Manager has been rewritten to offer more control on the number of assets that reside in memory. Once a loaded asset is not used anymore it will remain in memory until the cache size reaches a certain size.

The cache size is now defined by two new constants in the main configuration file: one for the scripts running from the command line (SQ_CONF_ASSET_CACHE_SIZE_CLI) and one for those running from the web server (SQ_CONF_ASSET_CACHE_SIZE_WEB). The default value is -1, a special value preventing the cache from unloading any assets no matter what size the cache has grown to. This emulates the existing functionality of MySource Matrix the best and should result in no unexpected problems for upgrades.

This update will help external scripts to execute many operations within MySource Matrix in one go without using an excessive amount of memory.

Although this modification is transparent for the rest of the MySource Matrix classes, the existing code will have to be modified to take advantage of this cache. Every call to getAsset() should be followed by a call to forgetAsset().

Note that this is not a permanent shared cache for all users like a frontend page content cache is. This cache relates to the loading and reuse of assets in a single script execution.

Editable Form Submissions

Added to: 3.5.0 development

Form submissions now have a details screen where you can edit the answers to questions, as long as those questions still exist in the form that created the submission. If the submitted value is no longer a valid value for the question you can leave it intact, or specify a new, valid, value. If new questions have been added to the form and they are required, you can still leave them blank when editing the submission. You can access the submission's details screen via the submission log screen of the form asset.

Planned Development

Search Page Dynamic Root Nodes

To be added to : 3.5.0 development
Estimated start date: already in development
Estimated end date : 25th May 2005

Asset listings have been able to accept dynamic root nodes for a while now. Search page is now getting the same functionality. This will allow you so send the search page the a list of asset IDs it should use as the root search nodes on the query string.

Upgrading

3.5.0 Development

Run step_02.php: no Run step_03.php: yes Run compile_locale.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

Bug ID Stable Beta Dev Description
631 Y - Y Recurring Event Cancellation asset asks for name and wont create
632 Y - Y Firefox crashes when repeatedly linking (not confirmed)
633 Y - Y No metadata field is displayed if 'Only if filled' option is set
634 Y - Y Multi-day events don't always show up on the first day
635 N - Y Hipo Jobs with large number of assets fail when processed in one group
636 N - N Workflow schemas can removed during workflow (not confirmed)
637 Y - Y Error when creating calendar event modification
639 Y - Y Event manager - memory
641 Y - N Unquoted statement in hipo_herder.inc
643 N - N Option list attribute ignores typed values if you dont click "add" (not confirmed)
644 N - Y Insert Link box's asset finder is broken in DEV
645 Y - Y Selecting to NOT cascade permissions causes lock cascades
Notes:

Bug #638 (getAssetInfo fails when getting info for a large number of assets) was submitted by Marcus, but was marked as "Will not Fix". The bug relates to a condition where if you ask Matrix to give you information about more than 10,000 assets at a time, the database query will fail. The real cause of this problem is that the custom form submission listing is not paginated and so tries to load all 10,000 form submissions in one go. A feature request has been added to paginate this interface and stop this error from occurring.

New Feature Requests Added To Bug Tracker

Bug ID Description
640 System/Submission Time in Custom Form email
642 Paginate form submission list in Custom Form's submission logs screen

Bugs Fixed In The Bug Tracker

Bug ID Stable Beta Dev Description
395 Y - Y Problem declaring multiple vars in a single MySource AREA
471 N - Y Custom form displays date when only time is set to display
480 Y - Y Client Side validation errors if Selection Limit rule is applied to Tickbox List
484 Y - Y Custom form select list won't allow "0"
526 Y - Y Customisation cannot be created in some case
537 Y - Y Default Value Not Displaying in Chosen Date Format
540 Y - Y Customised design areas not always updated
580 Y - N Form container for "test fr" (Id: #1683) could not print frontend
587 Y - Y Custom form, switching HTML/plain text email breaks WYSIWYG
599 Y - Y Metadata Date Incorrect When Keyword Chosen
627 Y - Y Mouseover description popups for calendar events in wrong position
629 N - Y When exporting form logs the frontend errors
631 Y - Y Recurring Event Cancellation asset asks for name and wont create
633 N - Y No metadata field is displayed if 'Only if filled' option is set
634 Y - Y Multi-day events don't always show up on the first day
637 Y - Y Error when creating calendar event modification
639 N - Y Event manager - memory
641 Y - N Unquoted statement in hipo_herder.inc
644 N - Y Insert Link box's asset finder is broken in DEV
645 Y - Y Selecting to NOT cascade permissions causes lock cascades
Add a Comment

You must click here to log in before posting comments.

View Comments

There are currently no comments for this newsletter.