Problem: The client needed help translating custom fields such as 'Experience', 'Fresh', and 'Year' from the WP Job Board plugin, which were not registered in a way that WPML could translate them due to compatibility issues. Solution: We recommended creating the same custom fields again for the secondary language and using the manual translation method to manually assign the translated fields to the translated jobs, while keeping the original fields assigned to the default language jobs. Additionally, we suggested configuring WP Job Board so that empty field values are not displayed to avoid showing duplicate fields. We also advised contacting the plugin author for potentially better multilingual support and checking the list of officially compatible plugins at https://wpml.org/plugin/.
If this solution does not resolve your issue or seems outdated, 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 is unable to translate the words "Country" and "City" on their website, which is caused by custom JavaScript code added via the WPCode plugin. Solution: 1. Temporarily disable the custom code added via WPCode and verify that translations work correctly. 2. Contact the developer who created the custom script and ask them to make the JavaScript strings translatable using WordPress localization functions. For guidance on how to localize scripts, visit the WordPress documentation: https://developer.wordpress.org/reference/functions/wp_localize_script/ Since custom JavaScript implementation is outside our support scope, the developer of the code will be the best person to adjust it.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problema: Si estás intentando importar traducciones de un documento PDF a tu sitio web multilingüe en WPML, es importante saber que WPML no puede procesar archivos PDF directamente porque necesita datos estructurados y segmentados. Solución: Debes convertir el PDF a un formato compatible como XLIFF, CSV o XML utilizando herramientas externas o un flujo de trabajo personalizado. Asegúrate de que la conversión preserve o te permita añadir la estructura y los identificadores necesarios (como el slug o ID de la página, el SKU del producto, etc.) para vincular correctamente el contenido en búlgaro con el contenido existente del sitio.
Si esta solución no resuelve tu problema o si la información proporcionada se ha vuelto obsoleta, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte.
Problem: The client is trying to prioritize the display of translated content on their multilingual site, but is unsure how to configure WPML to achieve this specific behavior. Solution: We explained that with the current features available in WPML, it is not possible to customize the content display to prioritize translated content as the client desires. The client can either: 1. Display only translated content. 2. Enable the fallback mode to show untranslated content as well. Both options will result in the content being displayed in the same manner as it currently appears on the site.
If this solution does not resolve your issue or seems outdated, we recommend checking the related known issues and verifying that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
Problem: Der Kunde möchte im Hauptmenü einen Sprachschalter einrichten, bei dem nur eine Flagge angezeigt wird und beim Hover über das Menü die anderen Sprachvarianten mit Flagge und Namen erscheinen. Der Name der Sprache sollte dabei nicht direkt in der Navigation sichtbar sein. Solution: Der Kunde hat das Problem mit Custom-CSS gelöst, indem er zuerst alle Titel ausblendet und dann die Punkte des Submenüs wieder einblendet. Falls diese Lösung für Sie nicht relevant ist oder veraltet erscheint, empfehlen wir, die bekannten Probleme zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Sollten weiterhin Probleme auftreten, zögern Sie nicht, ein neues Support-Ticket zu eröffnen. Besuchen Sie dazu unser Support-Forum.
Problem: If you're experiencing a fatal error when using PHP 8 with the WPML Multilingual & Multicurrency for WooCommerce plugin, and the error disappears when the plugin is deactivated or when using PHP 7.4, the issue might be related to a specific string translation. Solution: We recommend the following steps to resolve this issue: 1. Navigate to WPML -> Strings Translation. 2. Search for "All %s" under the "woocommerce" domain with "Exact match" checked. 3. Edit the German translation to include an "s" after "Alle %". 4. Press Enter to save the change. This adjustment should resolve the fatal error. Please check your site to confirm that the problem is solved.
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 at WPML support forum.
Problem: The client was experiencing issues with translating the product field description in the order summary of a Gravity Forms form on a multisite installation. The provided custom snippet did not translate the description text from German to English. Solution: We recommended replacing the existing snippet with a new one that includes steps to register and translate strings using WPML. Here is the revised snippet:
After implementing the new snippet, the client should: 1. Navigate to WPML → String Translation. 2. Filter by Domain/Context using the format 'gravity_form-{FORM_ID}', where {FORM_ID} is the ID of the form. 3. Look for strings named like 'field-{FIELD_ID}-description', add translations, and save. If the strings are not visible, the client should submit the form once or load any page that renders the product info to trigger the registration.
If this solution does not resolve the 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client noticed that some links on their multilingual website still pointed to the old URL after a site migration. This issue was not consistent across all pages. Solution: First, we recommended that the client back up the site and update all Elementor plugins to the latest version to ensure compatibility and functionality. After updating, we provided a Custom XML configuration to help correctly translate the links within Elementor widgets. The client should add the following XML configuration to their WPML settings:
If this solution does not resolve the 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.
