Problem: You are using the Download Monitor plugin to manage site downloads and have encountered issues with translating shortcodes for different language pages. Specifically, the shortcode [downloads category="plumbing" orderby="date"] works on the English page but not on the Welsh page, where it is ignored and displays nothing. Solution: We have identified that the Download Monitor plugin is not currently compatible with WPML. To address this, we recommend the following steps: 1. Set the plugin's custom post type, taxonomies, and related custom fields to translatable. 2. Translate the "download" endpoint and the category using WPML's String Translation. 3. Update the page translation to include the translated shortcode with the translated Welsh category. This can be done by switching from the top admin menu. 4. If these steps do not resolve the issue, we suggest contacting the plugin author to request a compatibility update with WPML. You can provide them with resources on making their themes/plugins compatible by directing them to achieving WPML compatibility for themes and plugins and the Go Global program.
If this solution does not apply to your case, or if it seems outdated, 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. We highly recommend opening a new support ticket if further assistance is needed. Visit our support forum at WPML support forum for more help.
Problema: El cliente ha creado y subido el feed de productos al Google Merchant Center en español y desea saber si es posible subir el feed en otros idiomas configurados con WPML (EN, FR, IT, DE) para que Google los muestre en diferentes países. Solución: Actualmente, el plugin Google for WooCommerce que el cliente está utilizando no es compatible con WPML para manejar feeds multilingües.Puedes explorar el plugin WooCommerce Google Product Feed que sí ofrece compatibilidad con WPML para esta funcionalidad.
Si esta solución no resuelve tu problema o si la información proporcionada se ha vuelto obsoleta, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos, verificar la versión de la solución permanente e instalar las últimas versiones de los temas y plugins. Para más asistencia, visita nuestro foro de soporte.
Problem: The client is unable to upload SVG files through WPML Media Translation after updating WPML plugins. They encounter a default image or a 'Security check failed' message depending on the SVG plugin used. This issue persists across multiple environments. Solution: We recommend verifying the compatibility of the SVG plugin with WPML. WordPress does not natively support SVG, and third-party plugins like 'Safe SVG' might not be compatible with WPML. Check if the plugin has been updated recently and might require a compatibility update with WPML. Encourage the plugin author to join WPML's Go Global program to ensure compatibility. For more details, visit WPML's Go Global program.
However, if the problem is outdated or if you have further questions, feel free to 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.
For further assistance, please visit our support forum at WPML support forum.
Problema: Utilizas el tema ThemeRex. Y en la sección Servicios de tu sitio web, al hacer clic en cualquiera de los servicios en español, te redirige a un error 404. Aunque las páginas están traducidas, no se muestran correctamente incluso después de cambiar el slug. Solución: El slug del CPT creado por el tema no se puede traducir.Seguimos estos pasos: 1. Accedimos a WPML > String translation. 2. Buscamos "services" asegurándonos de marcar "Exact match". 3. Seleccionamos la entrada que corresponde al dominio "trx_addons". 4. Eliminamos esta entrada. Después de realizar estos pasos, los servicios en español aparecieron, aunque con el slug sin traducir. Identificamos que el problema está relacionado con el uso del plugin ThemeREX Addons, el cual no es compatible con WPML. Puedes encontrar más información sobre la incompatibilidad aquí: https://wpml.org/es/plugin/themerex-addons/ Te recomendamos cambiar de plugin para los CPTs o evitar traducir el slug. Aquí tienes una lista de plugins compatibles con WPML para trabajar con custom post types: https://wpml.org/plugin-functionality/custom-post-types-taxonomy/ Si esta solución no resuelve tu problema o si la información proporcionada se ha vuelto obsoleta, 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. Para más asistencia, visita nuestro foro de soporte: https://wpml.org/es/forums/forum/ayuda-en-espanol/
Problem: The client is experiencing 404 errors, incorrect URL links on translated pages, and issues with string translations in a WooCommerce environment after restoring a backup. The suspected causes include potential conflicts with SEO plugins or incompatibilities with the 'Divi Plus' plugin. Solution: 1. To address the 404 errors, we recommend resetting the SEO Press plugin by deactivating it, clearing all caches, and reactivating it. This approach has resolved similar issues in the past. 2. If the problem persists, test the website with only WPML plugins and a standard theme, while deactivating all other plugins to isolate the issue. 3. For issues specifically related to the 'Divi Plus' plugin, it appears there is a known compatibility issue with WPML. We advise contacting the plugin author to request a compatibility update. Additionally, plugin developers can refer to WPML's documentation for making their plugins compatible. 4. If you encounter PHP notices related to '_load_textdomain_just_in_time', this is a known issue with WordPress 6.7 affecting many plugins and themes, including WPML. Updating your plugins and themes to the latest versions may resolve these notices.
Please ensure to back up your website before making any changes and, if possible, perform these actions on a staging site to avoid affecting your live site.
If these solutions do not resolve your issues or if they seem outdated or irrelevant 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client has translated all categories, but they do not appear in the Arabic version of their site. The issue seems to be related to the theme used, which is not WPML compatible.
If this solution does not apply to your case, or if it seems outdated, we highly recommend 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. If issues persist, please open a new support ticket at WPML Support Forum.
Problema: Cuando se activa el plugin WooCommerce Multilingual & Multicurrency, el diseño de la página no carga correctamente en los productos que utilizan WooCommerce Appointments, aunque no muestra errores directos. Se identificó un error crítico relacionado con la función
get_client_currency()
en un entorno multimoneda. Solución: Se propone una solución temporal mientras se espera una corrección definitiva por parte de WooCommerce Appointments: 1. Ir a WooCommerce > WooCommerce Multilingual & Multicurrency. 2. Activar el modo de varias monedas. 3. No agregar ninguna moneda adicional. Este ajuste debería permitir que el sitio funcione como antes sin introducir nuevas monedas. Además, se sugiere que WooCommerce Appointments verifique si la opción de varias monedas está activada antes de ejecutar cierto código crítico, específicamente en
Si esta solución no resuelve el problema o si es irrelevante debido a actualizaciones posteriores, recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable revisar los problemas conocidos, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, puedes contactarnos en nuestro foro de soporte.
Problem: You are trying to automatically translate everything on your site using WPML, but some Elementor elements (theme's widgets) are not translated. Solution: We recommend you follow these steps to resolve the issue: 1. Add the following XML in WPML >> Settings > Custom XML Configuration section:
2. Make a small change in the default language sample page title and press the Update button to reload the translation. 3. Remove that change and press the Update button again. 4. Open the translated page in ATE, and the custom theme heading element should now be available for translation. 5. Add the translation, and it should work correctly on the frontend.
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.
Problem: The client is experiencing an issue where the Custom 404 Pro plugin, even though translated following the rules, links to the Italian error page instead of the English one when switching languages. This causes the settings for the Italian page to be deleted. Solution: Since the Custom 404 Pro plugin is not officially compatible with WPML, we recommend adding the following custom code to the
functions.php
file in your theme folder:
add_action('template_redirect', function() {
global $wpdb;
// Define the custom table name
$table_options = $wpdb->prefix . 'custom_404_pro_options';
// Get the stored 404 page ID from the custom table
$page_id = $wpdb->get_var("SELECT value FROM $table_options WHERE name = 'mode_page'");
if (is_404() && $page_id && function_exists('icl_object_id')) {
$translated_page_id = icl_object_id($page_id, 'page', true);
if ($translated_page_id && $translated_page_id != $page_id) {
$translated_page_url = get_permalink($translated_page_id);
if ($translated_page_url) {
wp_redirect($translated_page_url, 302);
exit;
}
}
}
});
Please test this code in a staging environment before applying it to your live site. Additionally, consider contacting the plugin authors to encourage them to join our Go Global Program.
If this solution does not resolve your issue or seems outdated, please check our related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If necessary, do not hesitate to open a new support ticket.
Problem: You are experiencing issues with the WPC Frequently Bought Together plugin when switching languages on your website. Specifically, products added to the cart in one language disappear when switching to another language. Additionally, the + sign in the Frequently Bought Together widget does not adjust correctly between Right-to-Left (RTL) and Left-to-Right (LTR) orientations. Solution: 1) For the issue of products disappearing from the cart upon language switch, this is a known behavior with complex products. We recommend enabling the option in WooCommerce Multilingual (WCML) to 'Prompt for a confirmation and reset the cart' when switching languages. This option is particularly useful for complex products. You can find more details here: Clearing Cart Contents When Language or Currency Change. Additionally, we invite the plugin author to join our GoGlobal program to work on compatibility improvements: Go Global Program. 2) For the alignment issues of the + sign in RTL and LTR orientations, this is likely controlled by the theme or the plugin's CSS and not by WPML. We advise testing the widget without WPML in both RTL and LTR modes and reporting the issue to the theme or plugin developer.
If these solutions do not resolve your 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.
Problem: The client is experiencing an issue where the English version of the gallery is not copied as it is on the Italian site after moving the site to production. This problem was previously reported in another ticket. Solution: The issue is with the plugin Divi Dynamic Helper, which is not officially compatible with WPML. Disabling Divi Dynamic Helper, the option to add the gallery dynamically disappears, and only allows for selecting individual images. There is no way to display an ACF-created gallery in Divi without using a third-party plugin, as confirmed here: https://divibooster.com/show-acf-gallery-images-in-a-divi-gallery-module/. If there is an issue with Divi and ACF alone, we are committed to resolving it. However, since a third-party plugin not tested with WPML is involved, a complete debugging is necessary, and we need the cooperation of the plugin author. They can contact us through this form: https://wpml.org/documentation/support/go-global-program/.
As a workaround, we can suggest the following: 1. Open the page in the Divi editor. 2. Open the gallery module settings. 3. Select the correct Gallery (it should be 'Galleria camera 1', but if not, use the same value as in the Italian room). 4. Save. Please note that 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 the issue persists, please open a new support ticket at WPML support forum.
