Squiz has some exciting news to share! Recent release of MySource Matrix, v3.28, includes some significant changes and upgrades, most significantly, that it now includes all of the SSV modules as GPL.We are happy to announce:
Searches are performed against Collections, which are linked to MySource Matrix Site assets, and Meta-Collections which comprise multiple Collections (ie; for searching more than one site at a time). Configuration of Collections, Metadata mappings and indexing are performed under the Funnelback Manager asset.
The Funnelback Search Page asset has been expanded to include bodycopies for Contextual Navigation, Type Formats (HTML, PDF etc.), Featured Pages and spelling suggestions.
Funnelback search integration is performed through interaction with external binaries. These are included within MySource Matrix SSV for configuration during installation or upgrade.
Search indexing functions differently to MySource Matrix Search, in that content is not immediately indexed when updated. Scripts are available within the Funnelback package which can be added to the cron to update the index periodically. The frequency at which the indexer should be run is dependent on the amount of content being indexed and the dynamic requirements of this content. Collections can be reindexed independently of each other.
This functionality allows multiple sets of Workflow Steps per Workflow Schema, and allows Administrators to select which of these sets is to be used for any given Workflow process.
Please note that new and existing Workflow Schema steps will be moved under a "Default Stream" which resides under the related Workflow Schema. This Default Stream cannot be moved or deleted.
A checkbox "Replace keywords in the set value" is provided in the Set Metadata Value and Set Attribute Value Trigger Actions to indicate whether keywords supplied in these fields are to be replaced upon evaluation rather than being treated as literal text. This can be used with both asset-level and Global Keywords.
The "Preferences" screen of User Group assets now provides the ability to assign a Context ID to be used for User Group members for a Matrix session.
A Trigger Condition has been added to evaluate whether or not the user who caused the associated Trigger to fire was the Public User (ie; not logged in).
The attribute value for "start_at_level" can now be specified as a negative number to refer to direct parent assets of the current asset. For example, -1 would refer to the direct parent, -n to the nth direct parent. Other positive numbers (0 = current asset, 1 direct child etc.) still continue to function as previously defined.
The PayPal Payment Button asset now supports "Donate", "Add to Cart" and "View Cart" button types, in addition to "Buy Now". The options for each Button Type are available by toggling the Button Type from the "Details" screen and clicking "Commit".
This button allows the name of the Organisation or purpose of the donation to be supplied, as well as the ability to specify a fixed amount.
Add To Cart and View Cart buttons
This allows for cart-based transactions to be maintained by the PayPal environment. The "View Cart" button provides an option to open the cart contents either within the current browser window/tab or in a new window/tab.
PayPal IPN Receiver modifications
This asset has been modified to accept the "Cart" transaction type and to populate the receipt of the generated PayPal Order.
The Create Links HIPO Job is now used in this script to perform "move" operations, rather than direct asset manipulation.
The system_update_lookups.php script now supports an optional "--verbose" argument to display any errors which may occur as a result of updating lookups. The script can now be executed from the Matrix System Root directory as follows:
php scripts/system_update_lookups.php . 123 --verbose
Modifications have been made to the Matrix core to provide improvements in the evaluation speed of keywords and when site-based options are selected from the Parameter Map.
Instead of loading each asset in the lineage to determine whether they are in Safe Edit, this is now only performed upon assets in the lineage which are in Safe Edit. This should show a slight improvement on the initial load on long lineages with many assets not in Safe Edit.
A query has been optimised in the Purge Trash HIPO to return assets in "sort order". This modification removes the need to update the sort order of nearby assets, which may result in a performance increase when running this HIPO.