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/.
Si esta solución no resuelve tu problema o si parece estar desactualizada, te sugerimos abrir un nuevo ticket de soporte. También recomendamos 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 los temas y plugins.
Problem: The client reported that activating the WPML plugin affects the Elementor page builder on their website. Specifically, some blocks drop, and custom CSS for the main menu does not appear. Solution: We recommended the client to first ensure that the issue is specifically related to WPML by deactivating all other plugins except for WPML and Elementor and then checking if the problem persists. This helps isolate the issue. Additionally, we asked the client to provide screenshots to better understand the specific problems they are facing. We also inquired if the custom CSS might be causing the issue when WPML is activated and suggested testing the site without the custom CSS to see if that resolves the problem. Furthermore, we requested details on how the problematic sections were created to diagnose further. It's important to back up the database before making these changes to avoid any data loss.
Please note that the solution provided might be outdated or not applicable to your specific case. If the issue persists, 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 needed, do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You are experiencing an issue where you cannot access a specific page due to a PHP Warning related to an open_basedir restriction. This error occurs while attempting to load a translation file in the WPML plugin. Solution: We have addressed this issue in the latest version of the WPML String Translation plugin. To resolve this, please update your plugin to version 3.2.18. You can do this by navigating to the Plugins → Add New Plugin → Commercial tab and clicking the "Check for updates" button. Before updating, ensure that you back up your database. For more details, visit the errata page: WPML Errata on open_basedir restriction.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest checking related known issues at WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins.
Falls das Problem weiterhin besteht oder die Lösung aufgrund von Aktualisierungen irrelevant geworden ist, empfehlen wir, die neuesten Versionen Ihrer Themes und Plugins zu überprüfen und bei Bedarf ein neues Support-Ticket zu öffnen. Überprüfen Sie auch die bekannten Probleme unter https://wpml.org/known-issues/. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum: https://wpml.org/de/forums/forum/support-in-german/.
