Ben Huson

<h4>Add missing classes</h4>
Adds missing classes for selected menu states. Classes added include:
<ul>
<li><code>current-page-parent</code> and <code>current_page_parent</code></li>
<li><code>current-page-ancestor</code> and <code>current_page_ancestor</code></li>
<li><code>current-menu-ancestor</code></li>
<li><code>current-menu-parent</code></li>
</ul>
The classes are added in the following scenarios:
<ul>
<li>When viewing an attachment page classes are added to any parent pages and their menu ancestors.</li>
<li>When viewing a post classes are added to any relevant taxonomy menu items and their manu ancestors.</li>
</ul>
<h4>Manage Menu Select States</h4>
Allows you to control which menu items should be selected (or deselected) when viewing certain pages of your site. You need to add classes to the menu items for this to work.
<ul>
<li><code>ecms-archive-{$post_type}</code> – Select menu item when viewing a post type archive page.</li>
<li><code>ecms-single-{$post_type}</code> – Select menu item when viewing a single post type page.</li>
<li><code>ecms-taxonomy-{$taxonomy}</code> – Select menu item when viewing a taxonomy archive.</li>
<li><code>ecms-taxonomy-{$taxonomy}-term-{$term}</code> – Select menu item when viewing a taxonomy term archive.</li>
<li>
<code>ecms-404</code> – Select menu item when viewing a 404 page.
</li>
<li>
<code>ecms-no-archive-{$post_type}</code> – Deselect menu item when viewing a post type archive page.
</li>
<li><code>ecms-no-single-{$post_type}</code> – Deselect menu item when viewing a single post type page.</li>
<li><code>ecms-no-taxonomy-{$taxonomy}</code> – Deselect menu item when viewing a taxonomy archive.</li>
<li><code>ecms-no-taxonomy-{$taxonomy}-term-{$term}</code> – Deselect menu item when viewing a taxonomy term archive.</li>
<li><code>ecms-no-404</code> – Deselect menu item when viewing a 404 page.</li>
</ul>

Extra Classes

Adds classes for selected menu states such as highlighting categories when viewing a blog post or parent page when viewing an attachment page.

ambrosite

When activated, this plugin causes the body_class template tag to output five additional classes.
On single posts (is_single) : 
 postname-[permalink slug] 
 single-[category slug] 
 parent-[parent category slug] (all parent and grandparent categories in a hierarchy of any depth)
On pages (is_page) : 
 pagename-[permalink slug]
On category archives (is_archive and is_category) : 
 parent-category-[parent category slug] (all parent and grandparent categories in a hierarchy of any depth)
<h4>Custom Taxonomies</h4>
As of version 1.3, the plugin now supports custom hierarchical taxonomies. The new body classes take the following form:
On single posts (is_single) : 
 single-[taxonomy]-[term slug] 
 parent-[taxonomy]-[parent term slug] (all parent and grandparent terms in a hierarchy of any depth)
On taxonomy archives (is_archive and is_tax) : 
 parent-term-[parent term slug] (all parent and grandparent terms in a hierarchy of any depth)
For single posts, the taxonomy name is included in the class name, because I felt it was important to be able to distinguish between taxonomies in cases where a post is assigned to more than one custom taxonomy, and when the same term might appear in two or more taxonomies. For example, suppose you had a real estate site with property listings in New York City, and you had two custom taxonomies defined: City and State. Then the classes would look like this:
<pre><code>single-city-new-york single-state-new-york
</code></pre>
<h4>Multisite Support</h4>
As of version 1.3, the plugin now supports multisite installations. If a multisite install is detected, the plugin will output the follow additional body class on every page of the site:
<pre><code>site-[site ID]
</code></pre>
<h4>Examples</h4>
If you have a post titled “Top 10 Decorating Ideas”, in category “Christmas”, with a parent category of “Holidays” and a grandparent category of “Calendar”, the additional body classes will be as follows:
<pre><code>postname-top-10-decorating-ideas single-christmas parent-holidays parent-calendar
</code></pre>
Why is this useful? Because it enables you to style individual posts and pages, as well as entire categories of posts, using only CSS, without having to edit the template files or create new templates.
Continuing the above example, if I wanted to give all of the posts in the Christmas category a green heading (to give them some extra holiday cheer), I could use a CSS selector like this:
<pre><code>body.single-christmas h1 {
 color: green;
}
</code></pre>
Going further, suppose I want to attach a background image of a Christmas tree ONLY to the “Top 10 Decorating Ideas” post:
<pre><code>body.postname-top-10-decorating-ideas div.post {
 background: url('images/xmas_tree.gif') no-repeat left top;
}
</code></pre>
What if I want all posts categorized under Holidays (Christmas, Thanksgiving, Easter, whatever) to have a sidebar with a gold border?
<pre><code>body.parent-holidays div#sidebar, /* all posts assigned to a subcategory of Holidays */
body.single-holidays div#sidebar { /* any posts assigned directly to the Holidays category */
 border: solid 2px gold;
}
</code></pre>
These are just a few examples. If you are experienced in writing CSS selectors, you will find many more uses for the new body classes. For further discussion, check this support forum thread: https://wordpress.org/support/topic/393942

Ambrosite Body Class Enhanced

Still works fine. Please release an updated version so it's not flagged as obsolete.

Still great

Enhances the body_class template tag, adding some extra classes to the body (post/page slugs, post categories, and archive parent categories) useful i …

Extra Classes vs Ambrosite Body Class Enhanced