Working with Autoptimize

You can edit your posts for an hour from making it, to prevent a double post, Frank.

And I understood the question, I wanted to be sure I was looking at the right plugin 🙂 There are 45k plugins. I try not to assume the one I think they mean is the right one.

That’s a funny question, y’know… Because I’m not sure what the best order here is, in part because I’m not 100% up to speed on how your plugin (if that IS the right one 😉 ) works. Looking at how you coded around WP Super Cache, that may be the route we have to do.

I already have a filter for varnish_http_purge_events:

protected function getRegisterEvents() {

		// Define registered purge events
		$actions = array(
			'save_post',            // Save a post
			'deleted_post',         // Delete a post
			'trashed_post',         // Empty Trashed post
			'edit_post',            // Edit a post - includes leaving comments
			'delete_attachment',    // Delete an attachment - includes re-uploading
			'switch_theme',         // Change theme
		);

		// send back the actions array, filtered
		// @param array $actions the actions that trigger the purge event
		return apply_filters( 'varnish_http_purge_events', $actions );
	}

That would work for individual posts.

Though it sounds like you need to flush the WHOLE cache and not just the ones for the post? I’m not 100% sure ‘when’ this situation is popping up. I’m guessing that what’s going on is the OP is flushing the Autoptimize cache after making ‘some change’ to the theme, and then has to flush the whole Varnish cache.

I don’t have a way to externally trigger the whole Varnish cache. It’s intentional that it has to be a conscious manual action, since you really should RARELY be doing anything that requires it. The common situations are ‘adding new plugins’ and ‘changing themes manually’ which really should be rare occurrences.

You don’t have to sign your posts 🙂 Frank you should read https://codex.ww.wp.xz.cn/Forum_Welcome

switch_theme IS in there for flushing cache already (I thought it was removed, but I see it in my 3.9 alpha code …)

That said, I know your usecase is purging both, but that’s not actually a full usecase. WHY do you need to flush the whole Autoptimize cache? What changes are being made? How often do people really do this? The OP made it sound like it was a regular occurrence which a full cache flush really should never be.

Using any caching while actively developing your site’s design is a recipe for pain 🙂