Closed mhidas closed 10 years ago
@anguss00 @jkburges Make sure to add it to "why we suffer if the portal is stateful".
OK, what looks like happened is at 11:30am yesterday, a wms scan was started for IMOS Geoserver (IMOS Namespace) in portal admin. This server hadn't been scanned since February and so it added a whole bunch of layers added since then to the database. Unfortunately we haven't been using that server for our layers, we've been using geoserver-123.aodn.org.au and so the new scan created a whole bunch of duplicate layer records for geoserver-123.aodn.org.au
This caused findLayerAsJson to find the newly added layers without filters configured instead of the previously configured ones due to a wildcarded server uri match which matched both servers (using the server uri sourced from the metadata records).
I've deleted the Geoserver (IMOS Namespace) server and all its layers so this shouldn't happen again and the problem reported above has been resolved.
Good job!
@jonescc Please update https://github.com/aodn/internal_discussions/issues/37 with the amount of time you've spent on that.
Steps to reproduce
On the production Portal, in step 1 select any of the following layers (for example):
What happens
In step 2, the map looks fine, but in the Subset tab all we get is "Filtering of this layer is not available at this time." In step 3: "No direct access to data available currently."
What should happen
Should get filters and download options.
Note
At the same time there is at least one layer (SOOP Underway CO2 Measurements Research Group) for which both filters and download options are working fine.