Problem: The client is experiencing issues with WPML where after translating a page, the products are duplicated in the translated language. Additionally, images in the product description are not being transferred or displayed correctly in the translated products. Solution: We recommend the following steps to resolve the issue: 1. Ensure that all images are uploaded directly to your website and are not linked externally. 2. Manually assign these images to your products on the primary language page. This setup ensures that when products are translated, the images will be correctly copied over to the translated versions. 3. Replace the images in the product descriptions as well. This can be done by editing the product in the primary language and ensuring all images are correctly linked and displayed before translating. 4. If images are still linked externally in some products, correct this by ensuring all images are stored locally on the server. After making these corrections, delete the existing translations and retranslate the products. This should ensure that the images are correctly copied into the secondary language descriptions.
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 problems persist, please open a new support ticket.
Problema: El cliente no puede ver el icono de lápiz para editar la traducción de productos en WooCommerce después de haber creado los productos. Solución: El problema fue causado por un conflicto con el plugin 'All-in-One WP Migration Unlimited Extension', que faltaba un archivo. Desactivamos este plugin, permitiendo así que el cliente configure correctamente WooCommerce Multilingual & Multicurrency. Recomendamos verificar que el problema se haya resuelto tras esta acción.
Si esta solución no resuelve el problema o si parece desactualizada, te recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos y confirmar que tienes instaladas las últimas versiones de los temas y plugins. Para asistencia adicional, por favor visita nuestro foro de soporte.
Problem: The client experiences a 404 error when trying to open English pages on their multilingual website, although the pages exist in both Turkish and English. The error does not occur when switching from Turkish to English on the same page.
Solution:
After further investigation during a chat with the client, it was observed that there was a lot of custom code added in functions.php file which was causing this irregular behavior. Pages were throwing 404 randomly.
Since custom coding is out of scope of this forum, we advised the client to remove all the code and check piece by piece while keeping an eye on the issue.
If this solution does not resolve the issue or seems irrelevant due to being 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 problem persists, please open a new support ticket for further assistance.
Problema: Si estás intentando vincular productos en varios idiomas y encuentras que el desplegable de variaciones deja de funcionar o los productos desaparecen del carrito al cambiar de idioma, es probable que estés enfrentando problemas con la configuración de las traducciones y las variaciones en WPML. Solución: 1. Asegúrate de que los productos traducidos tengan las mismas variaciones en todos los idiomas. Si las variaciones son diferentes, no se consideran el mismo producto y, por lo tanto, no funcionarán correctamente al vincularlos. 2. Revisa la configuración del comportamiento del carrito en WooCommerce -> WooCommerce Multilingual & Multicurrency -> Pestaña 'Configuración'. 3. Para traducir correctamente los productos, debes crearlos primero en el idioma original y luego traducirlos a los idiomas secundarios. Evita vincular productos 'diferentes' con variaciones distintas antes de traducirlos. 4. Consulta la guía sobre cómo gestionar productos multilingües en WooCommerce en esta documentación. 5. Sigue los pasos para configurar el comportamiento del carrito al cambiar de idioma en esta guía.
Si esta solución no resuelve tu problema o parece no ser relevante debido a actualizaciones o diferencias en tu caso específico, te recomendamos abrir un nuevo ticket de soporte. También es altamente recomendable revisar los problemas conocidos en problemas conocidos, verificar la versión de la solución permanente y confirmar que tienes instaladas las últimas versiones de temas y plugins.
Problem: After upgrading the WPML plugin to version 4.6.15, the client's site experienced a critical error upon login, which was resolved by deactivating the plugin. The error was a TypeError in the WPML_Dependencies class, indicating an issue with handling expected versions of dependencies. Solution: The client managed to restore the site functionality after testing and reinstalling some WPML plugins and disabling others to prevent further crashes.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking the related 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.
Problem: You are trying to access the German version of your site and encounter the error: net::ERR_CERT_COMMON_NAME_INVALID. This error typically indicates a mismatch between the domain name and the name listed on the SSL/TLS certificate. Solution: If you're running a multilingual website with WPML and using different domains for each language, you'll need to ensure that each domain has its own SSL certificate that correctly matches the domain name. This is essential to avoid common name mismatch errors.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please visit our support forum at WPML Support Forum.
Problem: The client is trying to translate product attribute labels in WPML and encounters issues in both String translation and Taxonomy translation. The taxonomy general name is not plural and includes an untranslated English 'Product' prefix, which cannot be corrected through the UI. Solution: To remove the 'Product' prefix from the taxonomy general name and manually add the plural form of the taxonomy singular name, we recommend using a custom filter hook in WooCommerce. Here is the code you can use:
add_filter( 'woocommerce_product_attribute_taxonomy_name', 'custom_woocommerce_attribute_label_plural', 10, 2 );
function custom_woocommerce_attribute_label_plural( $taxonomy_name, $taxonomy ) {
if ( 'pa_your_attribute' === $taxonomy ) { // Replace 'pa_your_attribute' with the actual attribute taxonomy name
// Return the custom label you want
return 'Label'; // Replace with your desired label
}
return $taxonomy_name;
}
This code will change the appearance of the label on the frontend but not in the wp-admin. Alternatively, you could register the original taxonomy in English and translate it into German.
If this solution does not resolve your issue or seems outdated, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If needed, do not hesitate to open a new support ticket.
Problem: You are trying to translate labels, slugs, and attribute taxonomy options using WPML, but the translation interface does not consistently show the WPML default language (German) as the source. Instead, the globe symbol appears under the English flag, making it untranslatable. You have to manually change the language to German, and the label text is shown in English, not the source language. Solution: The default language in WordPress is typically English, depending on the language in which WordPress was installed. To resolve this issue, you need to adjust the source language for the taxonomy labels and strings. This adjustment will enable you to create your translations effectively. It is crucial to ensure that especially the slug is translated, regardless of the source language displayed.
If this solution does not apply to your case, or if it seems outdated, we recommend opening 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 https://wpml.org/forums/forum/english-support/.
Problem: After moving a website to a new server, activating the WPML Multilingual CMS plugin resulted in a critical error, and the site appeared without translations.
Solution: First, we removed an outdated and incompatible version of the WPML String Translation plugin that was not supported by your Multilingual Blog license. Next, we addressed issues in the .htaccess file by renaming it and resaving permalinks to generate a fresh .htaccess file.
We then resolved PHP errors related to undefined functions and constants by updating WordPress to the latest version through https://www.optiparts.com/wp-admin/update-core.php. After updating, we successfully activated WPML and tested creating and translating posts in different languages.
We recommend activating other plugins one by one to identify any potential incompatibilities. Ensure to update all plugins and the theme to their latest versions.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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 for further assistance at WPML support forum.
Problem: You are trying to install the WPML multilingual CMS and encountering errors such as 'Could not copy file' during installation and a fatal error upon activation. These issues persist even after attempting installation through different methods including OTGS, WordPress interface, and manual installation via cPanel. Solution: The issue appears to be related to your server rather than WPML itself. Here are the steps we recommend: 1. Check file permissions: Ensure that the
wp-content
folder and its subdirectories have the correct write permissions. Directories should generally have 755 permissions and files should have 644. You can set these using an FTP client or via SSH with the commands:
chmod -R 755 wp-content
(for folders)
chmod -R 644 wp-content/*
(for files) 2. Check disk space: Verify that your hosting account has sufficient disk space to complete the installation. Insufficient disk space can cause file copy operations to fail. 3. Consult your hosting provider: Since the problem persists even after ensuring file permissions and disk space, it might be related to specific server settings or PHP configurations. Discuss these issues with your hosting support.
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 problems persist, please open a new support ticket.
