-
Notifications
You must be signed in to change notification settings - Fork 26
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
EasyTheming plugin not loaded on home and admin page #727
Comments
In addition, if we go to It seems requried to load Viewer first to display custom CSS. |
After a short compare with https://github.com/georchestra/mapstore2-georchestra/blob/master/js/plugins/Header.jsx#L41C9-L41C13
It could be interesting to change the We need to test... |
I think I've found the right configuration. Just search "Header"' reference and complete parent section with Easytheming to activate this extension :
In conclusion, activate the Tests https://gis.jdev.fr/mapstore/#/home
|
Thank you @Gaetanbrl OK I will try |
@Gaetanbrl To complete that in all sections we need to add "Easytheming", in all the sections: Could be the the "common" section used for all ? |
It works for almost everything !!! Thank you @Gaetanbrl The case where it don't work is this one (creating a new context): It's not a problem, but I imagine it will have to be passed on to Geosolutions. |
Il est bien positionné ici:
|
Il faut voir s'il ne manque pas une variable au thème par défaut. Je vais regarder avec @Agath21 |
Describe the bug
We use the plugin to customise our mapstore. It works very well for the viewer. But there's a problem with home and admin pages: the theme doesn't apply. The default colour is pink. After checking, custom stylesheet and variables are not loaded in these pages.
Do I need to change the plugin configuration?
To Reproduce
Steps to reproduce the behavior:
1 - Go to mapstore/#
2 - Change to mapstore/#/home
3 - Empty the cache
Expected behavior
The custom theme is applied to the home and admin pages
Screenshots
Desktop (please complete the following information):
Chrome, firefox
The text was updated successfully, but these errors were encountered: