We are using a custom global color scheme (site-wide), and we're now starting to roll out optional themes that can be used for individual spaces.
The custom themes rely on the global color scheme, but observed the following odd (and as far as we could find, undocumented) behavior:
Whenever you change a space's theme, that space's color scheme automatically changes to the (space-level) "custom" scheme. This space-level custom color scheme inherits Confluence's default colors, not our global colors, so this produces undesired results.
To be clear, this happens with any theme change, not matter if its from global to space-specific theme or from space-specific to global theme.
How can we prevent Confluence from automatically switching to a space-level custom color scheme?
We are using Confluence Server 7.15.1
---
To reproduce:
- Have at least 2 themes installed
- Go to any space's "Look and Feel" settings, and ensure that it is set to both the "global theme" and the "global color scheme".
- Change that space's theme to a different one.
- Go to that space's color scheme settings: the scheme is now set to "custom".
- Change the color scheme back to "global", and go back to change the theme to "global" as well.
- The color scheme has been set to "custom" once again.
