Problem: Vous essayez de traduire le logo et le fil d'ariane de français vers anglais. L'image du logo est affichée via un code personnalisé. Solution: 1. Pour le logo, nous vous recommandons d'utiliser notre hook wpml_object_id pour obtenir l'ID de l'image dans la langue secondaire. Voici un exemple pour obtenir l'ID de l'image traduite en anglais :
Si cette solution ne s'applique pas à votre cas ou semble obsolète, nous vous recommandons de vérifier les problèmes connus sur https://wpml.org/known-issues/, de vérifier la version du correctif permanent et de confirmer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support sur notre forum de support.
Problem: The client needs to modify the language URL format to include country codes like /ca/fr/ and /us/en/ in their WordPress site using WPML. They attempted to modify the
REQUEST_URI
in an init hook but were unable to change the permalink structure as desired. Solution: We informed the client that achieving this URL format with WPML directly is not possible without additional custom coding. Since this requires complex code and might cause side effects, we recommended hiring a WPML contractor for professional assistance. You can find a suitable contractor by visiting https://wpml.org/contractors/.
Please note that this solution might be outdated or not applicable to your specific case. If this does 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: Der Kunde versuchte, die niederländische Version seiner Website automatisch zu übersetzen, stieß jedoch auf Probleme, da die Seite leer blieb und nicht übersetzt wurde. Zudem gab es Schwierigkeiten bei der Übersetzung des LayerSliders und eines externen Buchungswidgets. Solution: 1. Wir empfahlen, das WordPress-Speicherlimit zu erhöhen, da das aktuelle Limit von 40M zu niedrig war. Dies kann durch Hinzufügen des folgenden Codes in der
Bitte beachten Sie, dass diese Lösungen möglicherweise veraltet oder nicht auf Ihr spezifisches Problem anwendbar sind. Wir empfehlen, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und sicherzustellen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Sollten die Probleme weiterhin bestehen, eröffnen Sie bitte ein neues Support-Ticket im WPML-Support-Forum.
Problem: You are developing a site and need to add a custom currency or set different prices for different languages using the same currency. You found that the multi-currency plugin allows adding currencies like Solana or Bitcoin, and you are wondering if you can add your own custom currency to set different prices per currency. Solution: 1) Adding a custom currency is not a feature provided by WPML but by WooCommerce. You should add your custom currency to WooCommerce, and then you can use it in WPML/WCML. We recommend checking the WooCommerce developer documentation on how to add a custom currency symbol here: https://woocommerce.com/document/add-a-custom-currency-symbol/ 2) It is not possible to set different prices for different languages using the same currency in WPML. Each language version of a product is a translation of another, so the content and prices should remain consistent unless they are created as separate products.
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 at WPML support forum.
Problem: The client has a large multilingual site with posts in English and Spanish, consolidated from four older sites. They are facing issues with hardcoded links in Spanish content not correctly reflecting the new site structure. Solution: We recommend updating the hardcoded links via the database (DB). This approach will not affect the page content as these links are embedded in post meta. Therefore, updating them directly in the DB or by re-translating the pages and the links within them is necessary. For dynamic links, such as menu items, these should adjust automatically when you modify your WPML language settings.
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 here.
Problem: The client was unable to display translated regions, countries, and ports on their website using the Elementor Custom HTML widget. Solution: We recommended using the wpml_object_id filter hook to fetch translated post IDs in the current language. Detailed guidance on this hook is available at WPML documentation. For Ajax-loaded data, we advised passing the current language to the callback function. Instructions for handling Ajax requests can be found at WPML documentation. Additionally, we provided custom code examples to localize scripts and modify Ajax requests to ensure the correct language is used:
// Get the current WPML language
$current_language = apply_filters( 'wpml_current_language', null );
// Localize the script with the current language
wp_localize_script( 'common-js', 'wpmlData', array(
'currentLanguage' => $current_language,
));
lang: wpmlData.currentLanguage
These changes were implemented on the client's staging site. If further customization is needed, we recommended contacting a certified WPML contractor from this list.
Please note that the solution provided 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: You are working on a Russian translation for a website using WPML and have encountered an issue where all string translations for Divi footer widgets do not work, except for one. You have tried translating strings that you previously added from "Translate texts in admin screens" but most translations are not effective. Solution: We recommend using the method of "Creating Widgets in Each Language" to ensure all your footer widget strings are translated effectively. This approach involves setting up separate widgets for each language. You can find detailed instructions on how to implement this method on our documentation page: Translating Widgets.
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 further assistance is needed, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with creating English courses using Learndash on an Italian website. The permalinks for the courses are incorrect and not translated, leading to 404 errors and too many redirects. Solution: 1. Ensure that Learndash is translated using the WordPress Editor. For more details, visit https://wpml.org/plugin/learndash-lms/. 2. Duplicate the course with WPML and set it as independent. Adjust the permalink settings in WordPress and translate the slug in WPML > Settings > Post Type Translation. 3. Take note, that this issue was related to custom code in the child theme's functions.php file and we provided a workaround for the issue. 5. Verify that the custom post type slug is translated in WPML > Settings > Post Type Translation. For more information, visit https://wpml.org/documentation/getting-started-guide/translating-page-slugs/.
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your specific case, we recommend opening a new support ticket. Additionally, 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. For further assistance, visit our support forum.
Problem: You are using a custom plugin to modify the permalink structure for several custom post types that are linked to a parent post type via JetEngine relationships. The plugin is configured to dynamically include the parent festival’s slug in the child post URLs and uses WPML to translate the base slug. However, visiting the translated URLs results in a 404 Not Found error, suggesting a possible mismatch between the rewrite rules or WPML’s handling of the translated slug. Solution: We recommend not using the register/translate string hook for translating slugs as it is intended for PHP string translation, not slugs. Instead, create a custom post type (CPT) and its slug as outlined in our documentation. You can then easily translate it from WPML > Settings. Here are some helpful links:
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 at WPML support forum.
Problem: After updating WordPress and WPML, texts including standard paragraph blocks are missing on the translation page for patterns. Solution: We identified that the Arabic pattern was broken after the update. We have fixed the issue. Please verify if the texts are now appearing correctly on your translation page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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 WPML Support Forum.
