[Resolved] Visitor can not add to cart translated product (Woodmart theme)
This thread is resolved. Here is a description of the problem and solution.
Problem: The client reported an issue where a visitor (not logged in) adds a translated product to the cart, but the default language product is added instead. This problem occurred after making changes to the visibility of the English language and the product translation settings in a Woodmart theme environment.
Solution: We resolved the issue by enabling the "Language filtering for AJAX operations" option in WPML > Languages. This solution worked for both logged-in and logged-out users, ensuring that the correct language product is added to the cart. We confirmed that enabling this option should not cause any performance issues, so no further troubleshooting is necessary.
We found out that if we enable Language filtering for AJAX operations option in WPML - > Languages the issue is solved. We would like to know what this option does and if enabling it causes our site to slow down.
I apologize for any confusion. Since you've indicated that the problem has been resolved by enabling the "Language filtering for AJAX operations" option in WPML > Languages, we consider the matter closed. Is there any additional information or assistance you are seeking from our 2nd Tier Support team?
Ok, I can understand that but how can you expalin the fact that that we found the solution on our own by chance, just by checking and unchecking options and you, a wpml supporter, were not able to find this out yourself since you were given permition to trubleshoot in a demo site? Why did we have to wait all this days for this?
I want to extend my apologies once again for the oversight. I acknowledge that I overlooked that option in WPML. It's intriguing that it works correctly when logged in but not when logged out, unless you enable the "Language filtering for AJAX operations" option.
I have already submitted a report to our second-tier support team for investigation. However, since the problem has been resolved by enabling the "Language filtering for AJAX operations" option, the report has been closed. Additionally, enabling this option should not introduce any performance issues, so there's no need for further troubleshooting.
If you have any additional concerns or issues that require attention, please don't hesitate to let me know, and I will create a separate ticket to ensure they are addressed properly.
