We'll create fresh WordPress site with cbnet Ping Optimizer installed. You have 20 minutes to test the plugin after that site we'll be deleted.
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.
Let me explain why, starting with a walkthrough of how pings work in WordPress, courtesy of @Otto42:
Regarding draft, scheduled (future), and edited posts:
So consider again the Plugin description:
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:
- 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.
- 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.
- 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.
It should be obvious that most of that just isn’t true anymore.
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.
As you see above, this isn’t true. Saving a draft post does not fire the publish_post action; therefore, no pings are triggered.
When you create a new post, your blog will ping and notify all the ping services that it has been updated.
WordPress core functionality does this already.
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.
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.
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.
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.