Problem: You have installed WPML and translated your front page, but when trying to open or edit the translated version, you receive a critical error. The error logs indicate an issue with the 'Add Any Extension to Pages' plugin, which is not compatible with WPML. Solution: We recommend deactivating the 'Add Any Extension to Pages' plugin to resolve the critical error. This plugin is not currently on WPML's list of compatible plugins, and its compatibility with WPML cannot be guaranteed. You can check the compatibility of plugins with WPML here. If the issue persists after deactivating the plugin, consider contacting the support team of 'Add Any Extension to Pages' for further assistance. Additionally, you can suggest that they join the Go Global program to make their plugin compatible with WPML. More details about the program can be found here.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues here, 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 here.
Problem: The client is using the wpresidence theme, translating from English to Arabic. They encountered issues where the design and block positions differ between the two languages. Changes in the English version caused problems in the Arabic version, including misalignment and incorrect display of elements such as the floor plan size. Solution: We recommended CSS adjustments to address RTL (Right-to-Left) support issues and alignment problems. For example:
For translating strings like 'Resale', 'Rentals', and 'Projects', use the WPML String Translation tool. If strings are not found, follow the guide at this guide. For issues not resolved by these steps or if the solution 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. If problems persist, please open a new support ticket at WPML support forum.
Problem: The client is trying to hide the 'WPML Translation Editor / WordPress Editor' using the
wpml_tm_post_edit_tm_editor_selector_display
filter, but it is not working. Solution: We recommend using a simple CSS solution to hide the editor. Please ensure you have a live backup before applying this custom solution:
#translation-editor-post-settings{display:none;}
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: The client is attempting to change the folder name for interface-wpml-log.php located in the 'logs' folder within the classes directory. This is because many servers exclude logs folders from backups, causing the file not to be restored. Solution: We advise against changing the folder name for interface-wpml-log.php due to potential conflicts or fatal errors. Changing the folder name would require updates to multiple files, specifically the following autoloader files:
. 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 needs to set a transparent or semi-transparent background color for the language switcher button in WPML but found no documentation on how to achieve this. Solution: We recommend applying custom CSS to achieve the desired transparency effect. Here is the CSS code you can use:
Please test the changes on a staging site before applying them to your live site. If you need further assistance, consider hiring a professional from our contractors' page.
This solution might be 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 this does not resolve your issue, please open a new support ticket.
Problem: You are trying to set 'Set prices in other currencies manually' as the default choice on the product page for variations, but the WooCommerce Multilingual plugin defaults to 'Calculate prices in other currencies automatically', causing manually set prices to be ignored. Solution: Since there is no central feature in the WooCommerce Multilingual plugin to switch to the manual price option for variations, you need to use custom coding. Add the following code to the functions.php file of your theme to set 'Set prices in other currencies manually' as the default for new product variations:
function set_default_manual_currency_pricing($post_id) {<br /> if (get_post_type($post_id) === 'product_variation') {<br /> update_post_meta($post_id, '_wcml_custom_prices_status', '1');<br /> }<br />}<br />add_action('save_post', 'set_default_manual_currency_pricing', 20, 1);
To apply this change to existing product variations, add this code, run it once, and then remove or comment it out:
If you need further assistance with custom coding, consider hiring a professional developer. You can find one experienced in customizing WPML and its add-ons at https://wpml.org/contractors/.
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 this does not resolve your issue, please open a new support ticket.
Problem: Los elementos del menú necesitan tener una clase CSS específica para alinearse correctamente con el logo. Sin esta clase, el menú regresa a su posición original, lo cual no es deseado. El cliente pregunta si puede agregar esta clase al selector de idiomas para mantener la alineación deseada. Solution: En lugar de añadir una clase CSS al selector de idiomas, puedes optar por una de las siguientes soluciones: 1. Aplicar una regla CSS más general que afecte a todos los elementos del menú, incluso aquellos sin una clase específica:
.header_6_secondary_menu ul li {
margin-top: -20px;
}
2. Añadir la clase específica del selector de idiomas "li.wpml-ls-menu-item" a la regla existente para mantener la alineación deseada:
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 te sugerimos revisar los problemas conocidos y confirmar que tienes las últimas versiones de los temas y plugins instalados.
