Scott Reilly

Display an image for each category associated with a post.
Notes:
This plugin provides the templates tag <code>c2c_the_category_image()</code> which basically reproduces and extends the functionality of WordPress’s core function <code>the_category()</code> to add the ability to display a category image instead of the category name in the link to the category archive. With its $image_extensions argument defaulted to <code>""</code>, the plugin could be a drop-in replacement for <code>the_category()</code>. As is done in <code>the_category()</code>, the image or text for each category is also a link back to that category’s archive.
Related info about the function:
<ul>
<li>If $image_extensions is defined, but no image is found for the category, then nothing is displayed for that category.</li>
<li>$image_extensions can be defined as a space separated list of image extensions. Files will be checked with the image extensions in the order those extensions were provided; default is ‘png gif jpg’.</li>
<li>The number of category links/images displayed can be limited via the $limit argument</li>
<li>Category image tags are defined with class=”catimage” for stylesheet manipulation.</li>
<li>The result can be filtered via the filter named “c2c_the_category_image”.</li>
<li>
Must be run inside “the loop”.
c2c_get_category_image_list() is another provided function, which is identical to <code>c2c_the_category_image()</code> except that it doesn’t echo the result.
</li>
</ul>
Links: <a href="http://coffee2code.com/wp-plugins/category-images/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/extend/plugins/category-images/" rel="ugc">Plugin Directory Page</a> | <a href="http://coffee2code.com" rel="nofollow ugc">Author Homepage</a>
<h3>Template Tags</h3>
The plugin provides one optional template tag for use in your theme templates.
<h4>Functions</h4>
<ul>
<li><code><?php function c2c_the_category_image( $seperator='', $parents='', $image_extensions='png gif jpg', $image_dir='/wp-content/images/', $use_name_if_no_image=false, $start_from='begin', $limit=999 ) ?></code></li>
</ul>
This displays the image associated with a post’s categories.
<h4>Arguments</h4>
<ul>
<li>
<code>$separator</code> 
Optional argument. The text and/or HTML to appear between each of a post’s category images.
</li>
<li>
<code>$parents</code> 
Optional argument. Allows you to specify if you want ancestor categories of a post’s category to be imaged and linked as well. Valid options are ‘multiple’, ‘single’, and ”. Default is ”.
</li>
<li>
<code>$image_extensions</code> 
Optional argument. A space-separated list of image extensions (case insensitive). If defined as ” then no image is retrieved and the category name is displayed instead (a la <code>the_category()</code>). Default is ‘png gif jpg’.
</li>
<li>
<code>$image_dir</code> 
Optional argument. The directory in which the category image(s) reside. The value should be a location relative to the main URL of your blog. Default is ‘/wp-content/images/’
</li>
<li>
<code>$use_name_if_no_image</code> 
Optional argument. Boolean value (true or false) indicating if the name of the category should be displayed for each category that does not have an associated image. Default is false.
</li>
<li>
<code>$start_from</code> 
Optional argument. How to traverse the list of post’s categories; either ‘begin’ or ‘end’. Default is ‘begin’
</li>
<li>
<code>$limit</code> 
Optional argument. The maximum number of category images to be displayed. Default is 999 (basically, no limit)
</li>
<li>
<code>$post_id</code> 
Optional argument. The Post ID. If false, then use the current post (i.e. while in the loop). Default is false.
</li>
</ul>
<h3>Examples</h3>
<ul>
<li>
You can opt to treat only certain categories as having a graphical representation by defining an image for them but not creating images for the non-graphically represented categories (as in you can have a subset of categories that dictate what image to be displayed for the post).
</li>
<li>
You can take advantage of the $image_extension and/or $image_dir arguments to display different category icons under different contexts, i.e. if showing a $single post, choose to use a ‘png’ image, otherwise use ‘gif’; or locate your images in different directories ‘/wp-content/images/cat-images/small/’ and ‘/wp-content/images/cat-images/large/’ and decide based on context where to get the image(s) from:
// In showing the post singularly, then use a larger image, else use a small image 
 if ( is_single() ) { 
 c2c_the_category_image(”, ”, ‘gif’, ‘/wp-content/images/cat-images/large/’); 
 } else { 
 c2c_the_category_image(”, ”, ‘gif’, ‘/wp-content/images/cat-images/small/’); 
 }
