Not WPML issue

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/.

Problem:

You want to remove auto synchronization of pages/posts when duplicating them, as you need manual translation.

Solution:

After duplicating a post/page to a secondary language, open the duplicated post/page for editing and click on the Translate independently button. You can find more details on this step here: Translate Independently.

Then, return to the original language post/page and modify it to see if you are getting the expected results.

For further guidance, please refer to our documentation: Using Different Translation Editors for Different Pages.

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 or visit our support forum.

Problem:
The client reported issues with long delays when saving translations on a page, and the footer not translating correctly despite following provided instructions.
Solution:
1. For the issue of delays when saving translations, we recommended refreshing the page as demonstrated in the screen recording: https://go.screenpal.com/watch/cZlwDAneqqk.
2. Regarding the footer not translating, we corrected the string translation to point to the correct language Footer template ID via the WPML String Translation interface.

If this solution does not resolve your issues 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.

Problema:
El cliente está intentando traducir un producto del español al alemán usando WPML y no desea traducir el slug del producto para evitar conflictos con las campañas publicitarias.
Solución:
Para mantener el mismo slug en la traducción, simplemente debe copiar el campo del slug del idioma original al campo del slug del idioma traducido. En cuanto a las implicaciones de SEO de mantener el mismo slug, es recomendable consultar la documentación de los motores de búsqueda para entender las mejores prácticas.

Si esta solución no resuelve su problema o si la información parece desactualizada, le recomendamos abrir un nuevo ticket de soporte. También es aconsejable revisar los problemas conocidos y asegurarse de que tiene instaladas las últimas versiones de los temas y plugins. Para más asistencia, puede visitar nuestro foro de soporte.