Problem: The client is experiencing an issue where WPML automatic translation gets stuck for one specific page. The translation status continuously shows 'Automatic translations are in progress' and never completes. Despite attempts to cancel and resend the translation, and even duplicating the page with a new post ID, the problem persists. This issue seems isolated to a single translation job. Solution: We suspect that this issue might be related to one of the Elementor Addons, as each custom Elementor Widget requires proper XML configuration for WPML to handle translations effectively. We recommend taking a backup of your site and then installing the latest versions of our plugins. The WPML 4.9 update includes a new feature in WPML that automatically recognizes Custom Elementor Widgets for translations. After updating, please edit the original content, save the page again, and resend it for automatic translation. If the problem continues, it 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 issue persists, please open a new support ticket for further assistance at WPML support forum.
Problem: You are using WPML for automatic translations on your website and want to prevent the post name (product name) for a custom post type called 'products' from being automatically translated. Currently, the product names are being translated automatically, and you have to manually revert them to the original names. Solution: We recommend implementing a PHP workaround to exclude the title from translation for your specific custom post type. You can find an example of such a code here. Please use this code as a starting point and customize it to fit your needs. Ensure to test the code on a staging site before applying it to your live site. If you require further customization, consider hiring a developer or a WPML contractor from our list of recommended contractors.
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 this does not resolve your issue, please open a new support ticket.
Problem: In post type posts, taxonomy tags are all automatically translated, but 99% of them are just copies of the English version. Solution: If you're experiencing this issue, we recommend you navigate to WPML > Taxonomy Translation, select the Tags Taxonomy in the dropdown menu, and manually edit the translations. If you prefer to have them all automatically translated, you can follow the technique outlined here: https://wpml.org/faq/how-to-translate-all-taxonomy-terms-at-once/. Please ensure to delete all the existing taxonomy translations before applying this method.
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.
Problem: The client is experiencing issues with WPML on their site. Specifically, the translated values of custom fields are not showing in the default WordPress editor, despite being set to translate in the settings. Additionally, registered shortcodes in WPML > Settings > Custom XML Configuration are not automatically translated. Solution: For the custom fields issue, we recommend the following steps: 1. Navigate to WPML > Translations. 2. Select all posts checkboxes. 3. From the Bulk Actions dropdown menu, select "Approve translation reviews". 4. Apply this action to all posts. After these steps, the translated fields should be visible in the WordPress editor for secondary languages. It is crucial to use only one editor consistently; if you have used WPML's translation editor, avoid editing directly using the WordPress editor and vice versa. For the shortcode translation issue, we have created a separate support ticket to address this specifically. You can follow the progress and find solutions here: https://wpml.org/forums/topic/split-taxonomy-translations/edit/
Please note that the solution provided 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 issue persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with WPML on their site. Specifically, the translated values of custom fields are not showing in the default WordPress editor, despite being set to translate in the settings. Additionally, shortcodes registered in WPML > Settings > Custom XML Configuration are not automatically translated. Solution: For the issue with custom fields not displaying in the default WordPress editor, we recommend checking our documentation on enabling text translation for themes not compatible with WPML, which can be found here: https://wpml.org/documentation/support/enabling-text-translation-for-themes-not-compatible-with-wpml/. Regarding the shortcodes not being automatically translated, it's important to note that our technical support primarily covers default WPML functionalities and not custom code. If these solutions do not resolve the issues or if the documentation does not cover your specific case, we highly recommend opening a new support ticket. Additionally, 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.
