Allows users to create custom classes on a per-post/term basis.
The Custom Classes plugin allows you to create custom classes for posts (when post_class()
is called) and for the <body>
class (when body_class()
is called). It creates a meta box on the edit post and edit term screens in the admin with input boxes for adding your custom classes.
Custom post classes are added whenever your theme calls the post_class()
function, which is generally whenever a post is shown. Custom body classes are added on the single view of the post whenever your theme calls the body_class()
function.
Please consider helping the cause by:
If you need professional plugin support from me, the plugin author, you can access the support forums at Theme Hybrid, which is a professional WordPress help/support site where I handle support for all my plugins and themes for a community of 75,000+ users (and growing).
If you’re a theme author, plugin author, or just a code hobbyist, you can follow the development of this plugin on it’s GitHub repository.
Certainly. This plugin works with any public post type on your site. It’s not just limited to the “post” post type.
Most likely, this means your theme isn’t using the appropriate functions (post_class()
and body_class()
). You’ll need to talk to your theme author to get them to fix this. Or, better yet, use a correctly-coded theme from Theme Hybrid!
I wanted a quick and easy way to add styles to my posts without having to make a tag, create a category, or use post formats. Those solutions are great, but they’re not ideal for every situation. By using a custom class, I have complete control over post styles.
A meta box named “Classes” gets added to the edit post screen in the admin. From there, you can input a custom post and/or body class for individual posts. On the edit/new term (category, tag, etc.) screen, a new field labeled “Body Class” is also available.
Of course, you actually have to style the class in your theme’s style.css
file for anything to actually change on the front end. This plugin just outputs the classes for you. It’s up to you to decide how to use them.
The change log is located in the changelog.md
file in the plugin folder. You may also view the change log online.