@adairk, to use Jetpack, you need to turn on the Custom CSS option by going to Jetpack → Settings. Once you activate Custom CSS there will be an entry under Appearance → Edit CSS where you enter in your CSS rules.
Thanks CrouchingBruin,
I found what you were pointing out but that stuff is for you guys who know what you’re doing.
Nobita says he will have a fix in a few days so I’ll put up with that other Theme I now have to use on 7 of my 14 sites.
I’m wondering how the other people here have been doing as I haven’t seen them comment lately?
BUG fixed version 1.433 of raindrops.
Please update
Thank you.
Thanks but the update made no change for me Nobita.
Was the update supposed to bring back the old CSS settings? I would consider that highly unlikely. My guess is that the update just prevents the CSS settings from being wiped out in future updates.
Another person reply with Not Fixed
https://wordpress.org/support/topic/raindrops-customizer-issue/
I will continue to confirm the problem, if you needs.
After this, you give me a reply to the above-mentioned link
Note:
This bug has occurred in the version 1.426
https://github.com/tenman/raindrops/commit/22e9622af113a59c95fcf218066d088a51d820c3#diff-ddf14f11896191d5e1fa5d41eefd36d5R548
This error, your customization has been lost
1.433 remove delete_option()
This change is hotfix, by this change, now that has a low probability bug.(when switch child theme[has custom style type] to parent theme , child custom style type not removed)
The purpose of 1.432 is, was that to allow the switching of the option and theme_mod.
This bug is, because it was thought to be generated from the code of switching part, but took the time to work,
switch example
functions.php top
$raindrops_setting_type = 'theme_mod';
value theme_mod or option
-
This reply was modified 9 years, 6 months ago by
nobita.