Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Context Export] Unabble to export map configuration in context manager since 2023.02.RCx #679

Closed
rgoffinet opened this issue Dec 6, 2023 · 3 comments · Fixed by geosolutions-it/MapStore2#9896, #692 or #694
Assignees
Labels
Accepted bug Something isn't working Contract #4

Comments

@rgoffinet
Copy link

Describe the bug
Since the deployment of 2023.02.00-RC*-geOrchestra releases, we can no longer save map configuration in context manager, only the 'export context' option is now available.

To Reproduce

  1. As administrator, create a new context or edit the configuration of an old context
  2. Access page 2 of context configuration
  3. Click on the options icon and select export
  4. The 'export map' options is overlayed by the 'export context' option and we can't save our map configuration in a json or wmc file.

Expected behavior
Beeing able to export map configuration while configuring a context as it was possible in previous versions of MS2-geOrchestra.

Screenshots
MapExport_202302RC_issue

Desktop :

  • Browser : firefox 102.14 (32bits) ; chrome 116.0.5845 (64 bits) ; Edge 115.0.1901 (64 bits)
  • MapStore : 2023.02 RC1, RC2 & RC3

Additional context

@Gaetanbrl
Copy link
Contributor

Gaetanbrl commented Dec 6, 2023

I complete this issue.
After some test, too many components are loaded :

  1. Create a new contexte
    https://portail-test.sig.rennesmetropole.fr/mapstore/#/context-creator/new

  2. open browser web console and search export-panel class to find 3 panels :

image

This behavior is only reported from contexte editor map.

I reproduce the same for #DRAGDROP_IMPORT_ZONE id :

image

@catmorales
Copy link
Collaborator

catmorales commented Dec 6, 2023

@tdipisa, thank you to check this.
Probably linked to #584

@tdipisa tdipisa added this to the VSR MS4 - Phase 2 milestone Jan 12, 2024
@tdipisa tdipisa added bug Something isn't working investigation Contract #4 labels Jan 12, 2024
@dsuren1
Copy link
Collaborator

dsuren1 commented Jan 16, 2024

The issue happens because the control keys on both toggle operations are identical. The fix will be provided on MS and backported to stable

dsuren1 added a commit to dsuren1/mapstore2-georchestra that referenced this issue Jan 23, 2024
@dsuren1 dsuren1 linked a pull request Jan 23, 2024 that will close this issue
tdipisa added a commit that referenced this issue Jan 23, 2024
#679: Updated MS submodule to latest stable
@ElenaGallo ElenaGallo self-assigned this Jan 30, 2024
dsuren1 added a commit to dsuren1/mapstore2-georchestra that referenced this issue Jan 30, 2024
tdipisa pushed a commit that referenced this issue Feb 2, 2024
#694)

* Update MS submodule to include Phase IV and #679

* Revert config

* Update with fix #681
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment