Version 5.6.30

Version No5.6.30
Release Date
 
About this Release

Patch release with minor enhancements and fixes

Modules affected

Installers, iShare Core, iShare GIS, iShare Maps, My House, My Nearest, iShare 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

  • Astun 3rd Party Installer now installs the SUDS library when you install Python - required for Python to communicate with SOAP Web Services.

iShare Studio

  • There is a new DeleteFiles script which can be used through a Workflow Program Task to clear out directories that can fill up with temporary files over time. 
  • Fixed issues with Studio failing to connect to PostgreSQL versions 10 and above.
  • Correctly set type of Layer's SQL after editing data definition.
  • Corrected the tab order of all the Layer forms in Studio.
  • Ensured that simple manually entered SQL is correctly wrapped with quotes.
  • Studio now should no longer throw an unhandled exception if the Data Share database connection string is in the wrong format.
  • Removed the MULTILINE option from Force Geometry in the Spatial Data Transformation Workflow.
  • The SLD Style Editor:
    • now handles multi-geometries correctly.
    • is now being correctly updated on first load and after the Advanced editor is changed.
    • icons on the Advanced tab toolbar have been updated.
    • should no longer incorrectly switch the order of the symbolizers.
    • should load quicker as the time to load symbols from the cache into the SLD Style Editor on open has been significantly cut. This will be more noticeable the more symbols listed in the .map file (directly or through inclusion in a SYMBOLSET).
    • now uses the correct stroke control for solid colour fills.
    • has various other fixes & improvements.
  • Changing the display name of a Datasource field should no longer cause the layer to stop working in My House.
  • Users can now order the BaseMaps in Studio.
  • Fixed problem with listing some types of MapServer Layers in Studio when editing or creating Classic Layers.
  • Added missing icons to the caption bar of various forms and dialogs.

iShare Core

  • The VIEWPARAMS parameter for GetOWS requests has added new capabilities (and altered the way it works).

iShare GIS

  • Info-clicks now return fields with spaces in their name correctly.

  • Fixed a Feature Server configuration file issue regarding the schema not being set correctly.
  • The Print to PDF should now show any recent changes to layers upon the dialog loading without having to refresh iShare GIS.
  • The OmniSearch now correctly searches local metadata for the layer.
  • Using ampersands in passwords should no longer cause problems with iShare configuration files

iShare Maps

  • The Map Categories panel should no longer obstruct the Address Search when going back from the last page of results.
  • Ensure the Clear search, Previous & Next buttons remain in the same place on the Search Results to prevent clicking Clear search by mistake.

My House / My Nearest

  • iShare Maps tabs not having a Display Name will now render correctly.
  • The generic "No results found..." dialog title and OK button text is now correctly drawn from the languages file.

Web Services

  • Updated the Metadata web service so that it now returns cached metadata in the event that the CSW server is not available.
  • Fixed problem with aggregate Thematic layers not being properly displayed in prints.
  • Fixed issue where the Layer is not returning results to map queries when the Layer uses a SQL query formatted in certain ways.
  • Using ampersands in passwords should no longer cause problems with iShare configuration files.