Hello Emre, thanks for reaching out.
The things you have raised are related to the compatibility fixes we had applied in our plugin in order the scripts required for it to operate were properly inserted in the site code. This is controlled by “Caching compatibility” option in our plugin – once enabled these fixes are applied.
Now why we did it like that: simply because we haven’t found any other way to do it in your plugin. What we needed is to be able to remove our scripts from Preloading as it was affecting the functionalites of Cookie Compliance JS widget. As we have not find a filter hook or a different method to exclude it selectively we had to disable it in your plugin (but only when “Caching compatibility” was on). Maybe that’s not super elegant from your perspective but our priority is to take care of website visitors privacy and their right to consent, which was not fully possible without those tweaks.
Regarding the purge cache issue – indeed we’re doing that but only in specific and resonable situations, like changing our plugin settings or app configuration. Maybe there’s a case that we have missed in our tests and this is triggered in scenarios we’ve not taken into account, but we’d need some more feedback on that to try to replicate it.
Best,
Bartosz
