You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**It might look similar, but it's not. The commas (encoded as %2C) got removed and now the WMS service gets a request for 4 layers but with only 1 style requested, which breaks the functionality completely. **
The text was updated successfully, but these errors were encountered:
jacobwod
changed the title
The pairs of "layer/style" are not send correctly anymore
The pairs of "layer/style" are not sent correctly anymore
Dec 1, 2021
This might be a difference between QGIS server and Geoserver, I get the opposite problem where if "empty" styles are sent we get incorrect responses, as I described in #841
I had problems when STYLES=, was sent to the WMS server. Do you get a correct response even when all styles are empty? @jacobwod
Do you get a correct response even when all styles are empty? @jacobwod
I do but it is not relevant as a possible (and common) use case is to have a bunch of layers, use default styles (e.g. empty string) on most of them, but override one layer's style with a specific, named style.
Prior to #884 we created a correct URL with pairs of layer and corresponding styles like this:
Hajk/new-client/src/plugins/LayerSwitcher/components/LayerGroupItem.js
Line 380 in a81e942
In #884 that was changed to remove the empty styles:
Hajk/new-client/src/plugins/LayerSwitcher/components/LayerGroupItem.js
Line 381 in 65ca528
However, this breaks the custom style functionality completetly, as we don't send correct parings of
LAYERS
andSTYLES
.Prior the change the following parameters were send with the
GetMap
request (I only show the relevant parts):After the change, we get this however:
**It might look similar, but it's not. The commas (encoded as %2C) got removed and now the WMS service gets a request for 4 layers but with only 1 style requested, which breaks the functionality completely. **
The text was updated successfully, but these errors were encountered: