Problem: You are experiencing issues where most variant products are shown as not in stock on the Hungarian category page, despite being in stock on the Slovenian page. Additionally, input fields for personalization added with Advanced Product Fields for WooCommerce are not displaying on the Hungarian page, though they appear on the Croatian page. Solution: We recommend setting the fields to 'translatable' and then updating the product. This action should help synchronize the stock status across different languages and ensure that the input fields for personalization appear correctly on all translated pages.
If this solution does not resolve your issues 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. Should these steps not provide a resolution, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to sync WooCommerce product attributes for translation, but the translations do not appear. This issue may be due to the length and usage of the Thai script, which is decoded into much longer texts. Solution: First, ensure you have a full backup of your website. Then, follow these steps: 1. Access your Database manager (via phpMyAdmin or a plugin like DB Adminer). 2. Open your database and locate the
wp_icl_translate
table (note: your table prefix might differ). 3. Modify the
field_type
length value to 1600. 4. Make a minor change to the original product in WordPress. 5. Update the translation. If these steps seem too complex or if you're not confident in performing them, please contact us for further assistance.
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, do not hesitate to open a new support ticket at WPML support forum.
Problem: The client was experiencing an issue where links in automatically translated pages were not converting to contain the other language slug. Instead, links remained pointing to the English pages even when switching languages. Solution: We identified that the client was using a widget from an Gutenberg add-on. To resolve this, we manually registered the widget for translation by creating a custom XML configuration file. We followed the instructions provided on the WPML documentation page: https://wpml.org/documentation/support/language-configuration-files/make-custom-gutenberg-blocks-translatable/ Additionally, we modified the XML configuration using the xpath method to allow manual translation of the links.
If this solution does not resolve your issue or seems outdated, we 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 for further assistance.
Problem: If you're trying to implement a floating language switcher on your website and it stays in the footer instead of floating as intended, even after adding CSS to the Additional CSS section and clearing the cache. Solution: We recommend inserting the following custom CSS code into WP > Appearance > Customize > Additional CSS:
This should help position your language switcher correctly as a floating element on your page.
If this solution does not resolve your issue, or if it seems outdated or not applicable to your case, please check the 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. We highly recommend opening a new support ticket if the problem persists. You can do so at WPML support forum.
Problem: If you're experiencing database errors indicating a missing 'review_status' column or a non-existent 'wp_icl_background_task' table in your WPML plugin, it might be due to recent changes or migrations in your site. Solution: First, we recommend checking if the 'review_status' column exists in your 'wp_icl_translation_status' table. You can do this by logging into your database using a tool like PHPMyAdmin. If the column is missing, please ensure you have backed up your site, then run the following SQL queries to add the missing columns:
ALTER TABLE `wp_icl_translation_status` ADD COLUMN `review_status` enum('NEEDS_REVIEW','EDITING','ACCEPTED') COLLATE utf8mb4_unicode_ci DEFAULT NULL;
ALTER TABLE `wp_icl_translation_status` ADD COLUMN `ate_comm_retry_count` int UNSIGNED DEFAULT '0';
After applying these changes, verify if the issue persists.
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 continues, please open a new support ticket.
Problem: If you're experiencing issues where your translations are not being saved in WPML's Advanced Translation Editor (ATE) after translating posts from English to Dutch, and you find yourself redirected to the Posts list with the translation not saved, this might be due to a sitekey mismatch. Solution: We recommend checking your WPML account to ensure that your sitekey matches our system. Here are the steps you can follow: 1. Visit your WPML account dashboard at https://wpml.org/account/sites/ and remove the domain that is experiencing issues. 2. Generate a new sitekey and register it on your site's WPML plugin installation page, which can typically be found at
. 3. After updating the sitekey, attempt to save the translation again and check if the issue persists.
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 problems continue, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing issues with saving special characters and flags in WPML while using Elementor. The special characters and flags are not displayed correctly after being saved. Solution: We recommend switching to the previous version of the Advanced Translation Editor to resolve this issue. Here are the steps to follow: 1. Go to the top right corner of the translation editor. 2. Click the gear icon. 3. Enable the option "Use the previous version of the Advanced Translation Editor." Please try these steps and check if the special characters and flags display correctly.
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 do not hesitate to open a new support ticket at our support forum.
Problem: The user is seeing an error in the WPML Advanced Translation Editor Logs indicating a change in your site's URL. This error appears because WPML has detected a URL change and needs confirmation whether the site has been moved or copied. Solution: First, ensure you have a full backup of your site. Then, follow these steps: 1) Navigate to WPML>>Settings>>Translation Editor. 2) Select the Advanced Translation Editor (recommended) option. 3) Go to WPML>>Translation Management. 4) Check if the Site Moved wizard is showing. If it is, select the option for Changing to a New Site URL and complete the wizard steps. For more detailed instructions, please refer to the documentation on using the Advanced Translation Editor when you move or use a copy of your site.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also advise 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 content of the WooCommerce 'My Account -> Orders' page does not match between the default (Polish) and secondary (English) languages. Solution: We resolved the issue by deleting the order slug and re-translating it via WPML-> String Translation. 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: If you're experiencing a white page when trying to translate a post in Chrome, it might be due to a browser add-on. This issue occurs when the add-on interferes with the page's styles, preventing access to 'cssRules' which is necessary for the page to load correctly. Solution: We recommend deactivating any browser add-ons you have enabled. This action should resolve the issue as it appears to be linked to an add-on that modifies the page styles, causing security restrictions to block access to necessary style rules.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please open a new support ticket. 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, you can also visit our support forum at WPML Support Forum.
Problem: The client was experiencing issues with automatically translating entire pages and specific custom-coded content on their website using WPML, similar to their previous experience with the gtranslate plugin. They were particularly concerned about the main page and category pages not being translated in English and German, despite being okay in Polish.
Solution: We advised the client to ensure they had used the Automatic Translation feature correctly, as it should automatically translate all content that WPML can detect. For content that WPML does not automatically translate, such as custom-coded sections or taxonomies, the client needs to: 1. Ensure that any custom code is properly registered with WPML. For guidance on this, see Translating the Theme You Created. 2. Set themselves up as a translation manager or translator with access to all language pairs under WPML->Translation Management-> Translators. More details can be found here: Setting Up Translators. 3. For translating taxonomies automatically, follow the steps outlined in Translating Post Categories and Custom Taxonomies.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to translate the header button on your site using WPML. The translation works with subpages but not with posts. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Copy the footer template ID. 2. Go to WPML-> String Translation. 3. Scroll down and click on the "Translate texts in admin screens »" link. 4. Search for the ID. 5. Select the string. 6. Click on the "Add to String Translation" button. 7. Then click on the "« Return to String Translation" link. 8. Translate the ID into the translated templates IDs. For more detailed instructions, please check our guide on translating texts on the admin texts screen.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: If you're experiencing an issue where YouTube videos only display the cover photo on product pages when WPML Multilingual CMS is activated, even in the original language, and you're using the Woodmart theme, we can help.
Solution: 1. Navigate to WPML-> Settings-> Custom Fields Translation. 2. Click on "Show System Fields". 3. Search for and set the following fields to "Copy": -
woodmart_wc_video_gallery
-
_product_image_gallery
4. Click "Save". 5. Edit the product in the default language, make a minor edit, and update it. 6. Update its translation. After these steps, the video should appear correctly in all languages.
If the issue persists even when WPML is deactivated, it might not be related to translation. In this case, try creating a new test product in the default language with WPML activated and add the video. Check if the video displays correctly on the front end.
If this solution does not resolve your issue or seems outdated, we 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 need help translating footer elements, specifically the footer menu links, using WPML. Solution: If you're experiencing difficulties translating footer elements, we recommend following these steps: 1. Go to WPML → String Translation. 2. Enable "Look for strings while pages are rendered". 3. Navigate to the page where untranslated strings are displayed. 4. Return to WPML → String Translation and verify if the given string has been registered. 5. Translate the string. For more detailed guidance, visit our documentation on How to translate footers and headers.
Please note that 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.
Problem: The client needs to remove specific content only from the secondary languages (English and German) on a multilingual site using WPML and the Enfold theme. Solution: We suggest two methods to address this issue: 1. Use CSS to hide the content in the secondary languages. Navigate to Appearance > Customizer > Custom CSS and add the following code:
2. Manually remove the content from the secondary languages. Go to your site's backend, access "Pages", switch the language to English, and use the Avia builder to edit and remove the unwanted content. Repeat the process for German.
If this solution does not resolve your issue or seems outdated, we 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 WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
