Problem: The client is experiencing issues with translations after changing their site engine and wishes to delete their ATE (Advanced Translation Editor) translation memory. Solution: If you're experiencing this issue, we recommend following the steps outlined in the WPML forum post on deleting translation memory. You can find the detailed instructions here: https://wpml.org/forums/topic/delete-translation-memory/.
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 issue persists, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're trying to translate Gravity Forms and it's not appearing under WPML -> Settings -> Post Types Translation, and you're also unable to activate the otgs-installer-plugin version 3.1.3, here's what you need to know. Solution: 1. Gravity Forms are not registered as a post type, which is why they don't appear under WPML -> Settings -> Post Types Translation. Since you have the Gravity Forms Multilingual add-on installed, you can translate your forms via WPML -> Translation Management. Follow this guide for detailed steps: https://wpml.org/documentation/related-projects/gravity-forms-multilingual/#translate-gravity-forms 2. The OTGS Installer plugin is only necessary for installing WPML plugins. Once the WPML Multilingual CMS plugin is activated, the installer's functionality is included within WPML, so activating it separately is not required.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client is setting up a multi-domain and URL language switch for their site, with different domains and language folders for each language. Solution: We explained that it is not possible to mix different language formats; the client must choose either a domain per language for all languages or a directory for language mode. However, using subdomains like fr.houseofcufflinks.eu and de.houseofcufflinks.eu is feasible under the separate domain option. For detailed guidance on setting up different domains per language, we recommend visiting this documentation.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. We also 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. For further assistance, you can contact us through the WPML support forum.
Problem: The client was experiencing an issue where the header menu language switcher on their website only displayed one language, despite the page being loaded for the selected language. The language switcher was set to a dropdown style, and changes in WPML settings did not affect the header after clearing the server cache. Solution: We first suggested changing the language switcher from a dropdown to displaying all flags on the same line by editing the settings under WPML > Languages > Menu language switcher. Additionally, we identified that the header template had not been translated, which was likely causing the issue. We recommended translating the Elementor header template following the steps provided in the documentation: https://wpml.org/documentation/plugins-compatibility/elementor/#translating-elementor-templates.
If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
The client is experiencing an issue where job titles disappear on the frontend when switching from Dutch to English on their website. They are unsure how to ensure job titles appear correctly after language switching.
Solution:
We recommend checking and adding the missing translations for the 'Positie' field in the English version of the posts. This can be done by accessing the specific post in the WPML's translation editor. Here are the steps:
1. Go to the WordPress admin panel. 2. Navigate to the post you want to translate (e.g., Post 9332 or Post 9319). 3. Add or verify the translation for the 'Positie' field. 4. Save the changes and check if the job titles appear correctly on the frontend.
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: You are trying to send a field containing a form ID to Crowdin via WPML integration for translation, but the field does not appear in Crowdin's system nor in the source XLIFF file. However, using the WPML editor, both types of values (simple strings and form IDs) work without issues. Solution: We have adjusted the segmenter settings for your project. Please try to send another job to test and let us know if it works as expected.
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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
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. Should you need further assistance, please do not hesitate to open a new support ticket.
Problem: You are trying to access the German version of your site and encounter the error: net::ERR_CERT_COMMON_NAME_INVALID. This error typically indicates a mismatch between the domain name and the name listed on the SSL/TLS certificate. Solution: If you're running a multilingual website with WPML and using different domains for each language, you'll need to ensure that each domain has its own SSL certificate that correctly matches the domain name. This is essential to avoid common name mismatch errors.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client is trying to translate product attribute labels in WPML and encounters issues in both String translation and Taxonomy translation. The taxonomy general name is not plural and includes an untranslated English 'Product' prefix, which cannot be corrected through the UI. Solution: To remove the 'Product' prefix from the taxonomy general name and manually add the plural form of the taxonomy singular name, we recommend using a custom filter hook in WooCommerce. Here is the code you can use:
add_filter( 'woocommerce_product_attribute_taxonomy_name', 'custom_woocommerce_attribute_label_plural', 10, 2 );
function custom_woocommerce_attribute_label_plural( $taxonomy_name, $taxonomy ) {
if ( 'pa_your_attribute' === $taxonomy ) { // Replace 'pa_your_attribute' with the actual attribute taxonomy name
// Return the custom label you want
return 'Label'; // Replace with your desired label
}
return $taxonomy_name;
}
This code will change the appearance of the label on the frontend but not in the wp-admin. Alternatively, you could register the original taxonomy in English and translate it into German.
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If needed, do not hesitate to open a new support ticket.
Problem: The client was experiencing an issue where an icon continuously rotated on the admin bar where the language icon appears. The client had deleted the "icl_background_task" table as suggested, which stopped the icon from appearing but raised concerns about the necessity of the table, potential impacts on the site, and whether the table might reappear.
Solution: We explained that the rotating icon is part of the WPML's "Translate Everything Automatically" mode, indicating background tasks updating content. To address the issue: 1. Ensure you have a full backup of your site. 2. If the icon reappears and is bothersome, you might consider disabling and then re-enabling the "Translate Everything Automatically" mode, which should recreate the "icl_background_task" table without needing to manually truncate it again.
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 issue persists, please open a new support ticket.
Problem: The client is experiencing an issue where the content of the last 4 or 5 posts is not visible in their translations, although this problem does not occur with more recent posts. Solution: Try editing the original post in the WordPress Editor, save the post, and then reopen the WPML Translation Editor to see if the content appears.
If this solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, please open a new support ticket. We also 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. For further assistance, you can contact us through the WPML support forum.
Problem: You are trying to translate templates on your site using WPML and the newspaper theme. Although you have translated the Cloud library templates, they are not displaying correctly on the front end. Solution: We recommend checking the theme options for each language. Go to Newspaper > Theme Panel, switch the language in the top admin panel, and ensure that the correct header for the selected language, such as Polish, is active. This adjustment should resolve the display issue.
If this solution does not apply to your case, or if it seems outdated, please open a new support ticket. We also 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. For further assistance, you can contact us directly through the WPML support forum.
Problem: You are trying to translate labels, slugs, and attribute taxonomy options using WPML, but the translation interface does not consistently show the WPML default language (German) as the source. Instead, the globe symbol appears under the English flag, making it untranslatable. You have to manually change the language to German, and the label text is shown in English, not the source language. Solution: The default language in WordPress is typically English, depending on the language in which WordPress was installed. To resolve this issue, you need to adjust the source language for the taxonomy labels and strings. This adjustment will enable you to create your translations effectively. It is crucial to ensure that especially the slug is translated, regardless of the source language displayed.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client is facing an issue where editing a link or text in the default language results in losing the translation in another language, requiring retranslation of the entire content. Solution: We recommend using the 'Don't update translation' button to prevent translations from being overwritten when making changes to the original language. Here are the steps to follow: 1. Make changes to your page in the original language. 2. Click the 'Don't update translation' button in the language sidebar. 3. Verify if the translations remain unchanged, as this behavior is expected.
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 at WPML support forum for further assistance.
Problem: You are trying to translate the Porto theme product filters to Bulgarian, specifically the 'by size' and 'by color' filters, and you want to correct the translation of the word 'by' which was incorrectly translated to 'по'. Solution:We have a workaround.
Go to WPML > String Translation and translate the new strings.
To correct the translation of the word 'by', you can adjust it directly in the WPML String Translation interface. Access it via this link: WPML String Translation.
Please note that this solution might be outdated or not applicable to your specific case. If these steps do not resolve your issue, 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
