@digikraft Are you sure the colors are available on the corresponding page/post/template? If yes, we need more information on how to reproduce the issue.
Hi, I upgraded to 1.5.7 and the problem is still there, I have changed the css loading methods, regenerated the css, updated the inputs, put the variable back in the constructor and it is still not solved.
Hello, thank you for replying.
Yes, is that the dynamic colors work well, but the problem occurs when they are used within the loops, I hope you can solve it quickly, greetings.
Unfortunately, I can’t tell you more than that the task is still on the list - along with many others, so we have to prioritize. I’m pretty sure that if this task was easy to fix, it would have happened long ago.
I also ran into this problem when wanting to create an overlay using either an ACF colour field with {acf_my_field} or {echo:my_function()}.
I discovered that it occurs because the Overlay/Gradient colour control doesn’t seem to pull in dynamic data.
As a hack solution , I added the line below line (taken from another control that does use it and modified to access the correct array value) in themes/bricks/includes/assets.php:1457
Yes I agree, and as such I’m not modifying it for my solution.
I was hoping it would point the way to a solution that you guys would incorporate into a future release as currently dynamic data in the color control under the overlay doesn’t work.
Until that happens I also found a work-around for background color by using the Attribute setting and an inline css style with “style” and then adding the following CSS rule:
root:before{
background-color: inherit;
}
This way the dynamic data from a custom field (in my case ACF) can be used in the element to set the background overlay through an inherited background color on the element that is parent to the pseudo element.