Archived topic
Header Color Bug
10 replies · Started by Eddy on April 29, 2020
Hi,
Please watch this video here: https://www.loom.com/share/10027057dbf34707b2af4d9469671483
Please let me know if you need to login.
Thanks.
Eddy
Hi there,
Can you check your setting under Customizer > Colors > Header > Background?
Let me know :)
Hi,
I showed this in the video. Did you watch the video?
Hi Eddy,
I'm a GP user too and just took a quick look at this.
When inspecting the code I see that the <header> element has a CSS gradient applied that appears to be overwriting the background-color. There is also a typo in the first and last lines. When I deselect these in Dev Tools the header displays correctly for me.
header {
bbackground-color: #fff;
background-image: -webkit-linear-gradient(#fff 0%,#f8f8f8 50%,#f2f2f2 100%);
background-image: linear-gradient(#fff 0%,#f8f8f8 50%,#f2f2f2 100%);
border-bottom: 1px solid #ebebeb;
font-weight: 400;
padding: 20px 0 10px 0;
isplay: none
}
I'm unable to tell where or how this CSS was added, but it appears to be what's causing the problem.
Hope this helps!
Okay, thanks for identifying the issue. So how do we go about fixing it?
Is there some css code that needs to be added and if so what is it?
Is this some theme bug? Because i haven't added a css code to make that change. I'm just using the customizer as shown in the video.
Please advise as to the fix.
Thanks.
This isn't a bug.
That code is not added by GP.
Can you disable all plugins except GP Premium to test?
Make sure to activate the parent theme if you are using a child theme.
Thanks for the tip. It was wp rocket optimize css issue. My developer had put some css stuff there based on my old theme. Once I disabled it and removed the code, the issue was fixed. Thanks for your help!
No problem :)
It would be a good idea to always go through the process of disabling plugins when you encounter a weird issue like this.
Thanks. The last couple of issues I have reported had nothing to do with the plugins. So I assumed this was another one of them. But you're right I should always eliminate plugin issues first. Thanks again..
No problem :)