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
Currently we have a 1:1 relationship, as described in title.
The Admin UI does not allow to do anything that'd allow many maps to have the same documents, either.
But this can be fixed by copy-pasting the relevant portions of layerswitcher and documenthandler configs between map configs.
This works well but there seem to be one issue to resolve: DocumentHandler can contain links that are supposed to change visibility of layers. This is referred to as maplink functionality. The problem with its current implementation is that it seems to be tightly coupled to a specific map config in order to work: the m parameter must be present in the URL, else it will not work.
I'd like to propose a change of this behaviour as it's reasonable to assume that we never want to change the current map when clicking such a link. There's no reason to this tight coupling as far as I can see.
The text was updated successfully, but these errors were encountered:
OK, I've figured out what's wrong. The current implementation requires all layers specified in the "show layers array" to actually exist in the map. Otherwise, OpenLayers fails silently and no layers visibility's change. This is a bit problematic, so I think I'll add a check and perhaps display a warning (in the console) but I'll let the existing layers to actually be made visible.
Currently we have a 1:1 relationship, as described in title.
The Admin UI does not allow to do anything that'd allow many maps to have the same documents, either.
But this can be fixed by copy-pasting the relevant portions of
layerswitcher
anddocumenthandler
configs between map configs.This works well but there seem to be one issue to resolve: DocumentHandler can contain links that are supposed to change visibility of layers. This is referred to as
maplink
functionality. The problem with its current implementation is that it seems to be tightly coupled to a specific map config in order to work: them
parameter must be present in the URL, else it will not work.I'd like to propose a change of this behaviour as it's reasonable to assume that we never want to change the current map when clicking such a link. There's no reason to this tight coupling as far as I can see.
The text was updated successfully, but these errors were encountered: