covers versions 3.4.2 stable, 3.5.0 development
The first beta release of MySource Matrix for some time will be released next week. MySource Matrix 3.5.0 beta has an extensive range of new features that will allow for more advanced systems to be created in the future. The database schema has also been reviewed and modified to complete support for Oracle as a backend database for MySource Matrix.
After the release, all developers should ensure they have a 3.4.x stable, 3.5.x beta and a 3.7.0 dev system checked out for bug fixes.
A bug fix release of MySource Matrix will be released next week along with the new beta. MySource Matrix 3.4.3 contains a number of bug fixes and clients should be advised to upgrade to this version if they are experiencing any problems with their current system.
I'm off to the UK next week and wont be able to release the newsletter. Marc has kindly offered to write it for me, so there will still be a developer newsletter released next Friday. Thanks Marc.
Added to: 3.5.0 development
A new feature has been added to allow user sessions within MySource Matrix to be maintained for a customisable period of time (eg. 7 days). A user is able to keep their session information (including login details and shopping basket contents) for a period of time without having to have their web browser open for the entire period. They could log into MySource Matrix, edit some content, come back in 3 days and still be logged in.
The 3 different types of session timeout options that can be set are: - whether a user's session should expire when they close their browser - whether a user's session should expire when they've been inactive for a certain period of time - whether a user's session should expire if they haven't authenticated for a certain period of time
The feature has been added as a global/group preference rather than a system wide configuration setting, so you can choose to customise session timeout options per user group if you require, or use the global preference for all users.
Added to: 3.5.0 development
The metadata storage system has been improved to allow for faster retrieval of metadata values. As a side effect, various problems with default values have been fixed. A new feature has also been added to allow you to revert any metadata field to the current default value.
If a metadata field's value is changed from the default and then back again, it will not be seen as reverting to the default value because the default value may have changed or the user may actually want the value to remain unchanged even if the default is modified. Previously, there was no way to move a field back onto the default value. This new checkbox gives you the ability to do so.
To be added to : 3.5.0
Estimated start date: already in development
Estimated end date : 17th June 2005
Run step_02.php: yes
Run step_03.php: yes
Run compile_locale.php: yes
Additional queries: No additional queries are required for upgrades.
Additional comments: Run "php scripts/upgrade_metadata_default_values.php ."
| Bug ID | Stable | Beta | Dev | Description |
| 666 | Y | - | Y | Similar URLs breaking getLineageFromURL |
| 667 | Y | - | Y | Custom Form bodycopies not cloned with form |
| 669 | N | - | Y | Asset Builder WYSIWYG Keywords missing |
| 670 | N | - | Y | Asset Builder using undefined function translated() |
| 671 | N | - | Y | Cant edit status and content of page in simple edit during workflow (not confirmed) |
| 672 | Y | - | N | \"Divide by Zero\" error if search page has \"Assets per Page\" set to zero |
| 673 | N | - | Y | Issue with treeid components being out of ASCII order |
Bug #565 (Search mulit-select doesn't work) was submitted by Garth on April the 7th, but was marked as not being bug after it could not be replicated by two different developers. It appears something may be wrong with the search page setup causing this problem.
Bug #615 (keyword select dropdown missing from Customised List Position Formats) was submitted by Karen (Future Publishing) on the 8th of May but was marked as not being a bug because it could not be replicated by Australian or UK developers.
| Bug ID | Description |
| 665 | Feature request - reports have a text (not just colour) indicator |
| 668 | Custom Form file upload should create Image asset if image uploaded |
| Bug ID | Stable | Beta | Dev | Description |
| 206 | Y | - | Y | Custom Form - questions being shown on the asset map in reverse sort order |
| 220 | Y | - | N | Acquiring lock on settings screen for a Backend user crashes browser |
| 273 | Y | - | Y | Linked CSS Design Area - Changing css asset |
| 327 | N | - | Y | Archive Status Colour makes name almost unreadable |
| 498 | Y | - | Y | DIV properties content type should default to current type |
| 501 | Y | - | Y | Login_Form design area input boxes not using classes |
| 534 | Y | - | Y | Problems with declared_vars design area |
| 608 | N | - | Y | Created assets remain in memory |
| 616 | Y | - | Y | Relevance weights reset during step_03 |
| 618 | Y | - | N | Heading styles shortcut keys not working in WYSIWYG |
| 633 | N | - | Y | No metadata field is displayed if 'Only if filled' option is set |
| 635 | Y | - | Y | Hipo Jobs with large number of assets fail when processed in one group |
| 636 | Y | - | Y | Workflow schemas can be removed during workflow |
| 643 | Y | - | Y | Option list attribute ignores typed values if you dont click \"add\" |
| 652 | N | - | Y | The asset being removed from the cache is still in use when trashing |
| 658 | Y | - | Y | Standard Page Content Div won't release lock with parent |
| 659 | N | - | Y | Listing Engine - Position not respected |
| 661 | Y | - | Y | What's new asset returns error with less than three assets |
| 662 | Y | - | Y | Search within search returns no results |
| 663 | Y | - | Y | Image File Asset - Front End Editing Layout Anomaly |
| 664 | Y | - | N | Ecommerce forms cant be created |
| 669 | N | - | Y | Asset Builder WYSIWYG Keywords missing |
| 670 | N | - | Y | Asset Builder using undefined function translated() |
| 672 | Y | - | N | \"Divide by Zero\" error if search page has \"Assets per Page\" set to zero |
There are currently no comments for this newsletter.