</li>
<li>
Show all images in a comma-separated line:
</li>
<li>
Show all images in an unordered list:
</li>
<li>
Assuming one category per post, just show the category image without further HTML markup:
< ?php c2c_the_category_image(' '); // note the space in the argument, necessary to turn off default 
<ul> markups ?>
<h3>Filters</h3>
The plugin exposes two filters and one action for hooking. Typically, customizations utilizing these hooks would be put into your active theme’s functions.php file, or used by another plugin.
</li>
</ul>
<h4>c2c_get_category_image (filter)</h4>
The ‘c2c_get_category_image’ hook allows you to use an alternative approach to safely invoke <code>c2c_get_category_image()</code> in such a way that if the plugin were deactivated or deleted, then your calls to the function won’t cause errors in your site.
Arguments:
<ul>
<li>same as for <code>c2c_get_category_image()</code></li>
</ul>
Example:
Instead of:
<pre><code> <?php $cat_images = c2c_get_category_image( $cat ); ?>
</code></pre>
Do:
<pre><code> <?php $cat_images = apply_filters( 'c2c_get_category_image', $cat ); ?>
</code></pre>
<h4>c2c_get_the_category_image_list (filter)</h4>
The ‘c2c_get_the_category_image_list’ hook allows you to use an alternative approach to safely invoke <code>c2c_get_the_category_image_list()</code> in such a way that if the plugin were deactivated or deleted, then your calls to the function won’t cause errors in your site.
Arguments:
<ul>
<li>same as for <code>c2c_get_the_category_image_list()</code></li>
</ul>
Example:
Instead of:
<pre><code> <?php $cat_list = c2c_get_the_category_image_list(); ?>
</code></pre>
Do:
<pre><code> <?php $cat_list = apply_filters( 'c2c_get_the_category_image_list', '' ); ?>
</code></pre>
<h4>c2c_the_category_image (action)</h4>
The ‘c2c_the_category_image’ hook allows you to use an alternative approach to safely invoke <code>c2c_the_category_image()</code> in such a way that if the plugin were deactivated or deleted, then your calls to the function won’t cause errors in your site.
Arguments:
<ul>
<li>same as for <code>c2c_the_category_image()</code></li>
</ul>
Example:
Instead of:
<pre><code> <?php c2c_the_category_image(); ?>
</code></pre>
Do:
<pre><code> <?php do_action( 'c2c_the_category_image' ); ?>
</code></pre>

Category Image(s)

Display an image for each category associated with a post.

deathnfudge

fontawesome

frrrances

mlwilkerson

robmadole

The official way to use Font Awesome Free or Pro icons on your WordPress site, brought to you by the Font Awesome team.
<h4>Features</h4>
Our official plugin makes it easy to add Font Awesome icons to your pages, posts, and templates and includes the following features:
<ul>
<li>Use Pro or Free icons, from the latest release or a specific release.</li>
<li>Use custom icons from your Pro Kits.</li>
<li>Use a Font Awesome Kit to add any of our icons (including the latest Duotone styles and custom icons!), or select the Font Awesome CDN for Version 5 icons only.</li>
<li>Turn on automatic compatibility for Font Awesome Version 4 if you – or your plugins – are still using Version 4 syntax.</li>
<li>Troubleshoot and resolve issues when multiple versions of Font Awesome are loading on your site from other plugins/themes, which can cause unexpected icon display or technical issues.</li>
</ul>
<h3>How to Use</h3>
Install And Enable The Plugin 
(See the Installation tab for details)
How to Add and Style Icons 
Full docs on how to use the plugin and add icons are available on the <a href="https://docs.fontawesome.com/web/use-with/wordpress/add-icons" rel="nofollow ugc">Font Awesome Docs site</a>.
Add Icons in the Block Editor 
Once you’ve set up your plugin, you can add icons as blocks or inline with text.
To add icons as blocks, select the “Font Awesome Icon” block, and then click the “Choose Icon button” to open the Icon Chooser.
To add icons inline, select the Font Awesome option in the format toolbar to open the Icon Chooser. (Note: Inline icons require at least WP 6.3.)
Once you open the Icon Chooser, add icons by:
<ol>
<li>Searching for the icon you want – you can search by icon name, category, or keyword.</li>
<li>Changing the Family and Style using the drop downs if you want an icon in a different style.</li>
<li>When you see the icon you want, clicking it to enter it into the content of your page or post.</li>
</ol>
Note: If you want to search and add Pro icons in the Icon Chooser, make sure you set your plugin to use a Pro Kit.
Add Icons in The Classic Editor 
If you need to add icons in the classic editor, you can <a href="https://fontawesome.com/icons?d=gallery" rel="nofollow ugc">use the icon names in shortcodes or HTML</a>. Add an icon using shortcodes to any text area – just add the name of the icon and a style prefix, where <a href="https://fontawesome.com/how-to-use/on-the-web/referencing-icons/basic-use" rel="nofollow ugc">the prefix is the style of icon</a> you want to use. Note that you don’t need to include the <code>fa-</code> part of the icon name. And if you don’t include any style prefix, the icon will default to the Classic Solid style.
The shortcode for an icon looks like this:
<pre><code>[icon name="stroopwafel"]

