MySource Matrix has been superseded by Squiz Matrix. This site will remain available for archival purposes only; it is not intended as a current source of Matrix information. For all the latest on Matrix, including documentation and release information, visit the Squiz Matrix site.
covers versions 3.24.5 stable, 3.26.1 stable, 3.27.0 development
The next release of MySource Matrix will be next Monday 1st March when version 3.24.6 will be made available.
The release of MySource Matrix 3.26.2 has been rescheduled to Monday 8th March, due to final integration and testing of the Funnelback Search Package which will be available in this release under the SSV license.
Added to: 3.27.0 development, 3.26.2 stable
A new Keyword Modifier, "date_format", is available to format asset attributes which provide a UNIX timestamp. One argument is required to define the PHP date() format used for display.
For example, 2010 will print the four-digit representation of the year in which the current asset was created.
Added to: 3.27.0 development
The getParents() asset function in the JS API has been modified to allow a second argument referring to the number of levels to return, similar to getChildren(). When omitted, or set to 0, all parent asset IDs will be returned. Previous functionality of getParents() was to return only the first level, equivalent to setting levels to 1.
A new function "setMultipleAttributes()" is now available in the JS API. This function takes a single array of attribute names and their corresponding values to enable updating multiple attributes for an asset in one request.
No new generic features are currently scheduled for development.
Additional queries:
No additional queries are required.Additional comments:
No additional steps are required.
Additional queries:
No additional queries are required.Additional comments:
Implementations of the JS API which make calls to getParents() may need to be re-assessed, as this function now returns all parent asset levels by default, whereas this previously only returned one level. In order to retain a resultset which includes a single level only, calls to getParents() should be adjusted to pass "1" as the argument for the number of levels. For example:
// [asset_id], [num_levels], [callback_fn]
getParents(123, 1, resultGetParents);
| Bug ID | 3.24.x | 3.26.x | Dev | Description |
| 4201 | N | Y | N | Asset listing ignores user group restrictions (not confirmed) |
| 4202 | N | Y | N | Upwards direct asset listings use incorrect permissions (not confirmed) |
| 4203 | N | Y | N | Wrong asset tree where using Group Members setting (not confirmed) |
| 4204 | Y | Y | Y | JS API not handling '#' characters |
| 4205 | Y | Y | Y | Form submission asset throws error if accessed in edit mode |
| 4206 | N | Y | N | Contents' links of Current Pages attribute on multiple page is not linked correctly on simple edit interface (not confirmed) |
| 4207 | N | Y | N | Javascript API: transferred with MIME type text/plain (not confirmed) |
| 4209 | Y | Y | Y | Logging into Matrix via HTTP authentication not working |
| 4211 | N | N | N | Navigation appearance change for tunnelling remote content (not confirmed)* |
| 4212 | N | Y | N | Calendar Page included scripts being served from HTTPS incorrectly (not confirmed) |
(* Reported on 3.22.x builds)
Bug #4124 ("Calendar Page Asset not listing single calendar event assets with a time", reported 13th Jan by dquintal) was marked "Not a Bug". This was found to be a configuration issue relating to the time range of the Calendar Page, which was set to the range 08:00 to 08:00 (0 hours). This range does not wrap around days, so use of the 00:00 to 23:55 range has been recommended.
| Bug ID | Description |
| 4208 | New system events to broadcast update of lookups and permissions |
| 4210 | Feature Request : getKeywordsReplacements() for JS API |
| Bug ID | 3.24.x | 3.26.x | Dev | Description |
| 4173 | Y | Y | Y | Asset listing may display group name as '0' |
| 4199 | Y | Y | Y | Listing engine throws an error when expected structure does not exist |
| 4204 | Y | Y | Y | JS API not handling '#' characters |
There are currently no comments for this newsletter.