Litespeed Cache issue after using Main WP to update plugins

I seem to have an issue after using Main WP to update plugins on websites that are using the Litespeed cache.

Is there a webhook that MainWP uses after updating a plugin that I can use to trigger a purge of the Litespeed cache?

Thanks.

@wingnuttter This has actually been talked about over on the FB MainWP user group. FB group Thread

You should be able to add this Snippet to the Child Site in question via the MainWP Code Snippets Extension.

MainWP Hook: mainwp_updates_after_plugin_updates

Add this action to fire off where it says ā€œ// your codeā€ & save it to ā€œExecute on Child Siteā€ this will save it to fire off in the future as well.

do_action( ā€˜litespeed_purge_allā€™ );

source: API | LSCache for WordPress | LiteSpeed Documentation

[UPDATED WORKING SCRIPTS]
[MainWP Code Snippet] - After WP Plugin update Hook Ā· GitHub
[MainWP Code Snippet NO EMAIL ] - Purge LiteSpeed cache after updates. Ā· GitHub

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.