Version 5.4.18

Version No5.4.18
Release Date

 

About this Release

Patch release with minor enhancements and fixes

Modules affected

Data Share, Installers, iShare Core, Publisher, Studio, Web Services

Pre-requisites

This release of iShare requires the following to be installed:

  • Windows Server 2012 R2, 2012, 2008 R2 or 2008
  • Internet Information Services (IIS) Versions 8.5, 8.0, 7.5 or 7.0
  • Microsoft .NET Framework V3.5 Service Pack 1 (installed and enabled)

iShare and its modules are installed using the iShare Installer. Any 3rd Party software required by iShare may be installed using the Astun 3rd Party Installer. The AstunPGInstaller will install any Astun scripts on your Data Share database depending upon the selected Install Options.

Installers

  • AstunPGInstaller - Fixed comment string that was preventing Police SQL updater from running.

Studio

  • Put in an initial fix for situations where the username and domain are added to the mapsource in the iShareMaps.xml configuration file.
  • The "Seed Tilecache" options are now not shown for WMS tilecaches.
  • The OGC table list no longer remains disabled when selecting a different datasource.
  • Fixed some edge cases where the Map Editor would incorrectly interpret some legitimate content.

Data Share

  • Data Share synchronisation now uses the Workflow Timeout setting.

  • Fix situation where null values for columns in Data Sources meant that those columns were not present when output in GetData Data Source requests.

iShare Core

  • Fixed a problem which was causing OGC Layers from working due to case-sensitivity issues.
  • When performing an info-click on a map, a selection circle will be shown for a short time to allow the user to see what is included in the search.
  • iShare now correctly uses the MapPixelTolerance when performing and info-click search on a layer.
  • Ensured that any data output that uses the atJSONDatatable.xsl file correctly passes in the columns.

Web Services

  • GetData requests that return JSON should no longer produce invalid JSON if they have a number that doesn't match the JSON specifications.

Publisher

  • Stop 'AND' and 'OR' causing Publisher search results to return nothing.
  • Publisher should no longer return no results if the previous URL tag is NULL.
  • Publisher filters that use greater-than-or-equal-to should no longer cause an Invalid Filter error to be shown.
  • Publisher will now accept filters which include the words "and" and "or".
  • Publisher should no longer erroneously return a error reporting that the template isn't in the correct directory.