Problem: The client is experiencing an issue where the font changes from Noto Serif Georgian to Roboto when switching from the Georgian version to the English version of their multilingual website. Solution: 1. Navigate to WPML -> String Translation and use the search field to look for the font name strings. Ensure all instances, especially those under 'admin_texts' in the domain name, are translated. 2. If the font issue persists, go to the bottom of the String Translation page and click on 'Translate texts in admin screens'. Search for the font string in the admin texts, add it for translation, and translate it. 3. If these steps do not resolve the issue, it might be necessary to manually set the font via CSS for different elements like
p
,
h
tags, etc., to ensure it displays correctly in both languages. 4. Since the theme used is not officially compatible with WPML, consider contacting the theme author for further assistance or to make the theme compatible through our GoGlobal program: https://wpml.org/documentation/support/go-global-program/
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, please open a new support ticket for further assistance.
Problem: The client's plugin developer is encountering an issue with the
flush_rewrite_rules()
function when deactivating a plugin, which conflicts with WPML, leading to a 500 error. The developer has temporarily commented out this function in the plugin's deactivation hook to avoid the error. Solution: We recommend that the plugin developer joins the WPML Go Global Program to collaborate directly with our team for a compatible solution. Details about the program can be found here.
If this solution is outdated or does not apply to your case, 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. If issues persist, we highly recommend opening a new support ticket here.
Problem: If you're trying to translate a global element created with Bricks Builder and are encountering issues where the translation does not appear correctly on the frontend.
Solution: We recommend following these steps: 1. Apply the fix from the WPML errata page for Bricks Builder issues. You can find it here: Bricks translated content not showing on frontend. 2. Edit the home page in the default language using Bricks Builder and make necessary text changes. 3. Save your changes and exit to WordPress. 4. Update the translations in the Advanced Translation Editor (ATE), ensuring all text is present and translated. 5. If some elements still don't display correctly, go to WPML -> String Translation. Search for the strings that are not showing correctly, correct their language if necessary, and translate them. For guidance on changing the language of a string, visit: How to change the source language of strings. 6. Note that if you are using plugins like 'Max Addons for Bricks' which are not compatible with WPML, you might need to manually translate some elements using the WP Editor. For more information on using different translation editors, see: Using different translation editors for different pages.
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.
Problem: The client is experiencing issues with the search tool on their website, which works fine in the primary language (French) but does not return any results in the secondary language (German). The theme used, Zourney, is not officially compatible with WPML, which might be causing the issue. Solution: We recommend contacting the theme's author to discuss a potential quick fix, as the theme needs to adapt its code to handle translated posts/results in multiple languages. Specifically, they can implement WPML hooks such as
Additionally, you can invite the theme developers to join our GoGlobal program, where our developers will assist in making the theme compatible with WPML. More information can be found here: https://wpml.org/documentation/support/go-global-program/.
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 at WPML support forum.
Problem: If you're experiencing a fatal error when accessing the Pronamic plugin in the admin site, particularly when a custom post type has no posts, this might be due to a specific configuration issue.
Solution: We have identified that the issue is not directly caused by WPML. However, setting
'hierarchical' => false
in the Pronamic Pay with Rabo Smart Pay for WooCommerce plugin's custom post type (CPT) registration can prevent this issue. This adjustment addresses the root of the problem by modifying how the CPT is handled.
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. Additionally, if you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is facing an issue where custom links in the menu are not translated correctly from German to English using ATE. The links appear as /?product_cat=vehicle-type-car instead of the expected translated format like https://www.valtron.de/en/c/rear-view-cameras/f/vehicle-type-car/.
Solution: We recommend adding the following code to the end of your
functions.php
file to address the issue:
// WPML Workaround for compsupp-7532
function wpml_compsupp7532_add_custom_blacklist_requests( $blacklist, $sitepress ) {
// Add your custom request to the blacklist array
// We can hardcode URL's, like:
//$blacklist[] = "c/rear-view-cameras/f/vehicle-type-truck";
// Or use REGEX. This regex should match slugs like "c/(any slug here)/f/(any slug here)" - we may need to adapt it if needed
$blacklist[] = '/^c\/[^\/]+\/f\/[^\/]+\/?$/';
return $blacklist;
}
add_filter( 'wpml_sl_blacklist_requests', 'wpml_compsupp7532_add_custom_blacklist_requests', 10, 2 );
After adding the code, save the file, make a small modification to the block content, and save. Then, update the translations. You may need to re-translate the links.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are working on translating an online store using the Orderable plugin, which is not compatible with WPML. This incompatibility results in separate categories for each language, preventing linking of products in new languages to the main language categories for add-ons.
Solution: Since Orderable is not compatible with WPML, you will need a custom solution. We recommend using WPML's filters and action hooks to provide correct multilingual support. You can find more information and resources here:
We also suggest contacting the plugin author to request a compatibility update and refer them to the WPML Go Global program (Go Global Program) for assistance in making their plugin compatible with WPML.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: When using the Broadcast plugin to copy menus from one site to another, the copied menu is not visible on the child site, likely because the menu and its items do not have an assigned language. Solution: Currently, there is no available hook in WPML to programmatically set the language for menus and menu items copied using the Broadcast plugin. We recommend contacting the developers of the Broadcast plugin to discuss making their plugin compatible with WPML. They can also join our Go Global program where we assist developers in making their plugins compatible with WPML.
If this solution does not apply to your case, or if it seems outdated, 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.
Problem: If you're experiencing issues where the post format and structure break after translating into a right-to-left (RTL) language, it might be due to missing CSS files in the RTL stylesheet. Solution: We recommend checking if your theme's RTL CSS file (style-rtl.css) includes all necessary CSS files. In a case we investigated, adding the following imports to the style-rtl.css resolved the issue:
Please ensure to back up your site before making these changes. Additionally, it would be beneficial to contact the theme author to include these CSS files in the theme's RTL stylesheet to prevent similar issues.
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.
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 at WPML Support Forum.
Problema: Estás desarrollando un sitio y estás intentando usar el plugin Oasis Workflow junto con WPML Multilingual. El plugin Oasis Workflow no funciona cuando WPML Multilingual está activado. Si desactivas WPML Multilingual, Oasis Workflow funciona perfectamente. Solución: Si estás experimentando este problema, te recomendamos que contactes al autor del plugin Oasis Workflow, ya que afirman ser compatibles con WPML y tienen un flujo de trabajo específico para ello. Puedes encontrar más información aquí: https://www.oasisworkflow.com/oasis-workflow-compatible-with-wpml Además, sería beneficioso invitar al autor del plugin a nuestro programa GoGlobal para que podamos colaborar y hacer que este plugin sea oficialmente compatible. Más información sobre el programa GoGlobal aquí: https://wpml.org/documentation/support/go-global-program/
Si la solución proporcionada no es relevante porque está desactualizada o no se aplica a tu caso, te recomendamos abrir un nuevo ticket de soporte. También te sugerimos revisar los problemas conocidos en https://wpml.org/known-issues/, verificar la versión del arreglo permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins.
