Hi Kathryn,
Thanks for the access data!
I found the problem: the variable values from the variable manager were overwritten within the color palette because the raw value was assigned a hex value (#ffffff). To solve the problem, I edited each affected color in the color palette, removed the hex value and saved it.
In retrospect, I can’t say precisely how this happened - it may have been due to problems with the color palette in a previous version, which we have already fixed (so I updated to Bricks 1.10.1), or because of how you added the colors to the color palette.
There are two ways to use color variables within the color palette.
-
If you want to add an “externally defined” variable (in the variable manager, an external stylesheet, or a plugin) to the color palette, you only have to enter the variable name, e.g.
var(--fs-color-accent-200), in the RAW field and click on save. If you want to change the variable’s value, you do this in the place where it was defined. In your case, the variable manager. -
Alternatively, you can also create color variables within the palette without the variable manager, e.g., by choosing a hex value, entering a variable name in the RAW field, and clicking save. This assigns a value to the variable directly within the palette. If you want to change this, switch to “edit mode,” change the value, and save the color.
Best regards,
timmse