A bug was fixed this week in both 3.6.x and 3.7.x that caused all applied paint layouts in the system to be removed when a file asset was purged from the trash.
The new re-built thesaurus in 3.7 has quite a few changes, but there is one important one for users that use synonym searching. The synonym relation name has changed from 'Synonyms' in 3.6.x to 'Synonym' in 3.7. Please ensure you update your thesaurus relationships when upgrading to 3.7.
A new stable version of MySource Matrix was released for the 3.6 branch on Monday. Version 3.6.3 is primarily a bug fix release but does contain one new feature. Along with the 18 bug fixes, a new User Group Link Manager asset was added.
A new stable version of MySource Matrix will be released for the 3.6 branch on Monday. Version 3.6.3 will be a bug fix only release. No release for the 3.4 branch is required this month as no bug fixes have been committed to it.
During the development phase between 3.4.x and 3.6.x, a default value of all listing assets was changed. The number of assets displayed per page was changed from "0" to "10". When systems were upgraded from 3.4.x to 3.6.x, listings that were still using the default value (ie. that field was never modified) were changed to only list 10 assets per page rather than show all assets on the same page.
The createLink() method of the asset manager now uses a stored procedure to determine the next treeid to use for inserts. This is a fairly major core change so if anyone notices anything todo with linking in a 3.7.x system that seems odd, please report the problem ASAP.
A new stable version of MySource Matrix was released this week. Version 3.6.2 contains 19 bug fixes and no new features. All clients running 3.6.x versions of MySource Matrix should be upgraded to this new version.
Monday is release day for MySource Matrix. Version 3.6.2 stable will be released publicly and 3.4.8 will be released if there are bug fixes available. Version 3.4.8 is not scheduled for release at this time.
The listing engine assets have had their ID values for asset selections sanitised for XHTML compliance, both in their printing and in the JavaScript. Unfortunately due to the way the sanitisation works the selection ID has changed from
Beta is not in the best shape, so we have moved all MySource Matrix CVS repositories from beta.squiz.net to delta.squiz.net. To change your systems to point to delta, please user the script cvsdelta.sh or cvschange.sh (depending on what is available to you).
Our two new developer boxes are nearly ready to go. We are testing the install and running of MySource Matrix as well as the unit test framework before we allow all MySource Matrix developers onto them.
New stable releases of MySource Matrix were released on Tuesday. Versions 3.4.7 and 3.6.1 were released internally and are not available for download from the MySource Matrix web site.
With Monday being a public holiday, 3.6.1 stable and 3.4.7 stable will be released on Tuesday next week.
When entering the password for a user account incorrectly 3 times, a message was displayed to the user letting them know that the account has been locked. If someone was looking for a valid user account, this message would indicate to them that the account was valid. This was a potential security issue that could have caused an user enumeration issue. When an account is locked, the user no longer receives this message. Instead, the standard "User Not Found" message is displayed. The fact that the account was locked is still recorded in the system log file.
Previously, write access was required to change the group restrictions for a user. This has now been changed to require administrator as it is an administrative task that normal content editors should not be able to perform. This change has been made to both 3.6.x and 3.7.x and will be in the 3.6.1 release next month.
A new stable version of MySource Matrix was released on Monday. Version 3.6.0 is available from the web site and is the first stable release to include support for the Oracle database.
The new stable version of MySource Matrix will be released on Monday. Version 3.6.0 will include a range of great new features to allow for more advanced web sites to be created.
The triggering system of MySource Matrix uses the sq_trig_hash table to cache out various config information that speeds up the processes of looking for triggers that need executing when an action is performed. This table did not have a primary key defined. This weeks upgrades for 3.6.x and 3.7.x provide a query to add a primary key to the sq_trig_hash table.
There is no general MySource Matrix developer news this week.
Some query changes were committed this week to ensure all INSERT, UPDATE and DELETE queries are executed within transactions. This is sometimes overlooked and wasn't so much an issue with PostgreSQL as it COMMITs the transaction when the script ends regardless of if an explicit COMMIT has been executed.
New stable and release candidate versions of MySource Matrix were tagged on Monday and are available for client updates. These new versions have not been posted on the web site.
As reported last week, the next stable release of MySource Matrix (3.6.0) has been pushed back a month in order to test some new performance improvements in both PostgreSQL and Oracle. The next release candidate (3.6.0 RC2) will be released on Monday along with 3.4.5 stable.
Several changes have been made to MySource Matrix this week to help with system performance and caching. Due to the importance of these features to clients, they have been made to both 3.6.0 RC1 and 3.7.0 development. Being so close to the scheduled release of 3.6.0 stable, we have decided to postpone the stable release for another month and release another release candidate (3.6.0 RC2). This will allow for additional testing of these changes to ensure they are indeed working correctly in production systems.
Some more changes have been made to My Source Matrix for what we hope is a permanent fix for the treeid problems we've been having recently with database systems have been set to a specific collating order (which can't be changed after initdb is run on the system). Basically it involves changing the treeid field from a varchar to a binary string type (bytea). These fields sort based on byte (read: ASCII) values, a critical feature of the treeid field's operation. This would also eliminate any problems still seen after the temporary changes where some characters are considered "equal" and thus ignored in the sort order.
New versions of MySource Matrix were released on the web site this week, the first in 3 months. A big thank you to all the developers for the huge number of bugs that managed to get fixed Monday morning and to Marcus for helping with the release.
A new release candidate of MySource Matrix will be released on Monday. Version 3.6.0 RC1 will mark the end of the new stable feature set and no new features will be added to the 3.6.x branch from this point onward. This will allow us to move steadily toward a new stable release in either August or September, pending beta testing and bug fixing.
A change has been made to the trigger events that are fired during the creation of an asset. The "link created" trigger event is no longer fired during asset creation, leaving "before asset created" and "asset created" as the two trigger events that can be used to perform actions on newly created assets.
This week we welcome three new MySource Matrix developers to the Sydney office, Pratibha, Scott and Yosep. Please make each of them welcome and remember how hard it was when you first had to start Matrix development.
The first release of a MySource Matrix beta in some time was released on Tuesday which featured 116 bug fixes and more than 60 noteworthy features. Well done to all developers. The next stable version (3.4.3) was also released. Clients should be advised to upgrade to this version if they are experiencing any problems with their current system.
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.
Moving attributes higher up an asset type tree has been fairly complicated in the past. Changes have been made to the install/upgrade system to make this process a bit easier for developers. The new system works as follows:
It was reported in last week's newsletter that exact phrase matching was being added to the MySource Matrix search engine. Further development work as uncovered problems with PostgreSQL text indexing that has resulted in this feature having to be postponed for PostgreSQL installs of MySource Matrix.
There is no general MySource Matrix developer news this week.
The 3.4.2 stable release planned for Monday did not happen as expected. The MySource Matrix web site is currently being replanned and rebuilt from scratch, so future public releases will not be conducted until this has been completed. However, MySource Matrix was tagged at 3.4.2 on Monday and clients can be upgraded to the mysource_3-4-2 tag whenever required. We just didnt make a public release this month.
A bug fix release of MySource Matrix will be released on Monday the 2nd of May. MySource Matrix 3.4.2 will not contain any new features. There will also be no beta release again this month.
A new PHP developer, Darren McKee, will be starting in the MySource Matrix team on Wednesday. Please make him feel welcome.
A bug was found where a user could select to nest a redirect page inside a standard page by using the nest content cell type. When trying to edit the contents of the standard page, the user would be redirected by the redirect page that is being nested and was unable to edit the contents of the standard page. This also meant they were unable to deselect the nested redirect page.
A bug fix release of MySource Matrix has now been released. Version 3.4.1 fixes a number of core bugs. All clients on 3.4.0 should be upgraded to 3.4.1 if they are experiencing any bugs. This upgrade is not a complicated process.
A bug fix release of MySource Matrix will be released on Monday the 4th of April. MySource Matrix 3.4.1 will not contain any new features. There will also be no beta release this month.
It was reported last week that design customisations now seem to purge correctly. Chris N has since confirmed this during the last week on 3.4.0.
Avi has reported that it seems as though Design Customisation assets can now be trashed and purged from the trash. Previously, this caused a lot of problems and never worked. Avi speculates that the design linking changes made to 3.4.0 may have stopped the previous errors, but nobody really has any idea why this is suddenly working.
The second stable release of MySource Matrix was released on Monday. The upgrade procedure from 3.2.2 is more complicated than previous upgrades, but is detailed in the release notes. We have had reports of non-client users upgrading systems successfully from 3.2.2 to 3.4.0 using this procedure.
The second stable release of MySource Matrix will be released on Monday. The 3.4.0 release will also include the first stable releases of the Calendar, Ecommerce and Lexicon commercial module packages.
Following on from the changes made to the Inbox asset to allow for messages to be sent to other users, additional changes have been made to standardise and clean up the interface. These changes were suggested during the Feature Review meetings the MySource Matrix development team conduct each Monday. New development versions of MySource Matrix will contain this updated and cleaner interface.
I have added a short new upgrade section to this newsletter that will let everyone know what they need to do to upgrade their MySource Matrix systems each week. This should create a history of changes so monthly upgrade scripts can be compiled more easily.
MySource Matrix versions 3.4.0 RC1 and 3.2.2 have been released and are available for download on the MySource Matrix web site. If all goes well, the next release will be version 3.4.0 stable on the 7th March.
A new release candidate of MySource Matrix will be released on Monday the 7th. Version 3.4.0 RC1 contains a minimal number of changes from the 3.3.1 beta version currently posted on the web site and will not include upgrade instructions from the current 3.2.x stable versions.
The current release schedule indicates that a new branch and beta version of MySource Matrix will be released with each release candidate. Going by this release schedule means that when 3.4.0 RC1 is released next month, a new 3.5.0 beta will also be released. Due to the fact that a release candidate is not yet considered stable, we would have 3.2.2 stable, 3.4.0 RC1, 3.5.0 beta and a dev version floating around.
We have started the process of gathering real benchmarking data for MySource Matrix, which should be available next week. If all goes well, the next release of MySource Matrix may include some benchmarking statistics that can be released to clients and the general public.
The return value of the getParents() method in asset_manager.inc has been changed to use the same format as the getChildren() method. All developers should be aware that the getParents() method no longer returns an array of assetids, but now returns an array of assetids with type codes.
Versions 3.2.1 stable and 3.3.1 beta of MySource Matrix have been released and are now available on the MySource Matrix web site for download. All current 3.2.0 systems should be upgraded to 3.2.1 to fix a number of bugs discovered since 3.2.0.