Global Colours Tailwind Conflict

[hopscotch]

I have an issue applying global colours and a conflict with Tailwind. If I add my global colours (with the palette activated) via the Cwicly UI and have Tailwind activated, I see options for my global colours of shaded and opacity variations within Tailwind which is brilliant. But selecting any of the colours or opacity variations, no colour is applied to the div and the wee preview box for the selected colour is empty. But if I select a Tailwind stock colour it applies with issue. What is the best practice; to add my custom colours via Tailwind config? Or the Cwicly UI? Am I missing a step?

[StrangeTech]

@hopscotch

But selecting any of the colours or opacity variations, no colour is applied to the div and the wee preview box for the selected colour is empty. But if I select a Tailwind stock colour it applies with issue.

I thought this was fixed in 1.4.0.1 by:

@Louis

• Fix: Cwicly global colours would not show the correct preview in the Gutenberg colour picker

But maybe it wasn’t.

[T-low]

Hi @hopscotch,

unless I’m completely mistaken, I see a space in your color name. I have reported that here:

Global color naming bug?

Hi there, I’m not sure if this is a bug, but the custom color name is applied as a class. I’m not certain if this is the default, but shouldn’t the variable be applied and the name is for better readability? Also, if it is intended that the name is applied as a class, shouldn’t it be forbidden to use spaces and non-class symbols? Or is there some purpose that I’m not aware of? [grafik] [grafik] Cheers Environment info WordPress version: 6.4.3 Cwicly Plugin version: 1.4.0.1

As of now, when a global color is added, the post needs to be saved & refreshed before the colors can be applied.

Cheers

[hopscotch]

@T-low fair play indeed it was the space in the ‘name’. I should have copped on to that but it was the end the day. Should it not pull the class name from the variable not the ‘name’? See my screenshot below. I assumed the ‘name’ was a like a nickname for simplicity. I now have it working.

@StrangeTech maybe its not there yet…

[hopscotch]

@T-low seems you had the same issue!

Global color naming bug?

Hi @Louis, thank you for the info. No inconvenience, I will name them accordingly Cheers

[T-low]

Hi @hopscotch,

yup, it took me a while to figure it out, since the documentation also specifies the use of the name for better readability.

Colour tab

But as @Louis mentioned in the bug report this might not be the case for Tailwind.

@Louis

In this case, it is expected behaviour that the name is used to define the colour in Tailwind. There are pros and cons for using either the name or the variable, but we did end up deciding on the name as it had more pros.

I will add a reply in the report that it would be useful to update the documentation on this part.

Cheers

[hopscotch]

@T-low I read the same thing. @Louis I know you said there maybe unforeseen complications with pulling the class name from the variable instead of the ‘name’. But most people would assume it would pull from the variable. Maybe it would make sense to revert to using the variable regardless?