Hello, I just updated the theme to fix one problem and it created 2 more! The button in my call to action vanished. I made no changes other than updating the theme on the server. Also, my widget 1 area in the footer has reset to nothing. What's going on?
I have had to hack together a quick fix for this because my client is freaking out. I added this to my custom CSS panel, but I would appreciate if you could still examine the issue and offer a solid fix:
I'm using David's code, as shown, in my child theme's stylesheet, but it's not working.
[UPDATE Thursday, August 7, 2014 at 5:58:51 PM
OKAY, so... I added this to the themes's custom CSS panel (although I much prefer keeping all the custom CSS in the child theme stylesheet instead, but that wasn't working,) - and now it works.
a.nectar-button.accent-color {
visibility: visible !important;
}
I'd really like to know why some things in the child theme stylesheet work, while this fix didn't work there.
It's working now. I guess the only real issue at this time is that I'd rather keep all my custom css in my own child theme's stylesheet rather than have to use the theme's "custom.css"
I don't quite understand how the theme's custom.css works. When a theme update comes along, I suppose it doesn't ship with a custom.css, thus not over-writing any existing custom.css? I'd much rather not use it at all, and instead know that all my customizations are in my own child-theme stylesheet.
if you're referring to the dynamic-combined.css file, that's not meant to be written to directly by you - its contents are added dynamically from your theme options panel. Custom css does indeed belong in either a child theme style.css or the custom css box. If certain rules are not working in a child theme stylesheet it's probably because they need some more specificity since that stylesheet is loaded before the custom css box would. If you have any rules you can share that aren't working I'd be glad to help :)
Hello, I just updated the theme to fix one problem and it created 2 more! The button in my call to action vanished. I made no changes other than updating the theme on the server. Also, my widget 1 area in the footer has reset to nothing. What's going on?
Hello,
I have had to hack together a quick fix for this because my client is freaking out. I added this to my custom CSS panel, but I would appreciate if you could still examine the issue and offer a solid fix:
/* CALL TO ACTION BUTTON QUICK FIX */
#call-to-action .container a {
background: #0A65B0 !important;
}
.nectar-button:not([data-color-override="false"]), .nectar-button:not([data-hover-color-override="false"]) {
visibility: visible !important;
}
Hey David!
Thanks for shedding light on this. We will take a look.
Best,
-T
ThemeNectar Support Team
Thank you, David.
I just now noticed this problem as well. I'm off to implement your quick fix now. I'll report back my results.
I'm using David's code, as shown, in my child theme's stylesheet, but it's not working.
[UPDATE Thursday, August 7, 2014 at 5:58:51 PM
OKAY, so... I added this to the themes's custom CSS panel (although I much prefer keeping all the custom CSS in the child theme stylesheet instead, but that wasn't working,) - and now it works.
a.nectar-button.accent-color {
visibility: visible !important;
}
I'd really like to know why some things in the child theme stylesheet work, while this fix didn't work there.
Does anybody know?
Thank you
Hey Mitch! Is there anyway you can share the page where this isn't working?
Hi,
It's working now. I guess the only real issue at this time is that I'd rather keep all my custom css in my own child theme's stylesheet rather than have to use the theme's "custom.css"
The website is http://greenscoresolutions.com
I don't quite understand how the theme's custom.css works. When a theme update comes along, I suppose it doesn't ship with a custom.css, thus not over-writing any existing custom.css? I'd much rather not use it at all, and instead know that all my customizations are in my own child-theme stylesheet.
Hey Mitch,
if you're referring to the dynamic-combined.css file, that's not meant to be written to directly by you - its contents are added dynamically from your theme options panel. Custom css does indeed belong in either a child theme style.css or the custom css box. If certain rules are not working in a child theme stylesheet it's probably because they need some more specificity since that stylesheet is loaded before the custom css box would. If you have any rules you can share that aren't working I'd be glad to help :)