. Solution: We recommended removing the custom URL assigned in the ACF "Imóveis" custom URL option. This change allows the URL to use the slug configured in WPML. We asked the client to try this solution and inform us about the results.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are experiencing an issue where after translating an archive page created with Elementor using WPML, you are redirected to an incorrect URL instead of the expected translated page. Solution: We recommend completing the translations for your 'imoveis' Custom Post Type (CPT) posts. You can do this by accessing your WordPress admin panel at https://lattitude.sitedev.pt/wp-admin/edit.php?post_type=imovel&lang=pt-pt&admin_bar=1. Once the translations are complete, the English Archive page for 'imoveis' should be generated automatically. Please check if this resolves the issue.
If this solution does not apply to your case, or if it seems outdated, 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 do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You are unable to translate the content of the Search Placeholder and Generic Text in JetEngine using WPML. Solution: We recommend adding the following XML code to WPML > Settings > Custom XML Code (tab):
After adding the code, please follow these steps: 1. Go to your Dashboard > Pages. 2. Open the edit screen of the original page and make a small change, such as adding an extra blank space at the end of a sentence or paragraph. 3. Save the changes. You should now see a circular arrow beside the second language links, indicating that an update is required. 4. Edit the translation again and ensure it is saved up to 100% translated. You should now be able to see the translated placeholders.
If this solution does not resolve your issue or seems outdated, 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.
Problem: The client reported that the filter popup does not open on the products page in the English language. Solution: We edited the product template in the English language and located the 'Icon Box' widget. We then navigated to the 'Advanced' settings and pointed the Jetpopup to the correct filter popup. We recommend you try the same steps if you're experiencing this issue.
Please note that this solution might be outdated or not applicable 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 at WPML support forum.
Problem: The client is using WPML with the Husky Products Filter Professional and wants to maintain active filters when switching languages on their site. However, when switching languages, the URL changes and the active filters are lost. Solution: According to the plugin author, this is a feature request and not a bug. It is recommended to contact the plugin author to see if they can address this feature request.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket.