[icon name="stroopwafel" prefix="fa-sharp fa-light"]
</code></pre>
You can also use basic HTML with <a href="https://fontawesome.com/how-to-use/on-the-web/referencing-icons/basic-use" rel="nofollow ugc">standard Font Awesome syntax</a>, like this:
<pre><code>
</code></pre>
Using Pro Icons and Features 
To use a Kit to power your icons, <a href="https://fontawesome.com/kits" rel="nofollow ugc">create a Kit on FontAwesome.com</a> and select “Pro icons” in the Kit Settings tab. Then grab your <a href="https://fontawesome.com/account#api-tokens" rel="nofollow ugc">API Token from your Font Awesome Account page</a> and add it to your WordPress plugin settings.
To use the CDN to power your icons, know that you will only be able to use icons from Version 5. To enable Pro icons, add your site’s domain to the list allowed domains on your <a href="https://fontawesome.com/account/cdn" rel="nofollow ugc">Font Awesome CDN Settings page</a> and then use shortcodes or HTML to add the icons into your content.
Troubleshooting with the Plugin 
Font Awesome icons are popular, so lots of themes and plugins also load Font Awesome, and sometimes their version can conflict with yours. So we created a way to help you find and prevent those conflicting versions from affecting your icons: The Conflict Detection Scanner.
If the plugin seems to be set up correctly and your icons still aren’t loading and you’re not sure why, head over to the Troubleshoot tab, which has two parts:
<ul>
<li>Detect Conflicts with Other Versions of Font Awesome – which lets you start the conflict detection scanner to find versions of Font Awesome loading on your site.</li>
<li>Versions of Font Awesome Active on Your Site – which shows the results of the scanner and lets you prevent any conflicting versions from loading other versions of Font Awesome on your site.</li>
</ul>
Get more information about using the scanner for troubleshooting on the <a href="https://docs.fontawesome.com/web/use-with/wordpress/troubleshoot" rel="nofollow ugc">Font Awesome WordPress docs</a>.
<h3>Configuring</h3>
The plugin is set to serve Font Awesome Free icons as a Web Font via the Font Awesome CDN by default. You can change the CDN settings right in the plugin. If you want just the basic Free icons, you probably don’t need to make any changes to the default configuration.
You can get more information about all the available settings and troubleshooting on the <a href="https://docs.fontawesome.com/web/use-with/wordpress" rel="nofollow ugc">Font Awesome WordPress docs</a>.
<h3>Upgrading from Plugin Version 4</h3>
<ul>
<li><code>[icon]</code> shortcodes found in Block Editor content and elsewehre will continue to work as before, 
though new icons added with the Icon Chooser in the Block Editor will be inline SVGs. 
Previously added <code>[icon]</code> shortcodes will not be automatically be converted into the new inline SVG 
format. If you want to convert an <code>[icon]</code> shortcode, delete it and re-add the icon using the Icon Chooser in the Block Editor.</li>
</ul>
<h3>See Also</h3>
The <a href="https://github.com/FortAwesome/wordpress-fontawesome/blob/master/README.md" rel="nofollow ugc">README</a> on GitHub has details for WordPress site owners and developers.
You can get more information about all the available settings and troubleshooting on the <a href="https://docs.fontawesome.com/web/use-with/wordpress" rel="nofollow ugc">Font Awesome WordPress docs</a>.
And there are <a href="https://fortawesome.github.io/wordpress-fontawesome/" rel="nofollow ugc">API docs</a> for developers.

Font Awesome

Update: They refunded me after issues so I revised my rating. I do hope they update their Pro service. Original review below.

I upgraded to Pro because I thought it would speed up my site with their SVGs and the kit. My site load time went from 8 seconds to 20 seconds! If I deactivate the plugin to remove FA my site loads in 3 seconds. I know HTML and CSS so I know what I am doing here.

I have spent 2 months trying to figure out their documentation when I can figure out other programming languages in a couple days. The documentation is vague and not intuitive. Their customer support is equally as bad with one sentence answers that don't answer the question.

I think I might just go without icons to speed up might site. I want my money back!

updated: refunded me

This plugin work great as they did not left the junk behind in the DB on uninstalled.

But I found no option to use the Font Awesome assets (such as CSS+fonts) on my local site without CDN access.

For example that I may have to install the website and then use in the intranet where no external access.

However, there is some errors with WordPress 5.9-RC2-52567, PHP 7.1. It said:

Undefined variable: should_enable_icon_chooser in font-awesome\includes\class-fontawesome.php on line 1623

No local files.

This works perfectly for me where others didn't.

Just works

The Font Awesome plugin makes it easy to stay on top of the latest version that is otherwise hidden away in some assets folder. Block editor support makes it easy to insert icons without having to remember their names. Can't wait for version 6.

Great free icons

For a free product this works quite well and allows users to quickly add font-awesome to their site without messing with custom code.   If they offered a Pro version of this then it would definitely need to be cleaned up to work more easily on the editor side, however for a free piece of software its pretty nice and allows me to more easily integrate font-awesome into my sites.

Thanks!

Excellent Free Product

The official way to use Font Awesome Free or Pro icons on your WordPress site, brought to you by the Font Awesome team.

Category Image(s) vs Font Awesome