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

Problem:
With domain per langauge, The secondary domain with www. version always redirects to primary domain instead of displaying the translation

Solution:
Client htaccess rule which works best

RewriteEngine on
RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC]
RewriteRule ^(.*)$ https://%1%{REQUEST_URI} [R=301,QSA,NC,L]

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.

Relevant Documentation:

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

with:

$url_parts['host'] = $_SERVER['HTTP_HOST'];

Relevant Documentation:
- https://wpml.org/errata/possible-nginx-issues-with-different-domains-per-language-setting-when-doing-a-rest-api-call/

Problem:
I added all my pages to Translation Basket as per seen in tutorials. Since that happened I can't open Translation Basket

Solution:
If you do not have any translation in progress (beyond those that are stuck), you can reset it by following the steps below:

- Click on the WPML > Support > Troubleshooting
- Scroll down and look at the "Reset professional translation state"
- Select the "I am about to stop any ongoing work done."
- Click on the "Reset professional translation state"

Relevant Documentation:
https://wpml.org/documentation/support/wpml-troubleshooting-options/

Problem:
Some taxonomies in your site are forced to be untranslatable. This is causing a problem when you're trying to run a multilingual WooCommerce site.

Solution:
1) Go to WPML > Settings > Taxonomy translation and make sure all the related product taxonomies are set to (click on the lock to unlock) 'Translatable - only show translated items' or 'Translatable - use translation if available if available or fallback to default language'. For example, product_cat (Product category) should be translatable.

2) Override any of theme XML rules for specific taxonomies by checking theme XML file in the theme root folder and change 0 to 1 (translatable).

or

Go to the WPML -> Settings page and click the Custom XML Configuration tab. Add the taxonomy rules as per our documentation.

Relevant Documentation:
- https://wpml.org/documentation/related-projects/woocommerce-multilingual/#taxonomies
- https://wpml.org/documentation/support/language-configuration-files/#custom-taxonomies

Problem:
Would you please help us in translating the interactive forms with Formidable PRO addon? We have tried already below solutions, none of them worked.

Solution:
It seems that the glue plugin between WPML and Formidable was not made to have the placeholder string available for translation.

Now, can you go to wp-content/plugins/formidable-wpml/controllers folder, edit the FrmWpmlAppController.php file, and make a change on line 606, please?
Basically, just change the code from this:

$keys = array(
                    'name', 'description', 'default_value',
                    'required_indicator', 'invalid', 'blank',
                    'unique_msg',
                );

to this:

$keys = array(
                    'name', 'description', 'default_value',
                    'required_indicator', 'invalid', 'blank',
                    'unique_msg', 'placeholder',
                );

As you can see, now the placeholder is added to that array so it can be made available for translation.

Relevant Documentation:
https://wpml.org/documentation/plugins-compatibility/how-to-translate-formidable-forms-with-wpml/
https://wpml.org/forums/topic/formidable-placeholder-text/

Problem:

HTTP Headers plugin - Call to a member function switch_to_locale() when String Translation is active

https://wordpress.org/plugins/http-headers/

Solution:

1. Take a backup of your site in case something goes wrong.

2. Edit with code editor the following file in the HTTP Headers plugin folder.
/wp-content/plugins/http-headers/http-headers.php

3. Replace the following lines 1417/1418

add_action("added_option", 'http_headers_option');
add_action("updated_option", 'http_headers_option');

with:

add_action("added_option", function() {
     add_action('admin_init', 'http_headers_option');
     add_action("updated_option", 'http_headers_option');});

4. This should solve the fatal error issue when saving the HTTP Headers options.