covers versions 3.4.8 stable, 3.6.4 stable, 3.7.0 development
A release candidate of MySource Matrix 3.8.0 will be released on Monday. Version 3.8.0 adds a significant amount of functionality, especially in the areas of asset listings, searches, usability and performance. If no significant problems are found with the release candidate, MySource Matrix 3.8.0 stable will be released on the 6th of March.
MySource Matrix version 3.6.5 will also be released on Monday for users of the existing 3.6 stable branch. This is a bug fix only release.
The release candidate of MySource Matrix 3.8.0 signals the end of development for the 3.8 branch. No new core development will be incorporated into 3.8 unless it adds significant performance or usability benefits.
Asset listings (and search pages) have an option where you can select a list of statuses that the listed assets must have. The complete list of assets will be filtered to list only those assets that match the status and only those assets the current user has read access to.
You will get a significant performance improvement by clearing this list. If no statues are selected, the listing will filter results that the current user does not have read access to but will not check their status. The only downside is that logged in editors and administrators will see under construction assets in the lists if they have write access to them. They will need to log out to get an accurate preview of what the public users see (although this is always the case in reality).
Added to: 3.7.0 development
A new role based system has been developed MySource Matrix. Roles are created like user groups and then used within the permissions and workflow systems. Each asset now has a Roles screen to allow administrators to assign Users or User Groups to a role. Role assignments can be cascaded in the same way as permissions are. When selecting Users or User Groups to assign permissions to, or when adding them to workflow steps, a Role can be added instead. In this case, the role represents a user or a group of users but differs depending on the asset to which it is assigned.
Added to: 3.7.0 development
A new feature has been added to designs that allows them to exported to TAR archives and imported from properly constructed TAR archives. This functionality is available on the new Import/Export screen of the design asset. Note that customisations are not exported or imported.
No new generic features are currently scheduled for development.
Additional queries: No additional queries are required for upgrades.
Additional comments: No additional upgrade steps are required.
| Bug ID | Stable | Beta | Dev | Description |
| 1110 | N | N | Y | Raw HTML content type default size is too small |
| 1112 | N | Y | Y | Keywords not working in WYSIWYG editor in IE |
| 1113 | N | N | Y | Bulkmail exclude times not quite working |
| 1115 | N | Y | Y | Basic formatting buttons in WYSIWYG editor not working in IE |
| 1116 | N | N | Y | Global Keywords don't work with Custom Form |
| 1118 | N | N | N | Editor isn't saving content with right encoding (not confirmed) |
| 1119 | N | N | N | Mulitple page safe edit not working (not confirmed) |
Bug #1111 (Content type displayed as --Leave Unchanged--) was submitted by James Hunter but was marked as not being a bug as this is the intended behavior of the field and was introduced to fix a previous bug.
Bug #1114 (JS Calendar - days out of the week) was submitted by gnoel but was marked as Can Not Replicate after the functionality worked correctly for the calendar developers.
| Bug ID | Description |
| 1117 | Ability to configure Cron "blackout" period |
| Bug ID | Stable | Beta | Dev | Description |
| 1108 | N | Y | Y | Can't purge trash w/ desing customisations w/ associated files |
| 1110 | N | N | Y | Raw HTML content type default size is too small |
| 1112 | N | Y | Y | Keywords not working in WYSIWYG editor in IE |
| 1113 | N | N | Y | Bulkmail exclude times not quite working |
| 1115 | N | Y | Y | Basic formatting buttons in WYSIWYG editor not working in IE |
| 1116 | N | N | Y | Global Keywords don't work with Custom Form |
There are currently no comments for this newsletter.