Open MortenHofft opened 2 years ago
Thanks for finding this issue. This is strange - that it works within the explorer page but not otherwise.
It is also true for simpler query params like this: https://val.vtecostudies.org/gbif-explorer/?taxonKey=2431549&view=MAP&year=1990
some links works - others not. it is odd. the simplest I could come up with is fails: https://val.vtecostudies.org/gbif-explorer/?year=1900 (year) works: https://val.vtecostudies.org/gbif-explorer/?years=1900 (years)
Perhaps some code in your backend looks for the parameter year
?
I think your hunch is correct. These also fail:
https://val.vtecostudies.org/gbif-explorer/?day=2 https://val.vtecostudies.org/gbif-explorer/?minute=59 https://val.vtecostudies.org/gbif-explorer/?second=45
While these succeed:
https://val.vtecostudies.org/gbif-explorer/?day=Tuesday https://val.vtecostudies.org/gbif-explorer/?month=9
This suggests something is parsing query params and filtering them for validity. I asked our WP consultant. They asked what I'm doing that could be causing this. I've searched my code for those terms and there are none other than the GBIF data-widget config values. I suspect there is default WP apache config or REST API config that's causing this.
This is a nuisance. Is this bug disabling critical features of the GBIF data explorer?
The explorer works fine as far as I can see. But no one can link to a filter that includes a year filter.
I think this article explains the problem.
E.g. https://val.vtecostudies.org/gbif-explorer/?view=MAP&year=1900%2C1920 is a valid url that can be composed when using the filters, but when following the link it will redirect to a 404