Site Search
Content Tools
Main Content
MySource Matrix Developer Newsletter Issue 151
Friday 2nd November 2007
covers versions 3.14.5 stable, 3.16.1 stable, 3.17.0 development
News
Releases Next Monday
Two new MySource Matrix releases are unleashed next Monday (5th Nov): versions 3.16.2 and 3.14.6. Both are predominantly bug-fix releases.
New Features
Link Value Viewing and Editing Options
Added to: 3.17.0 development, 3.16.2 stable
The Linking screen of an asset has been updated to provide new options relating to link values. Those links whose type is editable (essentially, TYPE_1 and TYPE_2 links) also offer the ability to edit the values of those links.
Note that link values are an advanced option that are not required to be edited in most normal circumstances.
Search Page Updates
Added to: 3.17.0 development, 3.16.2 stable
New options for searching on the Search Page:
- "Search as Public User": when turned ON, this option forces the Search Page to search as the Public User, even when someone is logged in.
- "No Group Check" and "No Role Check": these allow you to skip certain permission checks for performance improvements. Specifically, these will not expand a user's roles and groups to be included in the permission check. This is an advanced option that probably shouldn't be used unless you understand the implications of this.
Planned Development
No new generic features are currently scheduled for development.
Upgrading
3.17.0 Development
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 | 3.14.x | 3.16.x | Dev | Description |
| 2733 | N | Y | Y | Set Future Lineage trigger action throws an error when supplied a valid datetime from attributes |
| 2734 | Y | Y | Y | Refresh cache cron job prints to stdout causing the cron daemon to send emails to the owner |
| 2736 | Y | Y | Y | LDAP Users can't create Design customisations |
| 2744 | Y | Y | Y | Data source assets do not allow list positions to be set in an asset listing |
Notes:
Bug #2743 ("Asset Listing next page keyword should not print text", feature requested by nnhubbard) was marked as a duplicate of bug #1684, "Option to suppress next/last page text if no next last." (requested by Richard on 15th September 2006) and closed.
New Feature Requests Added To Bug Tracker
| Bug ID | Description |
| 2735 | Insert DIV in Safe Edit |
| 2737 | Custom Grouping on multi-select meta data |
| 2738 | WYSIWYG Insert Link protocol confusion |
| 2739 | RSS Data Source mangles HTML/multiple fields |
| 2740 | Calendar Creates Invalid XHTML Code |
| 2741 | RSS Feed Reader doesn't fix remote URLs |
| 2742 | Parsefile should have a MySource Comment style/sequence |
Bugs Fixed In The Bug Tracker
| Bug ID | 3.14.x | 3.16.x | Dev | Description |
| 2717 | Y | Y | Y | PHP warning printing metadata w/ Rolling Calendar Page |
| 2718 | Y | Y | Y | PHP notices on Image Asset Builder |
| 2722 | Y | Y | Y | Unable to capture a metadata field and the asset id of an event asset calendar |
| 2729 | Y | Y | Y | Cannot change the users who created the asset |
| 2733 | N | Y | Y | Set Future Lineage trigger action throws an error when supplied a valid datetime from attributes |
| 2734 | Y | Y | Y | Refresh cache cron job prints to stdout causing the cron daemon to send emails to the owner |
| 2736 | Y | Y | Y | LDAP Users can't create Design customisations |
| 2744 | Y | Y | Y | Clone Asset trigger action gives error when 'Ignore Permissions' option is checked |
View Comments
There are currently no comments for this newsletter.