@slango
No, we are not deprecating any of the CSS code at all within the theme. And can you provide us any screenshot on it to better understand?
Thanks.
Thread Starter
slangs
(@slango)
Please READ THE RELEASE NOTES of the latest version of ColorMag.
* Tweak – Deprecate Custom CSS customize option provided via theme
Hi @slango,
We used to have a Custom CSS option provided directly from the ColorMag as WordPress doesn’t have it by default. However, later WordPress has added the Additional CSS option in the customize (in version 4.7). Then, we transferred the styles from the theme’s options if the user has added any to the WordPress core option.
In this process, the user’s with an older and newer version of WordPress wouldn’t have any problem.
Now, since the version of WordPress has been recently updated from 4.7 to 5.0 (3 major version releases in between), we deprecated the older option according to WordPress guideline. So, if you’re using WordPress version prior to 4.7, everything should be fine.
I hope you understand.
Thanks.
Thread Starter
slangs
(@slango)
Thank you, and I already understand all that, but *exactly* how are you defining and implementing “deprecate”?
Does that mean the feature is “frowned upon” or have you removed it entirely from the latest versions of the ColorMag theme.
Or maybe I am misunderstanding, as today I add CSS using the “Customize” option, as illustrated on this webpage as “Method 1: Use the WordPress Customizer”
https://wplift.com/how-to-add-custom-css-to-wordpress
This shows up as an “Additional CSS’ section of the theme – so that is part of WP now and is going to stay as-is?
-
This reply was modified 6 years, 2 months ago by
slangs.