Jeff Matson

It should dismiss without an issue, and I can’t seem to replicate what you’re seeing.

As of version 1.2.5, I’ve added a filter to completely disable it. Just return true to hbc_disable_notice and it’ll prevent it from displaying.

Could you also send me details on your environment (PHP version, WordPress version, plugins/themes active, etc.) so that I can try to replicate what you’re seeing?

This is due to the old WordPress version that you’re running. As wp_parse_url wasn’t introduced until WordPress version 4.4, you’ll need to update to use it in specific locations like this.

I’ll see if I can come up with a backwards compatibility fix, but you really should update WordPress, if only due to security concerns with a version this old.

@busterboydesigns was right.

It’s caused by an error when I deployed 1.2.4 which caused some users to experience this issue. The issue has since been resolved as of today with the release of version 1.2.5. Sorry about that!

Basically, it causes less requests for admin-ajax.php by limiting the WordPress heartbeat. Normally, the heardbeat will make a request to admin-ajax.php every X seconds (usually somewhere around 15 seconds, depending on where you are on the site and other plugins/themes). This allows you to disable or throttle those requests.

This plugin doesn’t create anything additional. Once you deactivate it, none of the functionality will be there.

This was caused by an issue if no locations were selected after installation. It’s been fixed as of version 1.2.4. Thanks!

Yup! Just updated the compatibility tag in the latest version as well.

Fixed as of 1.2.4!

Thanks!

It looks like there was an issue that was caused if no locations were selected in the settings page. I just added an additional check to handle it in 1.2.4. All should be good in the latest version I just pushed.

Thanks!

No network settings at the moment. It’s something I want to do, but just have to find the time. Since this is a “in my spare time” plugin that I don’t profit from at all, it just depends on if I find the time for it.

If anyone wants to write the code for it, I’d be happy to integrate it.

Thanks for the heads up. It seems to be a unique issue. I’ll see what’s up and get some extra error handling in here with the next update.

Weird. I’ll take a look and see what I can find. Thanks for the heads up!

Nope. Heartbeat Control doesn’t collect any data, so GDPR doesn’t apply here.

It’s possible that something may be overriding the settings. Could you send me over a link to the site you’re having trouble with, as well as your configuration settings and any plugins/themes you’re using?

You’re going to want to look into your files and site as it sits on the server. The file should exist by default there.

Heartbeat Control can limit these requests, but many things in WordPress will still utilize admin-ajax.php, so you’ll still see some errors if the file isn’t actually present.