Divi body content is not showing in the Translation Editor.
Solution:
By adding a small change, like adding a dot, to the original language page and then updating it, and then going to the Translation Editor, I could fix this issue.
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.
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.
Problem:
We have a multilingual website which is connected with English & Arabic using WPML plugin in WordPress. As a default behavior, the website is redirecting to /en/ version which I need to stop, but the same time, /en/ should not be removed from any menu links. The overall expectation is to stop the redirection only in initial load.
Solution:
Go to WPML->Languages->Browser language redirects and verify that it has been disabled.
Problem:
Hi, I did a scan with the "Website Auditor" of the SEO PowerSuite and it gives me back 274 errors under "Localization" ---> "Missing Return Links".
The issue is that non-canonical paginated URLs have the "hreflangs" instructions in the code while there should be none in case the canonical URL of the page is different.
Solution:
In the end, the issue seems to be related to an Elementor module not compatible with Yoast.
This is from the Yoast Support team:
"Yoast SEO utilizes the built-in WordPress core functions to recognize pagination. The blog page on your site uses an Elementor module to add pagination to the blog page instead of using the WordPress core static blog page. For Yoast SEO to detect pagination on a non-static blog page, a manual page break must be included in the content."
Problem:
Yesterday I tried to activate the Multi-domain functionality, it all seems to work wonderfully, but for one exception: When I activate the multi-domain functionality, all the wp-admin ajax calls are done to the first domain (covid19.groupealliances.com)
Solution:
There is issue when you use “Different domains per language” and Nginx server configured with server_name that does not match your domain name.
Replace:
$url_parts['host'] = $_SERVER['SERVER_NAME'];
- in wp-content/plugins/sitepress-multilingual-cms/classes/url-handling/converter/strategy/class-wpml-url-converter-domain-strategy.php
Problem:
Mailchimp and other from plugins do use tooltips.
Solution:
Those strings are usually displayed in browser user language. So, there is actually no need to translate them. If you switch the browser language to German for example you should see how the content changes.
Actually each browser has it own way of displaying them, as thez are generated with JavaScript programatically.
Problem:
How to disable specific products for a specific language?
Solution:
The way to exclude products from specific languages is to simply not translate them.
Important is that you do not display the original content, as long a translation does not exist (fallback) which means you need to make sure to set WPML -> Settings -> Post Type Translation -> Products to "Translatable - only show translated items".
Another way, in case the products are already translated, would be to go to the products list and set those specific products as "Draft" or "Private", which will make them only visible to admin users.
Now you can find and translate the full code in WPML -> String Translation -> Under 'admin_texts_widget_custom_html' domain, especifically the '[widget_custom_html][10]content' name.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
