Problem: The client was unable to preview or update posts in both the original French and the English translation after creating a translation using WPML. They encountered a 403 error, which persisted even after deactivating all plugins except for essential ones. The issue was linked to the 'aioseo' plugin triggering Apache's mod_security 'critical' alerts, which blocked the capability to save a post. Solution: We recommended deactivating all plugins except for the WPML ones to check if the issue persists. The client discovered that the 'aioseo' plugin was the cause of the 403 errors. Disabling or adjusting the settings of the 'aioseo' plugin should resolve the 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. If the problem persists, please open a new support ticket at our support forum.
Problem: You are receiving spam emails on email addresses linked to websites after using WPML. You suspect that WPML might be causing this issue. Solution: We suggest that the presence of your email address on the website's pages might be the reason for receiving spam emails, rather than the use of WPML itself. Since WPML only makes your site available in multiple languages, it does not influence the security of email addresses displayed on your site. To reduce spam, consider removing your email address from the website or replacing it with a contact form. This way, your email remains hidden from public view, reducing the likelihood of receiving spam. If you still suspect WPML is causing the issue, try disabling WPML temporarily to see if the spam emails stop. This can help determine whether WPML is related to the problem.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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 needed, do not hesitate to open a new support ticket with us for further assistance.
Problem: You have a multilingual website with 7 languages and want to use automatic translation for certain languages and manual translation for others, specifically for blog posts. However, the auto-translate feature tried to translate already translated posts and corrupted the Blog page. Solution: If you're experiencing this issue, we recommend you configure your WPML settings to selectively use automatic translation. Here's how you can do it: 1. Navigate to WPML -> Settings -> In the first section, set the configuration to automatically translate only the content you select. 2. Go to WPML -> Translation Management, select the blog posts you wish to automatically translate, and send them for automatic translation. Save the changes after each step.
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 the issue persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing a PHP fatal error due to WPML_Gutenberg_Config_Option being defined twice in a WordPress environment using version 6.7.2 and sitepress-multilingual-cms.4.7.0. The error might stem from an incorrect update or usage by the previous developer. Solution: 1. We recommend manually removing the
sitepress-multilingual-cms
folder from the plugins directory and then re-uploading it after downloading the latest version from your WPML.org account. This action should resolve the issue of the class being defined twice. 2. Increase the WordPress memory limit to at least 128MB, as recommended by WPML. You can do this by adding the following line to your
Ensure to place this code above the line /* That's all, stop editing! Happy blogging. */. You can verify the updated memory limit in the WPML -> Support section of your WordPress dashboard.
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 issues persist, please open a new support ticket at WPML support forum for further assistance.
Problem: Nach der Installation von WPML und einem WordPress-Update funktioniert das Avada Theme nicht mehr korrekt: Logos, Inhalte, Schriftgrößen, Abstände und Farben sind fehlerhaft, und der Footer ist beschädigt. Das Deaktivieren von WPML stellt die normale Ansicht wieder her. Solution: 1) Aktiviere WPML erneut und führe den Setup Wizard unter WPML > Setup aus. Registriere WPML auf deiner Website und installiere die Plugins 'WPML String Translation', 'Advanced Custom Fields Multilingual' und 'WPML SEO'.
2) Stelle sicher, dass die Avada Theme-Optionen für alle Sprachen gleich sind. Gehe dazu in die Avada-Theme-Optionen und wähle in der oberen Admin-Leiste "Alle Sprachen" aus. Speichere anschließend die Einstellungen. Weitere Informationen findest Du hier: Wie man Theme-Optionen für Sprachen in Avada einstellt.
Falls diese Lösung veraltet ist oder nicht auf dein Problem zutrifft, empfehlen wir, die neuesten Versionen deiner Themes und Plugins zu überprüfen und bei weiteren Problemen ein neues Support-Ticket zu öffnen. Besuche auch die Seite mit bekannten Problemen unter https://wpml.org/known-issues/.
Problem: If you're experiencing issues where the original image isn't displayed on the frontend for product translations, and changes are not reflecting immediately, it might be due to insufficient memory limit settings. Solution: We recommend increasing the WordPress memory limit. You can do this by editing the
wp-config.php
file located in the root folder of your WordPress installation. Find the line:
define('WP_MEMORY_LIMIT', '256M');
and change it to:
define('WP_MEMORY_LIMIT', '512M');
This adjustment should help in resolving the issue with images not showing up directly on the frontend.
Please note that this solution might be outdated or not applicable 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. If the problem persists, please open a new support ticket at WPML support forum for further assistance.
