Documentation request

Problem:
You need to change the image source (src) on a fixed banner loaded with a custom plugin, with a different image per language.
Solution:
1. Update your plugin with the following code:

$image_default = plugin_dir_url(__FILE__) . 'cmd_jobs/config/svs_Fixed_ban4_EL.jpg';<br /><br />/* Register image URL for translation */<br />do_action(<br />    'wpml_register_single_string',<br />    'svs-plugin',<br />    'banner_image_url',<br />    $image_default<br />);<br /><br />/* Retrieve translated image URL */<br />$svs_image_Banner = apply_filters(<br />    'wpml_translate_single_string',<br />    $image_default,<br />    'svs-plugin',<br />    'banner_image_url'<br />);

2. Navigate to WPML >> Theme and plugins localization, select your plugin, and press the “Scan selected components for strings” button.
3. Go to WPML >> String Translation.
4. Translate the 'banner_image_url' string by replacing it with the image URL for each language (e.g., EN image URL).
This approach allows WPML to load a different image URL per language without hardcoding multiple variables.
For more details, refer to the following documentation:

• https://wpml.org/wpml-hook/wpml_register_single_string/
• https://wpml.org/wpml-hook/wpml_translate_single_string/

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.

Problème :
Vous prévoyez de réinstaller WordPress et WPML sur votre site tout en conservant les mêmes domaines, langues, contenus, structure, et projet SEO. Vous souhaitez récupérer les traductions existantes sans retraduire les contenus, consommer de nouveaux crédits, ou recréer un nouveau projet de traduction.
Solution :
Après vérification dans l'éditeur de traduction avancé de WPML suite à une migration similaire, il a été observé que la mémoire de traduction fonctionne correctement et la majorité du contenu des pages migrées est réutilisée sans consommer de nouveaux crédits. Cependant, certains segments nouveaux ou structurellement différents ont consommé des crédits résiduels. Par exemple, des titres ou des paragraphes restructurés ont été identifiés comme nouveaux contenus nécessitant une traduction. Ces observations montrent que, bien que la mémoire de traduction réutilise efficacement les segments identiques, des modifications dans la structure ou le contenu peuvent entraîner une consommation de crédits.

Si cette solution ne semble pas pertinente ou est obsolète pour votre cas, ou si vous avez d'autres questions, nous vous recommandons de consulter les problèmes connus, de vérifier la version des corrections permanentes, et de confirmer que vous avez installé les dernières versions des thèmes et plugins. N'hésitez pas à ouvrir un nouveau ticket de support si nécessaire.

Problem:
You need to delete 15,000 translation strings in bulk.
Solution:
We recommend using the WPML String Translation module to manage and delete these strings. Here’s how you can do it:
1. Navigate to WPML → String Translation.
2. Scroll down to 'Remove strings by domain' and click 'Remove strings'.
3. Select the domains of the strings you no longer need and click 'Remove'. This will delete all untranslated strings from those domains and they will no longer appear on the String Translation screen.
For more detailed instructions, please visit our documentation on how to delete a string.

If this solution does not apply to your situation, 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.

Problem:
The client is experiencing an issue where the footer does not switch to the English version when changing the site language on the frontend, despite the footer custom post type being set as translatable and the English footer existing and being published.
Solution:
We resolved the issue by translating the footer ID via String Translation. We recommend checking the footer on the frontend to ensure it displays correctly in the selected language.

If this solution does not apply to your case, or if it seems outdated, please visit our known issues page, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the issue persists, we highly recommend opening a new support ticket for further assistance.