Problem: If you're trying to manually change the slug of a translated page and are having trouble doing so with your current settings. Solution: We recommend switching your setting to 'Translate'. After making this change, perform a minor edit in the original language to prompt the translation requirement. Then, access the translation editor where you will find the option to translate the slug. For detailed guidance, visit Translating Page Slugs.
Please note that this solution might not apply if it's outdated or not relevant 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 this solution does not resolve your issue, please open a new support ticket.
Problem: If you're experiencing issues where ACF Field Groups are set to 'untranslatable' in WPML -> Settings -> Post Type Translation, but they still appear in the Translation Management post type dropdown filter, this might be confusing. Solution: We would like to clarify that setting the ACF Field Group to 'Not Translatable' in WPML settings means that the entire field group itself cannot be translated using WPML. However, the field labels and placeholders within these groups remain active and translatable. These elements appear in the dropdown to allow you to send field labels and titles for translation through the Translation Management or String Translation, but not the entire field group itself. If you set the field group to 'Translatable', then you can send the entire field group, including all related information and settings, for translation.
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 feel free to open a new support ticket at WPML support forum for further assistance.
Problem: The client is facing an issue where the menu links in the French version of their site, which uses Elementor for the header and not a WordPress menu, still point to the URLs in the English version. Solution: We recommend translating the URLs when translating the header. This can be done using the Advanced Translation Editor. For detailed steps, please refer to the documentation on how to use the Advanced Translation Editor.
Please 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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client experienced an issue where after enabling automatic translation for product variations, the translation queue and used credits increased significantly. They also faced a problem where setting product variations to 'Not translatable' resulted in the original product losing all its variations after translating a test product. Solution: We advised the client to set global attributes to 'Translatable' but not to enable automatic translation for them. To manage the translation queue, we recommended the following steps: 1) Switch the translation mode to 'Translate what you choose' at WPML > Settings > Translation Mode. 2) Go to WPML > Translation Management > Jobs to cancel unnecessary jobs using the filters. 3) Refresh the page to ensure the jobs were canceled. 4) Re-enable 'Translate everything automatically' and choose whether to translate existing untranslated content or only new content. For translating global attributes, they should be done at WooCommerce > WooCommerce Multilingual > Attributes. Custom attributes declared directly on each product will be translated automatically if the product is translated.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket for personalized assistance.
If this solution does not apply or is outdated, or if further assistance is needed, 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 issue persists, please open a new support ticket in the WPML support forum.
Problem: The client wanted to know how WPML's automatic translation feature handles product featured and gallery images, specifically if it duplicates these images in the database, and how to prevent this to avoid bloating the
wp_posts
and
wp_postmeta
tables.
Solution: We explained that WPML's "WPML Media Translation" module manages media duplication across translations. By default, WPML duplicates media entries for each language in the database but does not duplicate the actual image files. To prevent automatic media duplication: 1. Navigate to WPML -> Settings. 2. Scroll to the 'Media translation' section. 3. Uncheck the options shown in the provided screenshot and save the changes.
We also clarified that it's not possible to have a single image load in the translation without duplication unless custom coding is implemented. If the client needs a custom solution, we suggested hiring a certified developer experienced in customizing WPML from https://wpml.org/contractors/.
Please note that this solution might be outdated or not applicable to your case. If so, 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 our support forum.
