Problem: You are using the JetSmartFilters plugin to generate filters for JetEngine custom fields, but the filter labels are not being translated into secondary languages. Solution: If you're experiencing this issue, we recommend checking if the filter was created in the correct language. If not, you should delete it and recreate it in the correct language. Alternatively, you can edit the existing filter, add the correct filter labels in the correct language, and then update the filter in both languages.
This solution might be irrelevant if it's 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 issue persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing 404 errors on WooCommerce product links when accessed from the shop page. Additionally, there is a URL structure issue where the language prefix is duplicated, and the client wishes to have consistent URL structures across different languages. Solution: 1. To address the 404 errors: - Navigate to Settings > Permalinks in your WordPress Dashboard and resave the structure without making any changes. - Go to Products > All Products, switch to the English language using the language switcher at the top bar of the Admin, locate the product showing a 404 error, and click on "Quick edit". - Ensure that the 'Status' is set to 'Published'. - Clear the site's caches. 2. Regarding the URL structure issue, it is not possible to have identical URL structures in different languages due to the requirements of the WPML to pass language information. WPML offers three options for Language URL Formats, which you can explore here: Language URL options.
If these solutions do not resolve your issues or if they seem 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 need to translate the 'before' fields on a list widget in Elementor but are unable to find a solution online. Solution: If you're experiencing this issue, we recommend translating your pages manually using the WordPress and Elementor Editor. Follow the steps described in the documentation. It's important to note that plugins and themes must be prepared for translation, which involves registering texts so they can be identified by translation software like WPML. Unfortunately, the specific field you mentioned is not registered, which limits direct WPML intervention.
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 is unable to translate the content of a page that uses an Elementor template; only the title appears in the translation interface. Solution: We recommend translating Elementor templates separately. For detailed instructions, please follow our guide on how to translate templates with WPML: Translating Elementor Templates with WPML
If the content is part of the standard page, it should be translatable when translating the page itself. If the content is part of the Elementor template, it will be translatable when you translate the template. If you encounter issues where only the page title is available for translation, try the following steps:
1. Make a minor edit to the page in the default language and update it. Then, try accessing the translation again to see if the issue is resolved. 2. Check the Elementor modules used on the page to determine if they are native to Elementor or if they come from the theme or a third-party plugin.
If the solution provided here is not applicable due to it being outdated or not relevant to your specific case, we encourage you to open a new support ticket. We also 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. If further assistance is needed, please contact us through the WPML support forum.
Problem: The client updated all plugins and noticed that when visiting the translated page with Elementor, the field lost the link to the original Advanced Custom Fields (ACF).
Solution: 1. We asked if the issue was present in the translated version of the page or also in the original one. 2. We suggested increasing the WordPress memory limit as WPML requires a minimum of 128MB. The client should add the following code to the
3. We identified that the "Field Group" Custom post type was set as "translatable", which it should not be. To resolve this, the client should: - Create a site backup. - Delete the translated language field groups in ACF, leaving only the default language ones, and remove them permanently. - Set the "Field Group" Custom post type to NOT TRANSLATABLE in WPML > Settings > Custom post type translation. - Ensure the field group's translation preferences are correctly configured as per our guide: Translate sites built with ACF. - Resend the page containing the Elementor widget configured with ACF from WPML > Translation management.
If these steps do not resolve the issue or if the solution is outdated or not applicable, we recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed. If the problem persists, please open a new support ticket for further assistance.
