Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 240 Next »

The download links for this content are now generated automatically to allow for the rapid release of these updates without having to come back and manually update this page.

The details and direct links to the releases are available at:

Additionally, there is a newer download site available that provides links to the latest stable releases. It is hosted in the cloud to provide for faster downloads.

2.6.6

Release Pending

Enhancements

  • activateEntity flag added to ToC panel

    • a flag when set to true will change the active entity, to the one associated with the toc entry, when the entry is turned on

  • Update to caching settings

    • The weave.cache.default flag will now disable caching for data definitions as well as search results

  • Tile update

    • When generating a single map image from a tiled map engine some optimisation have been made to try and improve performance

  • Edit panel update

    • It is now possible to configure the edit combo box width in the spatial edit panel, by setting comboWidth and comboListWidth in the panel config

  • New storage commands

    • There is now a flush option available for the storage and ustorage commands, which ensure that any outstanding writes are written to the storage provider

Fixes

  • PostGIS compatibility fix

    • The GeoTools 13.x PostGIS driver has been updated to fix compatibility issues with newer versions of PostGIS

  • EPSG:7899 support on client

    • A projection definition for VicGrid GDA2020 has been added to the client

  • Possible XSS fixed

    • A possible, but very unlikely, vector for an XSS issue we removed. An error response contained the id of the request that generated the error. While it’s not clear how or if this could be used as a vulnerability but we’re removing all instances of client request parameters being returned in responses to try and minimise any possibility of this being used

  • Runtime property parser fix

    • When parsing a runtime property that represents a file variations in the way the operating system and Java version present the “path” can result in the value not being interpreted as a path correctly. i.e. sometime the path is given as file://<path> and sometimes file:<path>

  • Client IP

    • If the server was behind a reverse proxy Weave might not guess the correct IP address of the client

  • Default style

    • The client would not be able to determine the default style to choose for a layer in some circumstances

  • No labels