Problem: If you're using Elementor and JetSmart Filter to display content on a page and notice that custom fields such as 'departure date' and 'performance index' revert to the original language (French) when filters are applied or when navigating to the next page, this issue might be familiar to you. Solution: We recommend making a full backup of your website before proceeding with any changes. First, ensure that the page and its translations are fully published. Then, adjust the settings of your filters from 'Ajax' to 'Page reload'. After making this change, update the translation of the page. If the issue persists, you might need to translate the page using a different method, which can be found here: Using Different Translation Editors for Different Pages. Please try these steps and let us know if they resolve the issue. If not, we will escalate this to our second-tier support.
Note that this solution might be outdated or not applicable to your specific case. We 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. If the problem persists, please open a new support ticket at WPML Support Forum.
Problem: The client was experiencing issues with translations and filter functionality on their multilingual website. Specifically, when a filter was applied, some listings lost their translation, and the 'Year of Departure' filter was not displaying the correct results in translated languages. Solution: 1. We advised the client to ensure that the custom field used in the filter, 'Départ le', is correctly translated and set up in all required languages. This involves editing the field in the page template and ensuring the correct language setting is applied. 2. For the 'Year of Departure' filter, we recommended setting the correct filter in the English language version of the page and ensuring that posts are translated independently to maintain accurate language information across different languages.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with JetSmartFilter options not appearing on translated pages of their website. The filters display names but no options, except for filters like 'age' where values are numeric and do not require translation. Solution: 1. Ensure that both the WPML plugin and the JetSmartFilters plugin are updated to the latest versions. Instructions for updating WPML can be found here. 2. Follow the documentation for translating taxonomies with JetEngine, which can be accessed here. 3. Manually adjust the translation for the second language by setting the correct taxonomy and term for each filter. An example of how to do this can be seen here. 4. Select the option to show also empty terms/taxonomy in the filter settings. 5. Ensure that posts are translated into the target language as the filters will not work if there are no posts to display or filter.
If these steps do not resolve the issue, or if the solution seems outdated or irrelevant to your case, we 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. If the problem persists, please open a new support ticket here.
Problem: The client installed WPML on their website, and there was a conflict between the WPML String Translation plugin and Elementor, causing the content of a page not to display in the live version. Solution: We requested the client to provide debug information and enable debug mode by adding specific code to their wp-config.php file. After reviewing the site, we identified that the issue was due to a specific bug with an image in the 6th item of the toggle widget on the page. We resolved the issue by removing and re-adding the image. We also provided a video demonstration of the fix process, which can be viewed here: https://www.loom.com/share/7782a06227044242ac06f1c59b2d576b.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we 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. If further assistance is needed, please open a new support ticket at our support forum.
