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.
Problema: Il cliente ha un form di Gravity Form complesso con centinaia di campi, molti dei quali sono ripetuti. Ha tentato di tradurre un campo, modificando il valore 'Due Date' in 'Data Scadenza', e questo ha cambiato tutti i 220 valori di 'Due Date' in 'Data Scadenza'. Ora, il cliente desidera correggere in massa il valore con 'Date d'échéance'. Soluzione: Se stai cercando di aggiornare in massa i valori nel database per i campi di Gravity Form, questa operazione richiede una programmazione personalizzata. Questo va oltre lo scopo del nostro supporto diretto. Ti consigliamo di consultare la nostra pagina dei contractor su https://wpml.org/contractors/ per assistenza professionale.
Se la soluzione proposta non risulta essere rilevante, perché potrebbe essere datata o non applicabile al tuo caso, ti suggeriamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di controllare i problemi noti su https://wpml.org/known-issues/, verificare la versione della correzione permanente e confermare di avere installato le ultime versioni di temi e plugin.
Problem: You want to translate WooCommerce strings differently based on the product category in Latvian, considering gender-specific language requirements. Solution: Currently, WPML does not support automatic conditional translations based on product categories. We recommend using the WPML String Translation module to manually translate or retranslate the strings to ensure they match the gender context of the product category. For detailed guidance on using this module, please visit WPML String Translation documentation.
If this solution does not fully address your issue or seems outdated, we encourage you to open a new support ticket. We also 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.
Problem: The client needs to change the fallback language to English for the /en part of their site, without altering the default language from Italian to English. Solution: We explained that the fallback feature in WPML is linked to the default language, and currently, there is no option available to set a fallback language to a secondary language. Additionally, implementing such a feature would require custom coding, which is beyond the scope of our support as per our support policy.
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 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.
Problem: The client is experiencing slow site response times of 10-12 seconds when using the WPML and String Translation plugins. The issue persists even after upgrading the server, enabling caching, and creating a staging site. Deactivating the String Translation plugin resolves the issue, indicating it as the source of the slowdown. Solution: We performed several steps to address the issue: 1. Ran the WPML troubleshooting option to "Cleanup and optimize string tables" at WPML > Support > Troubleshooting, and created the necessary custom language MO files at /wp-content/languages/wpml, which improved site performance. 2. Suggested cleaning up the database by following the steps outlined in this documentation. This includes installing a recommended plugin and running the cleanup process multiple times. 3. Provided a SQL query to delete untranslated strings from the WPML String Translation:
DELETE FROM wp_icl_strings WHERE status = 0;
4. Identified that the custom theme significantly increases load times when enabled. Recommended switching to a default theme like Twenty Twenty-Four, which reduced load times to about 2 seconds. 5. Noted an issue in the custom theme's code and provided the correct usage:
If these solutions do not resolve the issue or if they seem 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.
