Compute

Awesome – and thanks for the fast reply!

The error is no more. Yay, thank you.

Meh ?? But thanks for the answer!

Could you make a gist of you update and form methods of you widget?

@hummelmose Right ?? This is just a fix without hacking the core files.

@hummelmose Its just a normal plugin. It stops WordPress 4.3 from keep spamming the cron option – but it does not remove the currently wrong cronjobs (will do soon if a 4.3.1 is not around the corner).

@rené Yes the plugin only stops the new spam cronjobs. The idea is to remove the current spam cronjobs if the plugin gets approved to the .org directory anytime soon.

I made a hotfix plugin that stops WordPress from spamming the cron option:

https://github.com/phh/wp43-stahp-spamming-my-cron

We’ve implemented this is our MU-plugin (so we can roll it out with a mass deploy).

add_filter( 'schedule_event', 'schedule_event_unset_batch_split_terms' );
function schedule_event_unset_batch_split_terms( $event ) {
	if ( $event->timestamp == 'wp_batch_split_terms' ) {
		return false;
	}

	return $event;
}

But its really sad that this is a known issue for 5 days (and closed 3 days ago). For a developer this bug is really annoying. For a non-technical type this could just break their site.

Is there a reason that there has not been a release yet? This could break alot of sites.

Sorry I haven’t had the time to answer this. I think I’ll do a merge request with a better explanation instead of this “quickfix” question I started with.

Thanks ??

Oh yeah there is already events for that.

But so lets say I have an option that will change the behavior on a certain page. Or the widgets on the frontpage have been updated. Then I’m left with purging manual whenever any of these settings are updated.

Well. For instance on my site. When a new post is updated, a special page with a custom template should get purged, as its using data from all newest posts.

There are no way for this plugin to know that my setup works like that, but if I had a filter for the $purgeUrls I could purge my special page, whenever a post is updated.

But it seems like this plugin is using shutdown?
https://github.com/wp-plugins/varnish-http-purge/blob/master/varnish-http-purge.php#L45

https://codex.www.ads-software.com/Plugin_API/Action_Reference/shutdown

New events that would cause the plugin to purge. For instance, when I update something (mayeb a setting), I would like to purge some URL.
This could be done if execute purge had a filter for the execute purge urls, as it is run on every shutdown.

True, but only on getRegisterEvents actions ??

Makes sense. Thank you!

Correct. You can also use your own defined image sizes you have added from the add_image_size() function.