Jeff Matson

Yup! PHP7 is what I use for development of the plugin, so it’s going to be the most stable there.

Open up your inspector in Chrome and check the Network tab. How often is it firing?

Also, what plugins/themes do you have installed? Something might be overriding it.

Once the plugin is deactivated, it will no longer modify anything in the heartbeat.

At the moment, I haven’t tested with Gutenberg, but it’ll likely cause issues at the moment. Testing and patches are coming, but as this is something that I don’t profit on, it’s all up to when I have some spare time.

If someone wants to do some testing and bugfixes for me, it would be greatly appreciated.

It sounds like you have something that depends on the WordPress Heartbeat API. Try allowing the heartbeat on admin pages.

Admin-ajax.php will still fire on initial page load, but won’t utilize the heartbeat for subsequent requests on the page.

What this plugin does is allow you to control the automated requests to admin-ajax.php (usually every 15 seconds or so) after the page is already loaded. It won’t impact admin-ajax.php being loaded initially.

Just noticed that with the latest update! Done! Thanks!

Unless there’s a bug that’s impacting you, it should go away permanently as soon as you close it.

Could you send details on your environment (WordPress version, PHP version, etc) so that I could debug the issue?

Unless there’s a bug that’s impacting you, it should go away permanently as soon as you close it.

Could you send details on your environment (WordPress version, PHP version, etc) so that I could debug the issue?

The current version should operate just fine.

Weird. Haven’t seen this one pop up before.

If you don’t mind, could you set me up on a development environment so that I could test it? You can use https://jeffmatson.net/contact-me/ to send me over the credentials.

Yup! Just depends on when I have time to get around to it though. It’s one of the reasons the plugin was overhauled a while ago.

@bahead Could you post a lit of the plugins you’re running? Have you tried deactivating/reactivating other plugins one-by-one to see if you can locate which plugin is causing the conflict?

Looks like either something is re-enqueueing the script or something changed within elsewhere. I’ll be looking into it, but I have to find the time first.

If someone else wants to look into it before I can, I’ll gladly apply a patch for everyone.

@nicolasaczka I need more information to be able to troubleshoot it since these are the only reports I’m getting of this.