Review Block button colors not working

[Leo]

Hi there,

Since yesterday’s update I’m having issues with the styling of the review block. If I use a blue button with white text, it automatically gets changed back to the default theme body color.
I can currently only change the text button color by going to customizor -> colors -> body and then edit the “text color”.

How can I quickly fix this or is it possible that you guys update it quickly?

Thanks again for this amazing plugin 🙂

[Alexis]

HI @Triton ! We’ve tried recreating your issue on our end. So far, it only comes up when trying to edit an old review block within a reusable block. Have you tried inserting a new review block to check if it’s also affected? If the new one is not, you may try duplicating the old one.

[Leo]

New review blocks are also affected. I’m not using reusable blocks either….

I tried creating a new review block and duplicating the old one, I keep getting the same results…

edit: If I need to redo all of the review blocks, that would mean I’d be busy for the next month as well.. I’ve got 100’s on one website alone…

• This reply was modified 2 weeks, 1 day ago by  Leo.

[Leo]

If i check code on the button, I see it’s now to “inherit”. It was never inherit.. Please update so I can use it again..
https://i.imgur.com/8JDNduU.png

• This reply was modified 2 weeks ago by  Leo.

View post on imgur.com

View post on imgur.com

[Alexis]

Thank you for providing more details, @Triton ! We’ve been able to recreate the issue with the button text color on our end (by setting the button text color to #ffffff). We’ll be including a fix for it on the next update, and we’ll ensure that “inherit” as a color setting will only come up when the button text color setting for the review block is cleared.

However, we’re not yet able to find a situation where the color of the button is set to #f63d3d no matter what color the user chooses. We’ll let you know as soon as we come across such a situation.

[Leo]

Awesome. Thank you for the update. I’ll wait for the next update 🙂

[Leo]

For anyone running into the same problem, I’ve fixed it by downgrading to version 2.4.3