Chip Bennett

As of WordPress 4.3, this Plugin is no longer needed. The next update will integrate the Plugin into the core site icon feature, to allow for graceful 
retirement of the Plugin.
Add a Favicon to your site. No bells or whistles; simply upload a (ICO, PNG, or GIF) file.
Note: Plugin settings can be configured via Dashboard -> Settings -> Favicon.

cbnet Favicon

Add a Favicon to your site. No bells or whistles; simply upload a (ICO, PNG, or GIF) file.

Hello there! You may be wondering why you’re reading this, instead of looking at Plugin settings. Well, the reason that you’re not looking at Plugin settings is because there aren’t any Plugin settings anymore. In fact, this Plugin doesn’t have any functionality anymore.
Why? Because this Plugin’s functionality is no longer needed. In fact, this Plugin’s functionality may never have been needed in the first place. But regardless of that, it certainly isn’t needed now.
<h4>How Pings Work in WordPress</h4>
Let me explain why, starting with a walkthrough of how pings work in WordPress, courtesy of @Otto42:
<ul>
<li>When a post gets created, updated, inserted, modified, etc., eventually, it always goes through wp_insert_post().</li>
<li>wp_insert_post() calls wp_transition_post_status().</li>
<li>wp_transition_post_status() does various actions, but importantly it does this:</li>
<li>do_action(“{$new_status}_{$post->post_type}”, $post->ID, $post);</li>
<li>So the action of new-status and new-post-type is called. In this case, we’re interested in the publish status on the post post-type, so publish_post is the action hook.</li>
<li>In wp-includes/default-filters.php, we have this: 
** add_action( ‘publish_post’, ‘_publish_post_hook’, 5, 1 ); 
** So that causes publish_post to call _publish_post_hook().</li>
<li>_publish_post_hook(), among other things, adds the ‘_pingme’ post meta to the post, and schedules the do_pings action for a one-time cron call, which will happen on the next page load (because it’s hooked to time() for the schedule).</li>
<li>Again in wp-includes/default-filters.php, we have this: 
** add_action( ‘do_pings’, ‘do_all_pings’ );</li>
<li>The do_all_pings() function does all the pings for all the posts that are marked as needing them done at the moment.</li>
</ul>
Regarding draft, scheduled (future), and edited posts:
<ul>
<li>Draft posts have a post_status of draft, meaning that wp_transition_post_status() calls do_action() on draft_post rather than on publish_post. Scheduled posts have a post_status of future, meaning that wp_transition_post_status() calls do_action() on future_post rather than on publish_post. Thus, neither draft nor scheduled posts get pings sent for them until they actually transistion to publish, since that is when the publish_post action will get fired.</li>
<li>Editing posts: editing an existing post will send pings for the post, but do_all_pings() is smart. It calls the pingback() function to send pingbacks to blogs, and that in turn calls the get_pung() function to get the URLs in the post that have already been successfully pinged once before. This is very old code – so old, in fact, that the list of pinged blogs is actually a primary column (pinged) in the wp_posts table.</li>
</ul>
<h4>Why the Ping Optimizer Plugin Isn’t Needed</h4>
So consider again the Plugin description:
<blockquote>
Do you know your WordPress blog pings unnecessarily every time you edit a post? Think how many times you click on “Save and Continue Editing” or “Save” button. Your blog will ping unnecessarily that many times you click on those buttons.
Save your blog from getting tagged as ping spammer by installing this plugin.
After you install cbnet Ping Optimizer:
<ul>
<li>When you create a new post, your blog will ping and notify all the ping services that it has been updated. This encourages search engines and different blog directories/services to index your updated blog properly.</li>
<li>When you edit an existing post, it won’t send any unnecessary ping to ping services and saves your blog from getting banned by such services.</li>
<li>When you post a future post by editing the time stamp, it will ping only when your post appears in future. It won’t unnecessarily ping many times when you schedule posts as WordPress does by default.</li>
</ul>
</blockquote>
It should be obvious that most of that just isn’t true anymore.
<blockquote>
Think how many times you click on “Save and Continue Editing” or “Save” button. Your blog will ping unnecessarily that many times you click on those buttons.
</blockquote>
As you see above, this isn’t true. Saving a draft post does not fire the publish_post action; therefore, no pings are triggered.
<blockquote>
When you create a new post, your blog will ping and notify all the ping services that it has been updated.
</blockquote>
WordPress core functionality does this already.
<blockquote>
When you edit an existing post, it won’t send any unnecessary ping to ping services and saves your blog from getting banned by such services.
</blockquote>
As you see above, WordPress intelligently fires pings when a post is edited, by keeping track of previous successful pings and not re-pinging them.
<blockquote>
When you post a future post by editing the time stamp, it will ping only when your post appears in future. It won’t unnecessarily ping many times when you schedule posts as WordPress does by default.
</blockquote>
As you see above, scheduling a post fires the future_post action, and not the publish_post action. Thus, until a scheduled post actually transitions to publish, thereby firing the publish_post action, no pings are triggered.
So, none of this Plugin’s functionality is needed. You can safely deactivate and uninstall it, with the understanding of why the core WordPress handling of pings works just fine.

cbnet Ping Optimizer

Doesn't do anything. Isn't needed. Core WordPress handling of Pings is oh-so-fine!

cbnet Favicon vs cbnet Ping Optimizer