Custom CSS now in WordPress
The Custom CSS feature in Jetpack is now integrated in the new Customizer-based CSS editor introduced in WordPress 4.7.
Jetpack’s Custom CSS was very useful for making small (or more significant) changes to your site’s CSS without needing to modify your theme files or create a custom child theme. With WordPress 4.7 introducing the Additional CSS feature, we wanted to make sure that people previously using Jetpack’s Custom CSS can still use the edits they’ve made in the past and use this new WordPress CSS editor seamlessly in the future.
Other improvements
We’ve also shipped a number of other enhancements and bug fixes in this release. A few highlights include:
- Improved compatibility with the
wp-missed-scheduleplugin. - Fixed a bug that would create an infinite loop when removing the featured tag from the tag list.
- Fixed an issue where WordPress help tabs were being hidden.
- Improved the dashboard page to work better when there is no backup data yet.
- Improved overall performance by clearing out unneeded scheduled jobs.
Full changelog and thanks
If you’d like to see the full list of the updates and changes to this version of Jetpack, you can check the full changelog here.
We hope you’ll love the new Jetpack features and improvements! Install it on your site or upgrade your current version today and let us know what you think. As always, your feedback is extremely important to us and you can send it directly through our Support contact form.
A special thank you to the contributors to this release – thanks for helping make Jetpack better:
Benyamin Shoham, Brandon Kraft, Daniel Walmsley, Derek Smart, Elio Rivero, Enej Bajgoric, Eric Binnion, George Stephanis, Igor Zinovyev, Jeremy Herve, Rich Collier, Sam Hotchkiss, Steve Seear, and Timmy Crawford.
Jetpack 
I have a few customizations with the Jetpack CSS module. Is there any benefit to moving the custom CSS I have in Jetpack to the custom CSS feature in WordPress?
LikeLike
We’ll migrate your CSS for you as soon as you update to Jetpack 4.4.2 and WordPress 4.7, so you won’t have to do anything!
LikeLike
You are a Gentleman and a Scholar! Thanks. đŸ™‚
LikeLike
Hi guys, I just wonder if you met the custom CSS feature of the Elegant Themes Divi theme, which works much the same way. Does this mean any similar features just became obsolete? Cheers
LikeLike
It depends on how the theme developer handled the change in WordPress now that it includes its own CSS editor. If you use Jetpack 4.4.2+ and WordPress 4.7+, Jetpack plays nice with the new editor: Jetpack’s old full-width CSS editor redirects to the new customizer tab, where you can edit your CSS and see those changes in the preview instantly. The CSS that was available in Jetpack’s CSS editor should be ported to WordPress’ new CSS tool, and saved as such. We’ve also ported our own special features (CSS Preprocessing, Custom content width, Revisions, …) into the customizer, inside that tab.
You would need to contact the theme developer to see how they’re managing this change and the impact of their own feature.
LikeLike
Hi Guys,
The 4.7 update seems to cause a serious conflict with the custom CSS function.
When I ran the 4.7 update over the weekend any attempt to get to Custom CSS resulted in a 403 error.
This occurred on all of my sites using an assortment of themes. The one common factor was that all sites were running BulletProof Security.
After the 4.7 update the BPS plugin could not be found. Attempting to access Custom CSS returned a 403 error.
I disabled all plugins except for Jetpack and the problem remained
I manually deleted BPS from the CPanel. The problem remained.
I had found an answer to a similar situation on BPS forum and applied and inserted
`# WP Theme Customizer customize.php skip/bypass rule
RewriteCond %{REQUEST_URI} (customize\.php) [NC]
RewriteRule . – [S=2]`
in the CUSTOM CODE WPADMIN PLUGIN/FILE SKIP RULES section.
The 403 errors when accessing Custom CSS stopped on all of my sites.
Now while BPS was a common factor on all sites, along with Wordfence, disabling these had no effect on the problem.
I also don’t like the small window. Would be good if it was able to be enlarged.
LikeLike
When using both Jetpack 4.4.2 and WordPress 4.7, we migrate your existing Custom CSS from Jetpack to the new WordPress editor, so even if you were to deactivate Jetpack’s Custom CSS module, you wouldn’t lose any data. This is located in the Customizer under the Additional CSS tab. Were you trying to access your CSS in the old way under Appearance -> Edit CSS? If so, you would not see the old CSS editor as we defer to the default CSS editor now in the Customizer.
If you’re not seeing your CSS in the new Customizer editor, please let us know.
We’ve chosen to migrate Jetpack’s Custom CSS module into the new WordPress CSS editor to avoid duplicating features, so the width of that editor isn’t controlled by Jetpack. However, if you’d prefer to have a full-width CSS editor in Jetpack in addition to WordPress’ new CSS editor, you can chime in with your thoughts on the GitHub issue:
https://github.com/Automattic/jetpack/issues/5828
LikeLike
Can I restrict the TOP POSTS and PAGES widget to show only a specific category or tag?
Thank you.
LikeLike
You can customize the list of posts available in the widget thanks to the
https://developer.jetpack.com/hooks/jetpack_widget_get_top_posts/filter, as explained here:https://developer.jetpack.com/hooks/jetpack_widget_get_top_posts/
LikeLike
Can you please provide more details for a noob? I see how to exclude post but not category/tag, I would like to include only a specific category/tag in the widget.
– I am also trying to change the look of the widget to add some separators between articles.
Thank you,
LikeLike
Start a new thread in the support forums or send us an email with more details about the categories you’d like to exclude, and we’ll help!
You can customize the look of every element on your site thanks to CSS. You can add that CSS to your theme stylesheet, or to your custom CSS editor available under Appearance > Edit CSS in your dashboard.
LikeLike