Hi,
It appears that since version 4.0.0, the CAPI functionality is always enabled, and users can no longer disable it. Our use case is that we have the plugin installed on both our production and test sites, but we want to prevent the test site from sending data, as it impacts our analytics. While we could disable the plugin on the test site, we prefer to keep it active to fully test all plugins and ensure compatibility before deploying changes to production. Is there any plan to add the option to disable CAPI back in a future version, or what is the recommended approach for situations where we need to turn off CAPI functionality? Thank you in advance!
Hi,
It appears that since version 4.0.0, the CAPI functionality is always enabled, and users can no longer disable it. Our use case is that we have the plugin installed on both our production and test sites, but we want to prevent the test site from sending data, as it impacts our analytics. While we could disable the plugin on the test site, we prefer to keep it active to fully test all plugins and ensure compatibility before deploying changes to production. Is there any plan to add the option to disable CAPI back in a future version, or what is the recommended approach for situations where we need to turn off CAPI functionality? Thank you in advance!