-
Notifications
You must be signed in to change notification settings - Fork 340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
disable tracking_log #1252
Comments
Hello @grebbekevin, Are you sure that with I cannot reproduce it on a CE 2.2.7 in production mode with ElasticSuite 2.6.4 and the problem is that the code that ensures the boolean config param is taken into account is already there in 2.6.1... Are you on a EE version or a CE ? Regards, |
@grebbekevin any update on this one ? |
Dear Rbayet, We are still having this issue. |
Hello, just to ensure you understand how the workflow is done. When people navigate on the website, tracking data are stored (temporarily) on the MySQL table called @rbayet tested it, and on our instance, if the tracking is disabled in the back-office, this table does not get filled. Then, the tracking data contained in this table are sent (by batch) regularly to the Elasticsearch storage (your bonsai.io) by a cronjob. This is done like this because Elasticsearch has poor performance with multiple (concurrent) writing and would suffer too much if we keep writing each event in Elasticsearch one by one. That's why this buffer table exists. That being said, Please provide us :
Regards |
Ok, I think I have some insights, most probably, the only events that continue to get registered are the "add to cart", since all the frontend tracking part is properly disabled if the config says so. But the "add to cart" tracking is done in PHP and does not seem to be conditioned by the tracking enabling... Any other event tracked in PHP directly could lead to the same symptom. I'll push a PR to fix this one. Regards |
#1279 will fix this issue. |
Hi @romainruaud , |
Well I think we should release this 2.6.6 tag next week. If that's too slow for you, you can use the 2.6.x-dev branch for now, that contains already the fix. regards |
Magento Version : 2.2.5
ElasticSuite Version : 2.6.1
Environment : Production mode
Steps to reproduce
Set the option enabled to false.
Expected result
Actual result
The text was updated successfully, but these errors were encountered: