Problems with 2024.02.00-RC1-geOrchestra

[catmorales]

Describe the bug
Issue to report all the problems detected with the 2024.02.00-RC1-geOrchestra release

[catmorales]

Hello @tdipisa .
We are unable to deploy the release candidate in our environment.
We're using your docker image.
As a reminder, we have :

• the georchestra datadir containing the configuration files (localConfig.json, config.json, new.json, pluginsConfig.json) located in /configs
• the dynamic extensions directory, containing files located in /configs and /extensions directories

I've modified the localConfig.json file as described in your documentation.
Mapstore seems to load correctly, as do the extensions, but the map is blank (no header, no map). By modifying the config.json file, I don't see any improvement.
In the browser console, I get a 404 error on https://portail-test.sig.rennesmetropole.fr/mapstore/dist/81c145986683c200.js
Please tell me what's wrong. I can e-mail you the localConfig.json and config.json files if required.

You can test it logging with your account "tdipisa" and changing your host (because it is a test version not in production)
10.2.10.34 portail-test.sig.rennesmetropole.fr

[catmorales]

@landryb and @Gaetanbrl
Have you ever experienced this problem?

[landryb]

i didnt have issues with 2024.02 everywhere i deployed it in testing, but that was via debian packages/wars, not docker images. And since we cant access your test platform we cant really help...

[catmorales]

The error 500 on pdf/info.json was fixed by using this yaml : https://github.com/georchestra/datadir/blob/master/mapstore/printing/config.yaml

But for the localConfig.json I did a lot of customisation and don't want to reinitialise everything but perhaps, I will need to do it :/

[landryb]

The error 500 on pdf/info.json was fixed by using this yaml : https://github.com/georchestra/datadir/blob/master/mapstore/printing/config.yaml

yes, i had seen it and documented it on georchestra/datadir#428 (comment)

But for the localConfig.json I did a lot of customisation and don't want to reinitialise everything but perhaps, I will need to do it :/

you have to update localConfig.json (cf https://github.com/georchestra/datadir/pull/428/files) and follow the migration notes, that happens at each update... cf georchestra/datadir#428 (comment)

georchestra/ansible@23c9f7f is the main diff i applied on the ansible playbook part.

[catmorales]

Thank you @landryb
Yes I did it and modify everything referenced in
Migration from 2023.02.02 to 2024.01.00
Migration from 2024.01.00 to 2024.01.02
Migration from 2024.01.02 to 2024.02.00
but I had a lot of problems.

So this morning, I reinitialized localConfig.json and config.json and /printing using the update in the datadir georchestra made by dsuren1
. It's better the map is visible , the info.json problem is fixed with this config.yaml but I lost all my customisations. I will try to add them one by one and test.
First I think that the theme used and applied on our professionnel portal is now unadapted @pierrejego

[pierrejego]

We have to take a look, but normally only colors had been changed for Mapstore. Perhaps some entries are missing in the new CSS version. I will make some test here to see if i can reproduce.

[pierrejego]

The look and feel has changed between both version

Some fields were added to variable.less file (

mapstore2-georchestra/themes/default/variables.less

Line 62 in fe581a2

@ms-selected-color: rgba(@ms-primary, 0.4);

), we will make some test Monday to see if migration is needed in extended georchestra mapstore theme.