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.

[Gaetanbrl]

The new TOC design looks completely broken. But perhaps it's just a deliberate return to old school design ?

[Gaetanbrl]

The new TOC design looks completely broken.

Not broken, this new design seems a voluntary enhancement.

See https://docs.mapstore.geosolutionsgroup.com/en/latest/user-guide/toc/ captures.

[landryb]

it's been announced ages ago and was the first hilight of https://github.com/geosolutions-it/MapStore2/releases/tag/v2024.01.00

[catmorales]

Background layers in WMTS are not printed. Is it the same for yours ? @landryb @Gaetanbrl

[landryb]

Background layers in WMTS are not printed. Is it the same for yours ? @landryb @Gaetanbrl

works on https://demo.georchestra.org/mapstore/#/ with the wmts from data.geopf.fr, both in the minimap preview and the pdf preview.

[catmorales]

Thank you @landryb ok it's a problem in our infra so, it's ok now.

[tdipisa]

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

Hi @catmorales did you try to clean the browser cache already? It seems a problem like this that should have been resolved by geosolutions-it/MapStore2#10310
If you can restore the new version in portail-test we can do a check to see if we also reproduce the issue.

[jusabatier]

Here I tried to upgrade, but have problems with header.

I set :

"header":{"height":"90","url":"/header/","legacy":true,"stylesheet":""}

In the localConfig.json file of the datadir, but when loading the url /mapstore/configs/localConfig.json, I get :

"header":{"height":"90","url":"/header/","legacy":"","stylesheet":""}

The legacy value is replaced with an empty one, and it's the same for other new values for what I tested.

Edit :

I finally found the problem with help from @landryb.
If values are missing from default.properties, they are overrided with blank values in the delivered localConfig.json

[catmorales]

Hi @catmorales did you try to clean the browser cache already? It seems a problem like this that should have been resolved by geosolutions-it/MapStore2#10310

It-s OK, the problem has been fixed with the help of Jdev with the use of a new style css file (completed with nw values ) here in the localConfig.json :
"stylesheetUri": "https://public.sig.rennesmetropole.fr/ressources/app/mapstore/theme_mapstore_portail/thememapstore_rm.css",
the result is: