Problem: If you're experiencing issues where categories are not showing in the sidebar for certain languages on your site, it might be due to outdated plugins or themes. Solution: We recommend taking a backup of your site and database first. Then, update all plugins and the theme you are using. If the problem persists after updating, please contact us for further assistance.
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 you still need help, feel free to open a new support ticket at WPML support forum.
Problem: The client is using WPML for the first time to translate products from Slovenian to Croatian and is unsure how to automatically translate categories and their descriptions before translating the products. Additionally, the client is facing issues with the word count for translations being higher than expected, leading to a shortage of translation credits. Solution: We recommend translating categories automatically along with the products. After translating the products, you can synchronize the taxonomies at WPML > Taxonomy Translation. If you prefer to translate all categories in one step, you could assign all categories to one product and send this product for automatic translation. For syncing issues, a sync button will appear at the bottom of the section inside WPML > Taxonomies Translation when selecting a taxonomy to translate.
For importing existing translations, use the "WPML Export & Import" addon instead of the outdated "WPML All Import". You can download this addon under Plugins > Add new on the "Commercial" tab. Ensure to first import categories before posts if you're also importing categories. Guide: https://wpml.org/documentation/related-projects/wpml-export-and-import/
Regarding the word count issue, our development team is aware and working on a solution. The estimated word count might be 2-3 times higher than expected due to the current bug.
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. We highly recommend opening a new support ticket if problems persist. For further assistance, visit our support forum: https://wpml.org/forums/forum/english-support/
Problem: The client reported an issue where the admin received an order confirmation email in the HR (Croatian) language, but the customer received the same email in SI (Slovenian), despite all strings being translated correctly in WPML. Solution: We first recommended testing with only the default WordPress theme and essential plugins (WooCommerce and WPML) to ensure that the issue wasn't caused by any other plugin or theme conflicts. Upon testing, it was confirmed that the HR email was sent correctly to the customer under these conditions. Further investigation revealed that the issue was due to the use of a custom string added in the email content in SL (Slovenian), which was not translated. We advised the client to either translate these custom strings via WPML > Translation Management or to delete the custom strings and revert to using the default provided strings.
If this solution does not resolve your issue, or if it 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client was unable to access certain translation features in WPML after an update, specifically encountering issues with translating taxonomies and products. Additionally, the client could not add a translation manager as no user was found. Solution: We recommended the following steps to resolve the issue: 1. Ensure a complete site backup is taken. 2. Open the
1
functions.php
file of your theme in a code editor. 3. Insert the following function to expand translation manager capabilities:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
/**
* Expand translation manager caps to be able to translate taxonomies
4. Save changes to the file. **** Important! Please make a full site backup (files and DB) before you proceed with these steps**** After applying these changes, check if the issue with the 'Translate Products >' button is resolved.
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. If issues persist, please open a new support ticket.
Problem: The client is experiencing issues with partially untranslated WooCommerce emails in Spanish, despite having translations available in the String Translation. The client updated WPML and modified the TranslateWpmlString.php file, but the issue persisted. Solution: 1. We recommended updating the WPML plugins and add-ons to the latest version, specifically to version 4.7.2, to benefit from the latest bug fixes and improvements. Instructions for updating can be found at http://wpml.org/faq/install-wpml/. 2. We suggested applying a workaround for a known issue related to WooCommerce order update emails containing mixed language texts, which can be found at https://wpml.org/errata/wc-order-update-emails-may-contain-mixed-language-texts/. 3. After applying the workaround, it is crucial to double-check that all strings are correctly translated in the String Translation. 4. If the issue persists, we advised creating a staging site and performing a step-by-step isolation test by deactivating and reactivating plugins and themes to identify the culprit. 5. As a last resort, downgrading the WPML plugins by manually uploading the plugin folders or restoring a backup with a previous version was suggested.
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 at WPML support forum.
Problem: The client is experiencing issues with strings not translating unless the 'AUTO REGISTER STRINGS FOR TRANSLATION' is enabled. When this option is disabled, the strings do not translate. Solution: The issue stems from the Give Plugin not loading its text domain correctly, which prevents WPML from translating the strings. This problem is due to changes in how text domains are loaded in the latest major WordPress release. We recommend contacting the Give Support Team to inquire if they are aware of this issue and to check if an update is planned to resolve it.
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 open a new support ticket with us at WPML support forum.
Problem: You are experiencing issues with product translations being automatically duplicated and published when you duplicate the original product using the WooCommerce duplication option. Solution: We recommend using a different plugin that handles the duplication process without affecting other languages. Specifically, you can try using the Duplicate Page or Duplicate Post plugins. These plugins provide more control over the duplication process and should prevent automatic duplication across different languages.
If this solution does not resolve your issue or seems outdated, please check the related known issues 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 further assistance.
Problem: The client reported that the featured image and attribute images were not displaying on the translated version of a WooCommerce product, although they appeared correctly in the original version.
Solution: We identified two separate issues causing the image display problems:
1) For the product images: - Open the product for editing in the default language. - Switch to Croatian from the top admin bar to load the translation within the WordPress editor. - Add or update the product images (featured and gallery) and then update.
2) For the variation images:
- First, we adjusted a setting in WPML -> Settings -> Custom Term Meta Translation for the field "st-image-swatch" from 'don't translate' to 'Copy'.
- Navigate to Products -> Attributes in the default language. - Click "Configure terms" for the attribute "Barva". - After loading the terms, switch to Croatian from the top admin bar. - Click "Quick edit" for a term missing the image. - Simply click "Update Barva" without making any changes to the term. Repeat the last two steps for each term needing this fix.
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. If needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client reported an issue with the Croatian version of a WooCommerce product page showing an ERR_TOO_MANY_REDIRECTS error and having a URL with double slashes. Additionally, the featured image and attribute images were not displaying on the translated product page.
Solution: We advised the client to first take a full backup of their site and database. The steps included: 1) Checking in String Translation for the problematic URL and correcting it for the Croatian translation. We also suggested running the process to scan and auto-adjust links under WPML -> Settings -> Translate link targets. 2) Deactivating all plugins except for WPML, String Translation, WooCommerce, and WCML to check if the issue persists. 3) Switching to a standard theme like 2024 or 2021 to rule out theme-related issues. 4) Re-activating plugins one by one to identify any conflicts, and then switching back to the original theme to check for issues.
Alternatively, client found that plugin SEO press was causing the url to look like this, resetting the plugin fixed the issue.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant, 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 persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing issues with untranslated strings in the cart and checkout sections of their WooCommerce site after updates, despite using WPML's string translation features. Solution: We replicated the client's site in a local environment to investigate the issue. It was found that the untranslated strings are part of the WooCommerce blocks, dynamically served and not standard translatable strings in the database. After further investigation, it was determined that these strings are added through JavaScript, which WPML does not natively support for scanning and translating. We recommend using the "Loco Translate" plugin as a workaround to handle these translations. This plugin can be used alongside WPML to translate strings that are managed through JavaScript within blocks.
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. If further assistance is needed, please open a new support ticket at our support forum.
Problem: The client is unable to translate the WooCommerce integration on the checkout page, even though it appears translated in WPML's String Translation. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Edit the
// Ensure translation here 3. Save the file. 4. Navigate to WPML -> String Translation. 5. Enable the "Auto register strings for translation" option. 6. Visit the checkout page in the default language. 7. Disable the option. 8. Search for the string in String Translation. 9. You should see it twice, please translate both strings. 10. Clear the cache and check the translated checkout page.
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: In the Spanish version of a multilingual webshop, the client is unable to set display conditions in Elementor for the Spanish category 'JUEGO TABLAS'. Despite the taxonomy hierarchy being synchronized, only Slovenian categories are available for selection. Solution: We discovered that the issue was due to the use of an outdated 'Products' widget in Elementor, which was deprecated since version 4.1.3. We recommended switching to the 'Products Grid' widget. After making this change, the client should verify if the translated archive displays correctly by checking the front end.
If this solution does not resolve the issue or seems outdated, we highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket.
Problem: The client is unable to see the URL ACF field for translation on their website. Solution: We identified that the URL type field was set to 'Copy' under the 'Same fields across languages' option in the ACF groups. To enable translation for this field, the client needs to switch the translation option of the 'Dodatno mize' field group to 'Expert' mode. For more details on default settings and how to switch to Expert mode, please refer to the following documentation links:
If this solution does not resolve your issue or 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.
당사는 웹사이트와 서비스를 최적화하기 위해 쿠키를 사용합니다.
사용자의 동의를 통해 탐색 행동과 같은 데이터를 처리할 수 있습니다.
동의하지 않으면 일부 기능에 영향을 미칠 수 있습니다.
기능적
항상 활성화
웹사이트가 올바르게 작동하고 통신하는 데 필요합니다.
기본 설정
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
통계
당사는 이를 사용하여 사이트의 통계를 분석합니다.
수집된 정보는 완전히 익명으로 처리됩니다. 익명 통계 목적으로만 사용되는 기술적 저장 또는 접근입니다. 소환장, 인터넷 서비스 제공자의 자발적인 협조 또는 제3자의 추가 기록 없이, 이 목적으로 저장되거나 검색된 정보는 일반적으로 귀하를 식별하는 데 사용할 수 없습니다.
