Alexandru Negoita

Thank you for your fast reply! It really means allot to me.

I thought at first to fork the plugin and keep it as such in the project. However, there is some flexibility left and I could actually extend the class-caching.php into the theme’s functions.php file.

First, I had to create a new class which extends the WooSEA_Caching class and add a function to clear SpinupWP object cache, which is actually using the wp_cache object … so it was just a “wp_cache_flush”.

Just for being safe, I also added the “spinupwp()->cache->purge_page_cache()” , after checking if spinupwp function exists. But, I don’t think is needed.

I called the newly created class in functions.php where I had overriten you two functions which deals with the caching:
woosea_project_refresh and woosea_create_all_feeds
using the proper actions for it.

In the new functions I replaced your caching class with the one that I created and extends yours.

Of course, this should be just a patch, until your team updates the plugin, taking into consideration the SpinupWP caching plugin.

I hope this will be helpful, as it might reduce the development time.