Squiz Labs Blog - The latest news from the R&D division of Squiz®

Squiz Matrix Newsletter #401

This week we have three new features to report, including the Google Maps package upgrade to version 3 of the Google Maps JavaScript API. Continue reading below for more information on all this week's developments.

Google Maps Package Updated to Google Maps API V3

Due for release in version 4.12.0 (November 5th 2012)

Squiz Matrix's Google Maps package allows you to embed Google Maps within your site that your users can view and navigate with. These maps can contain a variety of map type options, plotted locations and other functionality.

Google is currently in the process of depreciating version 2 of its Google Maps JavaScript API after the new release of version 3 of the API. As a result, the Google Maps package within Matrix has been upgraded to this release.

Changes resulting from this upgrade include:

• A number of configuration options on the Details screen of the Google Map asset are now automated by Google Maps and are no longer available.
• The Street View overlay functionality (including the related keyword replacements) are no longer available. The Google Maps API now uses the familiar pegman feature to initiate Street View.
• Google Earth is no longer supported. This includes the Moon Elevation, Moon Visible, Mars Infrared and Sky Visible map types. These options will no longer be available for selection.
• Mouse zoom scrolling is no longer customisable, it is enabled by default.
• The map initialisation code has been modified.

The resulting functionality is a more accessible and intuitive mapping experience.

Most users should be able to continue using their existing implementations without complication. Users using functionality that has been removed, however, should review their implementations and make any necessary modifications before upgrading your system.

New Ignore Editable Attribute Parameter on the setMetadata() Function

Due for release in version 4.12.0 (November 5th 2012)

The setMetadata() core system function sets the metadata values for an asset, for example, when a user inputs new metadata values on an asset's Metadata screen.

Currently, this function respects the Editable? attribute of metadata fields, meaning that it does not update the values of metadata fields that are set as non-editable.

This minor enhancement adds an additional parameter to this function, which when enabled, stipulates that the function will ignore the Editable? attribute, and make changes to the metadata value.

The ignore_editable parameter can be set in the metadata_manager.inc system file. By default, this parameter is set to FALSE.

function setMetadata($assetid, $metadata, $contextid=NULL, $update_asset=TRUE, $broadcast_all_fields=FALSE, $ignore_editable=FALSE)

This enhancement has been added to aid developers using custom scripts to set the metadata on non-editable metadata fields.

Enhancement to the Metadata WYSIWYG Field Type

Due for release in version 4.12.0 (November 5th 2012)

The Metadata package's WYSIWYG field type allows users to enter rich text into the metadata field, using Squiz Matrix's WYSIWYG editor. Previously, however, the system's global WYSIWYG plugin settings where not being completely recognised within the WYSIWYG metadata field; certain plugins were not being made available to users.  

This enhancement to the metadata WYSIWYG field type allows all configured plugins to be made available to users within the WYSIWYG tools on the Details screen.