Jeff Matson

Weird. Haven’t heard of this one from anyone else. Could you shoot me over exactly what was said? Does updating to 1.2 resolve the issue?

This should be solved in 1.2.

I haven’t seen this issue at all and the only thing I’m thinking might cause it could be issues with WordPress user roles.

This issue occurs when you fail to select a location when the heartbeat is set to “modify”. I fixed it in 1.2 and it should no longer throw the error, but be sure to select a location.

I’m working on an update that clarifies things a bit. Hold tight for now.

If the heartbeat is firing on the frontend (many times it will), it’ll help.

Glad to see the issue went away. As the plugin is intentionally created to lessen page load, I’ve taken performance into consideration with every change I make. If it somehow pops up again, let me know.

@gecko_guy Thanks so much for your support. It helps a ton. It feels wonderful to know that my hard work is still appreciated, even if there are a few bumps in the road along the way.

@cpetitclerc73 Double-check it. Be sure to remove and reinstall it. That’s the exact error that appears in the earlier versions.

If you want it active on only the post editor, you’ll set Deny and select all boxes but the post editor.

I’ll be working more on the UI shortly to allow for more advanced conditions. Mainly trying to sort these initial requests first though.

Thanks for the support and understanding. I really appreciate it.

And yeah, maybe I shouldn’t have deployed at 7am when I had been up all night. Dealing with an onslaught of support tickets on roughly 2 hours of sleep isn’t very fun. Lesson learned. ??

@antermoia Overall, this isn’t a plugin that I’ve previously maintained much and the initial release was never intended to be as large as it has become.

For that reason, unit tests weren’t written and I noticed a potential issue (in 1.1), which when hastily corrected, led to a typo that wasn’t able to be caught by my IDE (in 1.1.1). Admittedly, the minor change wasn’t tested when committing it, so it got through.

I thought I caught it quick enough to minimize damage, but clearly I didn’t (although thankfully it looks like it only impacted less than 5% of sites).

I recognize the mistake, but the overall backlash is entirely overkill and honestly decreases motivation to continue developing open source plugins if I’m going to become a target for something I give away entirely out of good will.

Thanks, buddy! Always good to see encouragement when so much hate is flowing in. I knew my fellow devs would understand ??

Sorry to hear that it caused issues, but thanks for the 5-star review! Hopefully, it’s all going well for you since the patch was released.

@thelastbestwest @wpdreamer Yup. The issues only existed within the plugin files and don’t impact anything else on your site. There shouldn’t be a “next time”, but if you ever see anything like this with any of my plugins or someone else’s, you can just pull the plugin from the wp-content/plugins directory to fix it.

If you wouldn’t mind, I would appreciate it if you could update your review once you update to the fully functional version. I develop this plugin entirely in my free time without any compensation whatsoever, so reviews are my source of motivation to continue anything with it. I enjoy helping you all out, but when backlash like this happens, it’s rather disheartening.