Problem: The client is using WPML with WooCommerce and the WooCommerce Side Cart Premium plugin. They have set a threshold for adding free products in the main language (PL) and want to set different thresholds for other languages (EN, DE, CZ) with different currencies. Solution: We recommended checking if the threshold setting is stored as a custom field or within the plugin options. If it's a custom field, the client can set it to 'translate' using the guide on Translating Custom Fields. If it's a global plugin option, the client should register it for translation following the instructions on Finding Strings that Don't Appear on the String Translation Page. The client successfully found the threshold value under WPML → String Translation → Translate texts in admin screens, registered it for translation, and set different values for each language.
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 further assistance is needed, please open a new support ticket.
Problem: You are experiencing a connection error with both DeepL and Google translation services, and after removing and re-adding the WPML registration, your account does not recognize your translation credits. Solution: We have verified that the WPML.org account was credited with 90,000 translation credits. We recommend checking your account to ensure the credits are properly displayed and available for use. You can manage and verify your credits at https://wpml.org/account/manage-credits/.
If this solution does not resolve your issue or seems outdated, or if it does not apply 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 directly through our support forum at https://wpml.org/forums/forum/english-support/.
בעיה: הלקוחה נתקלה בבעיה שבה תוכן משדה חזרה (Repeater Field) לא מועתק לשפות המשניות בעת השימוש באפשרות 'copy once'. הבעיה התרחשה גם בעמוד האפשרויות וגם בקבוצת שדות רגילה.
פתרון: במקרה של שדה חזרה בעמוד האפשרויות, יש להגדיר את השדה ואת השדות שבתוכו ל-'copy once'. בתרגום הראשון, הערכים אמורים להיות מועתקים לשפה השניה וניתן לשנותם שם. לאחר מכן, שינויים בשפה הראשית לא יועתקו. במקרה של קבוצת שדות רגילה, יש לעקוב אחר ההנחיות במדריך הזה: מדריך לתרגום שדות מותאמים אישית
בנוסף, הבעיה נפתרה בגרסה 2.2.0 של ACFML. יש לעדכן את כל התוספים לגרסאות העדכניות ביותר.
אם הפתרון הזה אינו רלוונטי עבורך, או שהוא כבר לא עדכני, אנו ממליצים לבדוק את הבעיות הידועות בדף הבעיות הידועות, לוודא את גרסת התיקון הקבוע, ולאשר שהתקנת את הגרסאות העדכניות ביותר של הערכות והתוספים. אם עדיין נתקלת בבעיה, אנא פתח כרטיס תמיכה חדש.
Problem: El cliente experimenta cargos repetidos por créditos de traducción en WPML cada vez que realiza pequeñas ediciones de contenido, como puntuación o precios, en su sitio multilingüe. Esto se debe a que WPML considera cada cambio, incluso menor, como un nuevo segmento a traducir automáticamente, lo que resulta en un uso excesivo de créditos. Solution: 1. Se explicó que WPML cobra créditos solo por las palabras que se envían a traducción automática y que cualquier cambio en el texto, incluso menor, puede hacer que el sistema envíe la frase entera para traducir de nuevo. 2. Se sugirió minimizar el uso de créditos haciendo solo los cambios mínimos necesarios antes de enviar contenido a traducción automática y considerar la edición manual de traducciones para cambios menores. 3. Se recomendó revisar la cantidad de créditos que se van a usar antes de confirmar la traducción automática para asegurarse de que no se envían más palabras de las necesarias. 4. Se proporcionaron enlaces a la documentación de WPML sobre cómo la memoria de traducción no cobra por segmentos previamente traducidos (https://wpml.org/documentation/translating-your-contents/how-wpml-keeps-track-of-your-translations/) y el uso del glosario para traducciones precisas (https://wpml.org/es/documentation-2/traducir-los-contenidos/editor-de-traduccion-avanzado/como-utilizar-el-glosario-para-traducir-con-precision/). 5. Se aconsejó dividir los textos en elementos separados para que cambios en uno no afecten la traducción del otro.
Si esta solución no resuelve tu problema o parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins.
Problem: The client was unable to save or translate the Cash on Delivery (COD) payment title and description in WooCommerce settings. Changes reverted after saving, and the required string was not found in WPML String Translation even after scanning the WooCommerce plugin.
Solution: 1. Update WPML Plugins: - Update WPML Multilingual CMS to version 4.9.0. - Update WPML Multilingual & Multicurrency for WooCommerce to version 5.5.4. - Update WPML String Translation to version 3.5.0. - Navigate to Plugins → Add New Plugin → Commercial tab and click on Check for updates.
2. Scan WooCommerce for Strings: - Go to WPML → Theme and plugins localization. - Scroll down to the Strings in the plugins section. - Select the WooCommerce plugin. - Click on Scan selected plugins for strings.
3. Translate the COD Texts: - After the scan is complete, go to WPML → String Translation. - Search for the exact title or description text you are trying to translate for your COD option.
If these steps do not resolve the issue, it may be necessary to check for interference from custom or third-party plugins or theme functions, and confirm if strings for payment gateways are correctly registered in String Translation. If needed, manually register the strings and review WPML string registration logs or debug.log for errors related to WooCommerce payment settings.
If the problem persists, 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 solution provided here is outdated or not applicable to your case, please open a new support ticket at WPML support forum.
Problem: The client is attempting to use a custom translation service with WPML, but it does not appear in the Translation Services list. They have set
WPML_CUSTOM_TRANSLATION_SERVICE_URL
in wp-config.php to point to their custom Translation Proxy API, which implements the WPML Translation Proxy API (JSON:API). Despite this setup, the custom service is not visible under WPML → Translation Dashboard → Translation Services. The client also noted that the “Enable other translation services” button is not visible under WPML → Support → Troubleshooting, and they do not have a Preferred Translation Service set in their wpml.org account.
Solution: We informed the client that currently, there are no plans to make custom translation services available outside of the Partner program. As alternatives, we recommended considering the following options:
Translation Hub: A centralized interface for managing translations and translators.
Automatic Translation: Built-in machine translation with flexible pay-as-you-go options.
We also mentioned that we will soon announce the PTC (Private Translation Cloud) Partnership program for Agency accounts, which will provide benefits for those accounts regarding site translations.
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 further assistance is needed, please open a new support ticket.
