ericaG-7

Problem:
The client reported that the multicurrency feature of WPML was not functioning correctly. Despite various settings and configurations, including deactivating all plugins and switching to a default theme, the currency switcher did not appear or function as expected. The client also noted that the currency did not change appropriately when tested under different conditions, such as in incognito mode or with different billing addresses.

Solution:
We investigated the issue and found that the multicurrency feature was functioning correctly when cache was disabled. The problem arose due to the caching mechanism interfering with dynamic currency switching. We recommended:
1. Excluding WooCommerce-related pages (like cart, checkout, and account pages) from being cached.
2. Considering a caching solution that supports dynamic currency switching, or configuring the current caching setup to exclude certain pages.
For more details on caching compatibility with WPML, visit https://wpml.org/plugin-functionality/caching/.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific setup, please open a new support ticket. We also highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. For further assistance, you can contact us directly through the WPML support forum.

Problem:
The client reported that after translating their site using WPML, the styling settings in a Global Section (Cover) from the Rey theme for the headers of the categories were lost. These headers are built with Elementor and use a Dynamic title to generate the title. Although the titles were translated, the styling did not carry over, even after resaving/republishing in both English and Portuguese.
Solution:
We recommended editing the Portuguese category where the options for the cover are located at the bottom. We provided a screenshot for guidance and made the change for one specific category as a demonstration, which corrected the problem on the front end. We asked the client to confirm if the issue was resolved.

If this solution does not apply to your case, or if it seems outdated, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should the problem persist, please open a new support ticket.