Problem: The client reported that after manually translating the 'About Us' page to Spanish, the content reverted to English within a few hours. Additionally, a critical error occurred preventing the page from loading. Solution: We first suggested ensuring that manual translations are edited manually. Upon further investigation, we discovered a critical error unrelated to WPML, indicated by a fatal error due to memory exhaustion. We recommended: 1. Checking the server error logs, which can be done by following the debugging guide at https://wpml.org/documentation/support/debugging-wpml/ 2. Consulting with the hosting provider to address the memory limit issue.
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. If problems persist, please open a new support ticket at WPML support forum.
Problem: The client was facing an issue where only the first footer column was displayed on their website, despite the theme supporting six footer columns. The client had added all HTML and CSS to the first column, which was not following WordPress best practices. Solution: 1. We advised the client to save CSS in the Customizer > Additional CSS, in the style.css file, or in a Child Theme instead of embedding it directly in the widget area. 2. We recommended using all available footer widget columns and avoiding manipulating the layout with additional CSS. 3. We suggested placing the FontAwesome link inside the
section of the HTML document using a plugin, which can be found here: https://wordpress.org/plugins/insert-headers-and-footers/ 4. Upon further investigation, disabling the "Droplet Framework" plugin resolved the issue, indicating a conflict between the theme and the plugin. 5. We recommended reinstalling the theme after taking a backup to ensure no theme code alterations were causing the issue. If these steps do not resolve your issue, or if the solution seems 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 at WPML support forum for further assistance.
Problem: You are managing a site where you frequently update PDF files and delete old ones. However, the old files remain in the /uploads directory and continue to be indexed by Google. You suspect this might be related to a WPML setting. Solution: We recommend ensuring that when you delete media files, you do so for all language versions. In your WordPress admin, switch the admin language to "All languages" in the top admin bar before deleting the files. This ensures that the media files are completely removed from all language versions, preventing them from being left in the /uploads directory and indexed by Google.
If this solution does not resolve your issue, or if it seems 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: You need to export product attributes and their translations into a single table using SQL or the WP ALL EXPORT plugin, but currently, they export as separate rows. Solution: We tested the WP All Export Pro and WP All Export - WooCommerce Export Add-On Pro plugins and found that each translation has a separate Term ID, causing each term to start on a new line in the export file. To organize the data in a single table, you can add the custom fields _wpml_import_language_code and _wpml_import_translation_group. After adding these fields, sort your spreadsheet based on _wpml_import_translation_group to group the English term with its translations. Additionally, consider using AI to reorganize the spreadsheet if necessary, as it might be simpler than custom coding.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue with the WPML plugin on their site, where translation tools return an error stating 'There is a problem connecting to automatic translation'. The issue was linked to a static redirection in the index.html file. Removing this file temporarily resolved the issue, but the client seeks a permanent solution while maintaining the redirection. Solution: We recommended that the client upgrade all WPML plugins to the latest version (4.7.3) after ensuring a full site backup. If the problem persists, we advised providing private details for further investigation. We also need to verify the redirection setup as described in the client's previous support thread. For privacy and security details when sharing debug information, please visit our privacy policy and how to provide access information.
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 WPML support forum.
Problem: The client reported an issue where the product URL in English still showed parts in Finnish, despite being translated. Additionally, there were PHP warnings related to file access restrictions due to open_basedir settings on the server. Solution: 1. We initially attempted to debug the issue and requested a staging site or a duplicator copy from the client to safely investigate the problem further. https://wpml.org/fr/faq/provide-supporters-copy-site/ 2. After initial checks, we escalated the issue to our second-tier support for deeper investigation. 3. We suggested the client ask their hosting provider to disable the open_basedir restrictions in the PHP settings to see if that resolves the permalink translation issue.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with the Translation Management feature in WPML not loading when using a Divi child theme. Despite disabling other plugins and changing themes, the problem persists specifically with the Divi child theme. Solution: We recommend the following steps to troubleshoot and resolve the issue: 1. Disable all plugins except for those related to WPML from your WordPress Dashboard > Plugins, and check if the issue resolves. If it does, reactivate each plugin one at a time to identify the conflicting plugin. 2. Temporarily switch to a default WordPress theme, such as 'TwentySeventeen', via your WordPress Dashboard > Appearance > Themes to see if the issue still occurs. 3. If the problem continues, it might be related to custom modules or configurations within the Divi child theme. We suggest contacting Divi support for further assistance on this matter. 4. Ensure you back up your site before making these changes. You can use the UpdraftPlus plugin for backup needs.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your specific case, please 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, you can visit our support forum at WPML support forum.
Problem: The client is using WPML with Elementor Pro on a WordPress site with different domains per language. The English domain (medicinepark.co.uk) redirects to the Romanian version and Elementor does not load when editing the English page. Solution: 1. Visit https://medicinepark.com.ro/ and deactivate the WPML Multilingual CMS plugin. This will help determine if the issue is related to WPML. 2. Check https://medicinepark.com.ro/ to ensure it displays the Romanian content correctly without WPML. 3. Visit https://medicinepark.co.uk/. If it still displays the Romanian content, the domain setup is correct. If it redirects, contact your hosting provider to resolve the redirection issue. 4. Once the redirection issue is resolved and the domain correctly displays content without redirecting, contact us before reactivating WPML.
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.
Problem: The client is unable to respond to an open support ticket on the WPML support site. Solution: We recommend logging out and then logging back in to the WPML support site. It is also advisable to clear your browser's cache. Trying a different browser might help if the issue persists.
If this solution does not resolve the issue or seems outdated, please check for 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. If the problem continues, we encourage you to open a new support ticket at WPML support forum.
Problem: You are encountering an issue where incorrect unicode characters ('@' and 'Ã') are appearing on the live product pages, but not within the WPML Translator. Solution: We recommend checking the character encoding settings of your database and your WordPress configuration. Ensure that your database is set to use 'utf8mb4' encoding and that your wp-config.php file includes the line
define('DB_CHARSET', 'utf8mb4');
. If these settings are correct and the issue persists, it might be related to the theme or other plugins that could interfere with the correct display of characters on the front end. In such cases, try disabling other plugins temporarily to see if the issue resolves. If none of these steps work, please visit our support forum and open a new ticket for further assistance. 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.
If the provided solution does not resolve your issue or seems irrelevant, please do not hesitate to open a new support ticket at https://wpml.org/forums/ for personalized assistance.
Problema: Estás experimentando un problema con WooCommerce en tu sitio web. Cuando un cliente registrado realiza una compra, es redirigido correctamente a la URL: ****.com/checkout/order-received/[order_num]. Sin embargo, un cliente no registrado es redirigido a ***.com/checkout después del pago. Este comportamiento ocurre solo con usuarios no registrados. Solución: 1. El problema parece estar relacionado con la configuración de WooCommerce y no con la traducción del contenido del sitio. Te recomendamos que contactes con el soporte de WooCommerce para que te ayuden a resolver esta cuestión. 2. Además, te sugerimos incrementar el límite de memoria de WordPress a un mínimo de 128Mb para mejorar el rendimiento general del sitio. Puedes hacerlo añadiendo el siguiente código en tu archivo wp-config.php:
Asegúrate de añadirlo encima de la línea /* That's all, stop editing! Happy blogging. */ Puedes verificar el límite de memoria actual en WPML -> Soporte.
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 y confirmar que tienes instaladas las últimas versiones de los temas y plugins.
Problem: The client reported that after a WPML update, the original language categories on their website disappeared, leaving only the categories in the translated language (Spanish). Attempting to recreate the categories in the original language resulted in duplicate category slugs (e.g., 'news-2'). Solution: We suggested that the disappearance of the categories might be due to changes in the database after uninstalling WPML, rather than a direct issue caused by WPML itself. To address this, we recommended the following steps: 1. Navigate to WPML -> Support -> Troubleshooting. 2. Click on 'Set language information'. For more details, visit WPML Troubleshooting Options. 3. Check if the original language categories reappear after these steps. If the issue persists, it might be unrelated to WPML or due to other configuration issues. In such cases, 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 this solution does not resolve the issue or seems irrelevant, please open a new support ticket at WPML Support Forum for further assistance.
