Hello,
Just tested both and they seem fine. Can you share a link where this is happening, please?
Hello, thank you for your reply.
Of course, you can see an example of the issue here: https://www.unitest.app/blog/
The background color for the whole site is stuck to #f7f7f7 whereas it should be #ffffff.
I don’t really understand why this issue appears only with the colors of the “General” section of the Colors menu in the Customizer.
In particular it won’t allow me to save the changes made to the general background color and general body text color. Usually in the Customizer, as soon as an edit is detected, the “Publish” button on the top lights up in blue and allows you to save the changes, however only in this case it stays grey, as if no edit was made.
Everything works fine with the rest of the sections though (links, titles, etc.).
In case there is no fix, is there any chance you can provide the code to edit those two elements in the custom CSS section of the Customizer?
Thanks a lot
Try a hard refresh please while you have the Customizer open by pressing CTRL F5, or cmd shift R on Macs.
Thank you for your suggestion, but unfortunately a hard refresh did not change anything.
Can you please provide the CSS element name for the general background color and for the general body text color so that I can try to fix this with customized CSS?
Thanks
Hi @marco-v,
I did some inspections on your blog page. And, if, I got your query correctly, you’d add this CSS code to your site’s Additional CSS:
.content-inner,
.comment-respond,
.post-navigation .nav-links {
background-color: transparent;
}
.posts-layout .entry-post {
color: #ff0000
}
Thank you for trying to help, unfortunately this CSS does not seem to replace the settings that are not working anymore.
I see that this problem is common to other users (e.g. see this thread), can you please confirm that these issues (i.e. background color, body text color) will be fixed in the next version?
Hi @marco-v,
Thank you for getting back!
I have added this to our bug tracker. Hopefully our development team can include a fix for this in future version updates of the theme.
