Site Search
Content Tools
Main Content
MySource Matrix Developer Newsletter Issue 3
Friday 24th December 2004
covers versions 3.2.0 stable, 3.3.0 beta, 3.5.0 development
News
Next Matrix Release
I know a lot of you are going to be away next week, so I'm giving you an early warning about the next release of MySource Matrix. MySource Matrix version 3.2.1 stable will be released on Tuesday the 4th of January 2005. This will be a bug fix release for the current stable version.
We will also be releasing version 3.3.1 beta on the web site. We did not release 3.3.0 beta due to a lack of upgrade instructions. The upgrade from a stable version of MySource Matrix to the beta version is quite complicated due to the large number of database changes, so version 3.3.1 beta will be released for new installs only. We will recommend that 3.3.1 be used for testing and evaluation only and that users do not attempt to upgrade their systems from a stable version.
Bug Tracker Versions
When submitting a bug, the reporter needs to select the version of the software they discovered the bug in. The bug tracker automatically selects the most recent released version (in our case 3.3.0 or 3.5.0 depending on your account type) to make it easy for reporters. However, all staff members reporting bugs should ensure that they have selected the minimum version in which the bug is present. Unless you know otherwise, this should be 3.2.0.
This will require all staff members to change the version during the bug reporting process. Before continuing to step 2 of the bug reporting process, please check that the version is correct. Once the bug is reported, previous versions cannot be added to the bug report, but previous versions already attached to the bug report can be removed.
Design Linking
Linking of designs has been changed from TYPE_3 to NOTICE links to stop problems with cascading changes. More information about this change is listed below in the New Features section. This change has not been made in 3.2.0 stable.
This change is very important because it means that design files will need to be moved into a web accessible location of the site tree. Previously, designs could sit anywhere within the tree and the cascading changes would ensure they get URLs when linked to a site or page. Now, these URLs will no longer be created (although the current ones will remain temporarily after the upgrade).
For example, if you have a folder called "Designs" that sits at the top level of the asset tree, you will have to move it under a site to update the URLs of the files inside the design. You can do this by moving the folder (or individual designs) under the site that uses them, or you may wish to create a new site with a URL similar to www.example.com/design_files, and place all your designs under that site.
New Features
Metadata Storage
Added to: 3.5.0 development
The storage of metadata has now changed in the database. Metadata is no longer stored as one table row per asset, with all metadata stored as a serialised array. It is now stored with one table row per field value for each asset. For example, metadata for an asset with one schema applied, and 10 fields in the schema, would have previously been been stored as one table row in the database. In the new system, each field is stored separately, creating 10 table rows for storage.
The previous metadata system was unable to retrieve selected metadata field values without fetching the entire metadata schema from the database. The new system will allow for a more efficient selection of metadata field values, as required by assets such as the Asset Listing or Search Page.
To upgrade an existing system, first run step 2 to add the new database table, and then run the upgrade script (scripts/upgrade_metadata_storage.php).
Asset Builder Create Types
Added to: 3.2.0 stable, 3.3.0 beta, 3.5.0 development
When using the asset builder to create multiple types of assets (eg. pages and files), the list of assets that can be created used to be displayed in DIVs above the create interface. This list is now displayed as an unordered list, but works the same way as the previous DIV interface.
The advantage of using the unordered list method is that you can use CSS to create custom interfaces, such as a tabbed interface. Using CSS to create custom interfaces with the DIV method was much harder.
Any clients who use asset builders with multiple create types should be informed that their lists will now change slightly. There will be bullet points before the create types and the list will have slightly more padding. Changes to their CSS files may be required the customise the interface for them.
New Keyboard Shortcuts
Added to: 3.5.0 development
Two new keyword shortcuts have been added for locking and unlocking an asset. You can now use ALT + A to acquire the lock on an asset, and ALT + R to release the lock.
New Image Keywords
Added to: 3.5.0 development
Two new keywords are now available for image assets and can be used in assets such as the Asset Listing. The new keywords are and . Both values are in pixels.
Improved Editing For Raw HTML Cells
Added to: 3.3.0 beta, 3.5.0 development
Raw HTML cells now use a monospaced font to allow users to correctly line up HTML elements and improve the readability of the textarea. A monospaced font is one in which all characters have an equal width, and so are able to be aligned under each other. This allows for cleaner HTML editing in this very basic editing interface.
Design Linking Changes
Added to: 3.3.0 beta, 3.5.0 development
When you link a design to a site or page, the design used to be TYPE_3 linked to the asset. TYPE_3 links don't appear in any menus, but they are still part of the asset tree. As a result, all status, schema, permission etc changes that occurred to a site or page would cascade to the design assets as well. This lead to many problems.
Designs are now NOTICE linked instead of TYPE_3 linked to stop the cascading of changes. The link is no longer part of the tree - it is just an association. All beta and development systems will need to be upgraded using the upgrade_design_linking.php script in the scripts directory.
New Bugs Added To Bug Tracker
| Bug ID | Stable | Beta | Dev | Description |
| 383 | Y | Y | Y | Problem deleting custom form recipient email addresses |
| 384 | Y | Y | Y | Option List attributes do not delete everything marked as deleted |
| 387 | Y | Y | Y | Get Links generates invalid query SQL under certain circumstances |
| 388 | Y | Y | Y | Custom Form - undefined index notice when using client-side validation |
| 390 | Y | Y | Y | Search page allows you to specify search fields for non-searchable attributes |
| 391 | Y | Y | Y | Custom Form-Client Side Validation does not work with complex formatting |
| 392 | Y | Y | Y | Some datetime attribute values end up as 01-01-1970 when inserted into the index table |
| 394 | Y | Y | Y | Cannot add thumbnail to Single Calendar Event |
| 395 | Y | Y | Y | Problem declaring multiple vars in a single MySource AREA |
| 400 | Y | Y | Y | Asset listing custom asset form cache not working |
| 401 | N | N | Y | Metadata keyword replacement in asset listing is broken |
| 403 | Y | Y | Y | Workflow spelled incorrectly on workflow screen |
| 404 | N | Y | Y | Thumbnail asset shows "current file" information twice |
Notes:
Bug #399 (CLI installer should check step requirements) was submitted by Andrei, but was not a bug. He suggested that step 3 of the install should check to see if step 2 needs to be run. These two scripts run independently of each other, and it is the developer's job to ensure that they run step 2 before running step 3 during upgrades. This is a reminder to all developers that step 2 now makes database changes and so should be run before step 3 for all upgrades - as the web installer does.
New Feature Requests Added To Bug Tracker
| Bug ID | Description |
| 385 | Auto-saving of content |
| 386 | Raw HTML content type's textarea could use a monospaced font |
| 389 | Requests via HTTP to HTTPS only URLs should auto-redirect |
| 396 | Be able to cascade current status |
| 397 | Wrong dependent children status |
| 398 | CLI installer should report detailed DB changes |
| 402 | Asset Builder's asset type selection HTML should be a list |
Bugs Fixed In The Bug Tracker
| Bug ID | Stable | Beta | Dev | Description |
| 173 | N | Y | Y | Permissions/Workflow should not cascade to linked designs |
| 202 | N | Y | Y | Cloned designs do not appear in the asset map as they are TYPE_3 linked to their new parent |
| 320 | N | Y | Y | Asset listing - shows files of a design customisation |
| 380 | Y | Y | Y | Deleted form section appears in form |
| 383 | Y | Y | Y | Problem deleting custom form recipient email addresses |
| 384 | Y | Y | Y | Option List attributes do not delete everything marked as deleted |
| 387 | Y | Y | Y | Get Links generates invalid query SQL under certain circumstances |
| 388 | Y | Y | Y | Custom Form - undefined index notice when using client-side validation |
| 391 | Y | Y | Y | Custom Form-Client Side Validation does not work with complex formatting |
| 392 | Y | Y | Y | Some datetime attribute values end up as 01-01-1970 when inserted into the index table |
| 400 | Y | Y | Y | Asset listing custom asset form cache not working |
| 401 | N | N | Y | Metadata keyword replacement in asset listing is broken |
| 403 | Y | Y | Y | Workflow spelled incorrectly on workflow screen |
| 404 | N | Y | Y | Thumbnail asset shows "current file" information twice |
View Comments
There are currently no comments for this newsletter.