[Bugfix] JS config themes

[rldhont]

Fixing JS classes around map themes

Funded by Karum

[josemvm]

hi @rldhont i get this error An error occurred while loading this map. Some necessary resources may temporarily be unavailable. Please try again later. [Go back to the home page.](https://xxx.xxx.xxx/) when i activate de first map theme on qgis server 3.34, lwc 3.7.9-pre but not on qgis server 3.28

maybe related to this PR (?)

[rldhont]

hi @rldhont i get this error An error occurred while loading this map. Some necessary resources may temporarily be unavailable. Please try again later. [Go back to the home page.](https://xxx.xxx.xxx/) when i activate de first map theme on qgis server 3.34, lwc 3.7.9-pre but not on qgis server 3.28

maybe related to this PR (?)

When you've got this message, it means that one of the GetCapabilities requests (WMS, WFS, WMTS) or all has failed.

[Gustry]

@josemvm

i get this error

Please check your Javascript console, you will have some tips about what was wrong, in the "Console" and/or in the "Network" tab by checking which requests as failed.

[josemvm]

@rldhont

When you've got this message, it means that one of the GetCapabilities requests (WMS, WFS, WMTS) or all has failed.

in this case when i deactivate de first map theme the map loads with all layers and without problems

@Gustry this is what i can get in my javascript console:

[josemvm]

in the network tab everything looks good to me but i can provide an url if you want to investigate

thanks

[rldhont]

@Gustry I have apply #4565

[Gustry]

I'm not able to review too much this PR, but given the fact it fixes tests on QGIS 3.34, LGTM.

You will have some conflicts while backporting, at least on 3.7 I think.

I think it's a blocker for releasing 3.7 and 3.8 this PR.

[3liz-bot]

The backport to release_3_7 failed:

The process '/usr/bin/git' failed with exit code 1

stderr

error: could not apply 269a2dcd5... [Bugfix] JS: activateFirstMapTheme options config
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config advice.mergeConflict false"

stdout

Auto-merging assets/src/legacy/switcher-layers-actions.js
Auto-merging assets/src/modules/config/Options.js
CONFLICT (content): Merge conflict in assets/src/modules/config/Options.js
Auto-merging tests/js-units/node/config/options.test.js

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-release_3_7 release_3_7
# Navigate to the new working tree
cd .worktrees/backport-release_3_7
# Create a new branch
git switch --create backport-4514-to-release_3_7
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 269a2dcd572458bfcc9b7f2e825254f325c265f2,f9833ae079d7fd8d4a8f44815ac2f3141d2aa476,f345e3a8d26f87da80bdcbd73fa97cc58569c503,03f35fd8422f36f98342766b9e06dce4419d39ae,97cdaa30ded7a67b265f28e6b44e902ed919d586,ff9dfd1c6401d3977ef9a1ce1b96387987611d79
# Push it to GitHub
git push --set-upstream origin backport-4514-to-release_3_7
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-release_3_7

Then, create a pull request where the base branch is release_3_7 and the compare/head branch is backport-4514-to-release_3_7.