Available Solutions

Problem:
The client is receiving an error message when entering their WPML registration key.
Solution:
If you're experiencing an issue with your WPML registration key, we recommend you try the following steps:
1. Remove the site registration from your WPML account.
2. Navigate to Plugins -> Add New -> Commercial tab, then click on the link 'Obtenez une clé pour ce site' to obtain a new key and use it to register the site.

If this solution doesn't look relevant, please open a new support ticket.

Problem:
The client is experiencing an issue where importing translations for properties using WP All Import in conjunction with the Estatik plugin results in the translations overwriting the original English content instead of updating it.

Solution:
We recommend the following steps to resolve the issue:

1. Make sure in the last step in the section that "Records in this import file will be matched with properties on your site based on"... TITLE

This is a better option since your titles are unique either way, and if you use a custom field value it may be the same in EN / HR language and may match it and skip import.

- For each record in this import file, every time this import is run... Create new property from records newly present in this import file

This is needed to create new posts in 2nd language that exist in your files but not on the website, otherways they will be skipped, and only update changes will be made to already existing matching posts.

Problem:
The client is experiencing an issue where the Advanced Translation Editor (ATE) displays links with the staging environment path ("/wpml/") after promoting the staging environment to production.
Solution:
We recommend making a minor change to the default language page and then resending the page for translation through WPML > Translation Management. This should update the content and display the correct URLs in the ATE, matching those on the frontend.

If this solution does not seem relevant to your situation, please open a new support ticket with us.

Problem:
The client needs help changing the hover color of the text in the language menu dropdown, as the text turns white and becomes invisible when hovering over the Spanish option.
Solution:
If you're experiencing an issue with the hover color of your language menu dropdown text, we recommend you add custom CSS to your site. Here's how you can do it:
1. Navigate to your site's backend.
2. Go to Appearance > Customizer > Custom CSS.
3. Add the following code, replacing 'red' with your color of choice or a hexadecimal color code:

.sub-menu > li.wpml-ls-item a:hover {<br />    color: red !important;<br />}

4. Save your changes.
This should change the hover color of the text in the language menu dropdown to the color you specified.

If this solution doesn't look relevant to your issue, please open a new support ticket with us.