I would recommend that you contact the W3 Total Cache support forum for clarification: https://wordpress.org/support/plugin/w3-total-cache/
The issue is not with W3 Total Cache, because also the other plugins I have tried caused the same conflict. I think the issue is with the combination of WordPress, Woo and hosting, especially the latest, because the same combination of WP, Woo, Cache on other hostings doesn’t result in any conflicts.
You are here in the general support forum for WordPress. Your problem concerns the interaction between different plugins. This is not a problem with the WordPress core itself but between these plugins.
Since you gave the specific example with W3 Total Cache, I would recommend that you contact their support forum again. The users and support there know how their plugin works and would be able to best assess which function from their plugin is causing you problems here. It is also possible that this is something that is used by other caching plugins that you have tested. But I can’t say, partly because I don’t know how many caching plugins are programmed. This is beyond the scope of this general WordPress support forum.
Alternatively, you can also take a closer look at the error you are seeing. Unfortunately, you only wrote that there is an error, but not which one. If you don’t see a specific error message, a look at the error log can also be helpful. There you will find the specific cause of the error that has occurred. The debug mode of WordPress could also be helpful in this analysis, see: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/ – in the result you will probably find something that comes from W3 Total Cache and you would then have to contact their support forum with this information.
