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 …

Julio Potier

SeoMix

SecuPress

Daniel Roch

WordPress show your WordPress login and ID in several places. It’s time to fix this !
<ul>
<li>WordPress automaticaly uses “User login” to fill in the “User Display Name”.</li>
<li>WordPress also allows everyone to use the same value for Nickname, Display Name and Login.</li>
<li>The body_class function also shows to everyone your User ID and Login on author pages.</li>
</ul>
A hacker can easily see then use your “NickName” or “Display Name” to find your real login. Once activated, SX User Name Security will prevent WordPress from showing those informations, and will warn you if you need to fix old users.
Features
Body_class function:
<ul>
<li>Removes User ID from body_class function (front-end users pages)</li>
<li>Removes User Nicename from body_class function (front-end users pages)</li>
</ul>
Current User informations:
<ul>
<li>The plugin changes “Display Name” and “Nickname” to a random value (like ‘Ticibe T. Aduvoguripe’, ‘Lagubo N. Agigerovibe’ or ‘Datela N. Orejadavino’) if they are identiqual to user login</li>
<li>If not, it changes “Display Name” to “Nickname” or “Nickname” to “Display Name” if one of them is identiqual to user login</li>
</ul>
New Registration:
<ul>
<li>Display Name and Nickname are changed to random value during user registration.</li>
<li>Nicename is also changed (it’s used to generate the user permalink on the front-end). For previous user, a notice has been added to use another plugin to safely change old nicenames.</li>
</ul>
Other information:
All functions are translated into french and english.
You can find me here on <a href="https://www.seomix.fr" rel="nofollow ugc">SeoMix</a>, and here is the official french post about this plugin <a href="https://www.seomix.fr/user-name-security/" rel="nofollow ugc">https://www.seomix.fr/user-name-security/</a>
Find here our other plugins:
<ul>
<li><a href="https://fr.wordpress.org/plugins/seo-key/" rel="nofollow ugc">SEOKEY WordPress SEO plugin</a></li>
<li><a href="https://fr.wordpress.org/plugins/secupress/" rel="nofollow ugc">SecuPress Security plugin</a></li>
</ul>

SX User Name Security

SX User Name Security prevents WordPress from showing your real Login everywhere. It ovverides the body_class function, User Nicename, Nickname and Di …

Ambrosite Body Class Enhanced vs SX User Name Security