Not WPML issue

Problem:
The client was experiencing issues with the hover effect not working as expected for a language menu in Elementor. Despite setting the standard color to black and the hover and active color to red, the hover effect was not applying correctly.
Solution:
We recommended the following steps:
1. Add the necessary CSS in WPML -> Languages -> Language Switcher Options -> Additional CSS. The specific CSS to use is:

header ul li.wpml-ls-current-language a span.wpml-ls-display, header ul li a span:hover{<br />  color: #e40028;<br />}

2. Ensure to create a full site backup before making changes and update the WPML plugins to the latest version.
3. Increase the WordPress memory limit to at least 128MB by adding the following line to wp-config.php:

/* Memory Limit */<br />define('WP_MEMORY_LIMIT', '128M');

Place it above the line /* That's all, stop editing! Happy blogging. */.
For further guidance on customizing the language switcher with CSS, visit how to fix styling and CSS issues for the language switchers.

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 further assistance is needed, please open a new support ticket.

Problem:
After migrating a site, the client encountered an issue where WPML could not run normally due to an AJAX Error and a server configuration problem. Additionally, there was an inability to edit or see text in the editor, even though the AJAX Error was resolved after re-migrating.
Solution:
We recommended checking with the hosting provider regarding the AJAX Error as it is typically related to server issues. For the memory limit issue, which could also affect WPML's functionality, we advised increasing the WordPress memory limit. This can be done by adding the following lines in the

wp-config.php

file, right before the '/* That’s all, stop editing! Happy publishing. */' line:

define('WP_MAX_MEMORY_LIMIT', '256M');

define('WP_MEMORY_LIMIT', '128M');

After updating, the client should verify the new memory limit under WPML > Support > WordPress > Memory limit.
If these steps do not resolve the issues or if the solution 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 the latest versions of themes and plugins are installed. If problems persist, please open a new support ticket at WPML support forum.

Problem:
You are trying to display line breaks in the German translation as in the original English version, but WPML does not transfer the line breaks. Specifically, for a

<h2>

header in mobile view, WPML squeezes all sentences into a single line.
Solution:
The issue was related to the Divi theme, where the header was tagged as

<h2>

for desktop and tablet but as

<p>

for mobile. Changing the tag from

<p>

to

<h2>

in the mobile view resolved the issue.

If this solution does not apply to your case, or if it seems outdated, we recommend checking the related known issues and verifying that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.

Problème :
Le client a rencontré un problème de crash du site après l'installation du plugin WPML, qui semble entrer en conflit avec le plugin trx_addons utilisé par le thème Impacto Patronus. Le message d'erreur indiquait que WPML manquait certains enregistrements dans les tables de langues et mentionnait une classe manquante 'WPML_Elementor_Module_With_Items'.

Solution :
Nous avons identifié que le problème était causé par le plugin trx_addons, qui nécessitait une classe spécifique non trouvée. Nous avons recommandé au client de vérifier si le problème persistait après la désactivation de ce plugin ou en changeant de thème. Nous avons également vérifié que le thème et le plugin étaient à jour. Après avoir désactivé les addons WPML non nécessaires (comme GraphQL, ElasticPress, etc.), le site fonctionnait sans afficher d'erreurs. Nous avons conclu que le problème d'importation n'était pas lié à WPML mais spécifique au thème du client et recommandé de contacter le support du thème pour plus d'assistance.

Il est possible que cette solution ne soit plus pertinente en raison de mises à jour ultérieures ou qu'elle ne s'applique pas à votre cas. Nous vous recommandons de vérifier les problèmes connus et de vous assurer que vous avez installé les dernières versions des thèmes et plugins. Si le problème persiste, n'hésitez pas à ouvrir un nouveau ticket de support.

Problem:

The client is using WPML on their site and inquires whether they can switch between automatic and manual translation methods after the initial setup. They also ask if it's possible to get an estimate of the credits needed for automatic translation before starting, and how to choose among different translation engines like Google, Deepl, and WPML AI with ChatGPT.

Solution:

If you're experiencing similar questions, we recommend the following steps:

1. You can change your translation method at any time in WPML > Settings.
2. To estimate the credits needed for automatic translation, navigate to WPML > Translation Management, get a word count, and then use our simulator to calculate the costs. You can find the simulator here: Automatic Translation Pricing.
3. For choosing a specific translation engine, please refer to our detailed guide here: How to Change Automatic Translation Engines.

Please note that the solution provided 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 issue persists, please open a new support ticket at WPML Support Forum.

Problem:
The client is using a Revolution Slider template and has added the WPML language switcher shortcode, but it displays as text instead of functioning. Additionally, the language switcher cannot be clicked due to an HTML layer.
Solution:
1. Replace the shortcode with

[wpml_language_switcher]

and verify if the issue is resolved.
2. Increase the WordPress memory limit to at least 128MB. You can do this by adding the following code to your wp-config.php file:

/* Memory Limit */<br />define('WP_MEMORY_LIMIT', '256M');

Place it above the line /* That's all, stop editing! Happy blogging. */.
3. If the language switcher still cannot be clicked, contact the Slider Revolution support service to inquire about removing the obstructive HTML layer with ID SR7_12_1-41-16.

If these steps do not resolve your issue, or if the solution becomes outdated, we recommend opening a new support ticket. Additionally, 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. For further assistance, visit our support forum at https://wpml.org/forums/forum/english-support/.