# Improving the "Beeminder-Ping" WordPress plugin

**URL:** <https://forum.beeminder.com/t/improving-the-beeminder-ping-wordpress-plugin/3946>\
**Category:** Akrasia\
**Created:** [May 25, 2018, 6:12pm UTC](https://forum.beeminder.com/t/improving-the-beeminder-ping-wordpress-plugin/3946 "2018-05-25T18:12:08Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![dreev](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/dreev/32/4311_2.png) [@dreev](https://forum.beeminder.com/u/dreev)\
**Post date:** [May 25, 2018, 6:30pm UTC](https://forum.beeminder.com/t/improving-the-beeminder-ping-wordpress-plugin/3946/2 "2018-05-25T18:30:06Z")

</div>

(Thanks so much for helping, @mattepp!)

The WordPress plugin has been utterly rock solid for us – sending +1’s for new posts to [blog.beeminder.com](http://blog.beeminder.com) to [beeminder.com/meta/blog](http://beeminder.com/meta/blog) – for years and years.

I recall now that at one point, editing an existing blog post would send a +1 to Beeminder if that blog post wasn’t already counted. Which is not typically what you want if you want to beemind your blog _starting now_. Our workaround was to just delete the extra datapoints. And future edits, if I’m remembering this right, didn’t send a new +1 so all was good after we’d hit the point of having edited all past blog posts at least once.

Sorry that’s such vague feedback! And my only feedback about the PHP library is that every time I look at it I have to fight the urge to purge all the OOP stuff and redo it in a functional style. 🙂

---

_[View the full topic](https://forum.beeminder.com/t/improving-the-beeminder-ping-wordpress-plugin/3946)._