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
Geoserver 2.19.x fixed a wrong behaviour where style names isnide workspace-specific GetCapabilities reponse were returned with the workspace prefix.
MapStores Styled editor relied on this prefix for its functionalities, which now are broken with Geoserver 2.19.x.
...
…e the style names returned by GetCapabilities (#7423)
* replace get capabilities request with GeoServer rest api to get information about styles
* get missing styles information from get capabilities
* store the current default style name
* remove restriction on workspace for editing
…ce prefix inside the style names returned by GetCapabilities (geosolutions-it#7423)
* replace get capabilities request with GeoServer rest api to get information about styles
* get missing styles information from get capabilities
* store the current default style name
* remove restriction on workspace for editing
…e the style names returned by GetCapabilities (#7423) (#7447)
* replace get capabilities request with GeoServer rest api to get information about styles
* get missing styles information from get capabilities
* store the current default style name
* remove restriction on workspace for editing
…de the style names returned by GetCapabilities (#7423)
* replace get capabilities request with GeoServer rest api to get information about styles
* get missing styles information from get capabilities
* store the current default style name
* remove restriction on workspace for editing
Description
see GeoNode/geonode-mapstore-client#519
How to reproduce
Expected Result
Current Result
style included in a specific workspace cannot be edited or deleted because mapstore is not able to build the correct url due to latest fix
Not browser related
Browser info
(use this site: https://www.whatsmybrowser.org/ for non expert users)Other useful information
The text was updated successfully, but these errors were encountered: