โซลูชั่นที่มีอยู่

Problem:
Plugin strings not translating after WPML default language change.

Solution:
Delete and recreate the translation strings in the WordPress admin dashboard, under WPML → Translations.

• In WPML → Translations, find the string - you can select domain of your plugin in the "Select strings within domain:" drop-down and use the "Search for:" field and search for part of the string to be translated
• Select all occurrences of the string and click "Delete selected strings" button - before this please copy the existing translations and save them somewhere for the later step
• At the bottom of the same page, in "Auto register strings for translation", activate the "Look for strings while pages are rendered" checkbox
• Reload the front end where plugin is active - plugin code should execute when the page is refreshed
• Go back to WPML → Translations, clear the "Look for strings while pages are rendered" checkbox, and perform the same search for the string again, it should show up on the list as "Not translated"
• Insert your saved translation from step 2, save, mark "translation is complete"

The translated string should now show up on the front end.

Relevant Documentation:
https://wpml.org/documentation/getting-started-guide/theme-localization/

Problem:
Unable to list all WPML plugin in Plugins > Add New > Commercial tabs it displays the text "No repositories defined"

Solution:
Search for the option_name wp_installer_settings in wp_options table and rename the option_name to something else, This will reset the installer config and resolve the issue

Problem:
When sending page for translation via Translation management I get an error:
"(12) Invalid state 'translating' to complete operation"

Solution:
There was an issue with Redis cache which creates objects from WordPress content which doesn't work well with WPML Translation Management. Fixed in the next release.

Problem:

Sticky Links - When Sticky Links is enabled, the link is shown in its raw state after processing the links.

Solution:

This is expected. When the WPML Sticky Links addon is installed and you have enabled it to make your links sticky, then it is expected to see such a URL pattern. WPML makes it to avoid broken links in your content, although internally you will see these links in this format (?post_type=ID) when clicked they are automatically converted into a permalink structure set up in your WordPress Dashboard > Settings > Permalinks settings.

Relevant Documentation:

https://wpml.org/documentation/getting-started-guide/sticky-links/

Problem:
How to code PHP as per current language?

Solution:
You have to use "ICL_LANGUAGE_CODE" to get your current language.
Here is the sample code/structure

function my_custom_function() {
    if(ICL_LANGUAGE_CODE=='en'){
        <!--- your code to english--->
      
    } elseif(ICL_LANGUAGE_CODE=='de'){
        <!---your code to german--->
  
  
    } elseif(ICL_LANGUAGE_CODE=='fr'){
        <!---your code to french---
        Global site tag (gtag.js) - Google Analytics -->
  
    } elseif(ICL_LANGUAGE_CODE=='es'){
        <!---your code to spanish--->
    }
}

Modify your code according to this and you will get what you want.

Problem:
Redirect Ninja Form to language-specific thank you page

Solution:
1. Go to Ninja Forms-> Edit your Form
2. Emails & Actions
3. Edit the redirection field
4. Add {wp:site_url}/thank-you/ instead of the permalink alone as now wp:site_url will include /cy/ in the translation and automatically redirect thank-you to its translation.

Relevant Documentation: https://wpml.org/documentation/related-projects/creating-multilingual-forms-using-ninja-forms-and-wpml/#adding-a-redirect-for-translated-forms

Problem:
I am trying to: Translate SEO title and meta description for custom post types for each of my website's languages. I can see the string in the "translation strings" screen (and I add the translation here), but in the frontend site, the custom post type archive page only shows meta title and description in the default language.

Solution:
Version 14.0 of the Yoast SEO plugin came out with some major changes. Some changes affected the compatibility with WPML. However, everything's gonna be fixed in Yoast SEO Multilingual 1.2.0. Until then you can use the fix presented in the errata below.

Relevant Documentation:
https://wpml.org/errata/search-page-title-in-wordpress-yoast-seo-is-not-translating/