Problème : Vous utilisez le thème Twenty Twenty-Five avec un Page Builder pour modifier le modèle de catégorie de votre livre en anglais, mais vous rencontrez des difficultés pour lier ce modèle à la page en français en modifiant les taxonomies. Le modèle de catégorie ne se reflète pas correctement dans la traduction française, résultant en l'affichage de la version générique des archives de catégorie.
Solution : Nous vous recommandons de suivre ces étapes pour résoudre le problème : 1. Supprimez la traduction de la base de données (wp_posts et icl_translations). 2. Activez la traduction du slug dans WPML > Paramètres (Page URL > Translate). Cela inclura le slug dans la traduction et ne le créera pas automatiquement à partir du titre. 3. Allez à : wp-content/plugins/sitepress-multilingual-cms/classes/full-site-editing/BlockTemplates.php et commentez la ligne suivante :
$postData['post_name'] = $post->post_name;
4. Envoyez le modèle à la traduction depuis le gestionnaire de traduction. 5. Assurez-vous que le slug traduit est correct, par exemple « category-exemple ».
Si cette solution ne résout pas votre problème ou semble dépassée, nous vous recommandons de vérifier les problèmes connus, 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 nécessaire, n'hésitez pas à ouvrir un nouveau ticket de support.
Problem: If you're trying to translate strings from 'WooCommerce Subscriptions' and 'All Products for WooCommerce Subscriptions' using WPML and they are not appearing in WPML String Translation, even though they are visible in Loco Translate, this might be due to how strings are registered and rendered, especially when using Gutenberg blocks in themes like Twenty-Twenty Four. Solution: First, ensure you have scanned the plugins through WPML -> Themes and plugins localization. Also, check the Admin Texts section as described in our guide on Finding strings that don't appear on the String Translation page. If the issue persists, it might be related to a known problem with WooCommerce Multilingual cart page strings not being translated when using blocks. You can find the detailed solution on our errata page at WooCommerce Multilingual cart page strings not translated when using blocks.
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.
Problem: You are trying to translate field labels and form fields on WooCommerce cart and checkout pages using WPML, but the translated labels are not displaying on the frontend. Solution: If you're experiencing this issue, we recommend taking a backup of your site and applying the workaround provided in our errata. You can find the necessary steps and details here: WPML Errata for WooCommerce Multilingual Cart Page. Additionally, for more information on using WooCommerce shortcodes, please refer to WooCommerce Shortcodes Documentation.
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 issue persists, please open a new support ticket.
Problem: You are experiencing a PHP fatal error when using WPML with Visual Composer on your WordPress site while working on translated pages. The error is related to a method in Visual Composer’s WpmlController, impacting WPML functionality despite updating both plugins and increasing server limits. Solution: We recommend applying a workaround detailed in our errata. Please ensure to back up your database before making any changes. You can find the necessary steps here: Visual Composer Fatal Error when translating a page in PHP 8.0.x.
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 open a new support ticket at WPML support forum.
Problem: After installing the WPML plugin, the 'my profile' and 'my events' links in a user account stopped working. The issue was identified as related to the activation of the WPML plugin. Solution: 1. Increase the WordPress memory limit by adding the following code to the wp-config.php file:
Ensure this is added above the line /* That's all, stop editing! Happy blogging. */. 2. Run the Elementor database update and ensure all plugins and themes are updated. 3. Clear the browser cache or try accessing the site in incognito mode to see if the issue persists. 4. If the problem continues, check for known issues related to BuddyBoss and WPML at BuddyPress member pages not available for translation and BuddyBoss platform known issues.
If these steps do not resolve the issue or if the solution 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 the problem persists, please open a new support ticket at WPML support forum.
Problema: Después de actualizar a WordPress 6.7.1, algunas cadenas como 'All Events', 'Free', 'Details', 'Date', 'Cost' y 'Add to Calendar' del plugin The Events Calendar PRO no se muestran traducidas en el frontend. Solución: Este problema es conocido y se debe a cambios en el core de WordPress, no en los plugins de WPML. Recomendamos contactar al soporte de The Events Calendar PRO para que ajusten su código y resuelvan el problema. Puedes encontrar más información sobre problemas similares en nuestra página de erratas: https://wpml.org/errata/missing-translations-on-front-end/.
Si esta solución no resuelve tu problema o si la información 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 del arreglo permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins.
Problem: The client is using a BLock Theme and was unable to see changes made to the theme, such as background color, consistently across different language versions of the site. Specifically, changes made in the site's default language (French) were not appearing in the English version. Additionally, there were issues with editing and updating the French 'Pages' template when WPML was enabled. Solution: 1. We advised the client to always make changes in the site's default language (French) and then use WPML to translate these changes into other languages. 2. To view and edit the English templates, the client needed to change the admin language to English, navigate to Appearance > Site Editor > Templates, and then reinitiate the English 'Pages' Templates. 3. For translating, the client should go to WPML > Translation Management, select the French 'Pages' Template, send it to translation, and translate it at WPML > Translations. 4. We identified a misconfiguration in 'WPML > Settings > Taxonomy Translation' where the taxonomy 'Themes (wp_theme)' was set to 'Translatable - use translation if available or fallback to default language'. Changing this setting to 'Not translatable' resolved the issue. 5. We also noted that there were duplicate and manually created translations for templates and template parts which needed cleanup. The client was advised to delete unnecessary translations and reset the default template where needed. 6. Detailed steps for managing template translations can be found here: https://wpml.org/errata/template-is-not-applied-to-translated-page/
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. Please feel free to open a new support ticket for further assistance at https://wpml.org/forums/forum/english-support/.
