mickd-3

Problem:
The client is trying to translate the button URL in the Woodmart theme using WPML but cannot find the way to do so.
Solution:
We recommend trying two methods to locate and translate the button URL:
Method 1:
Navigate to WPML > String Translation and at the bottom of the page, check the option "Look for strings while pages are rendered." Then, visit the front end of the page where the string is displayed, and return to WPML > String Translation to search for the string.
Method 2:
If the string is not found in WPML > String Translation, it might be included as an admin text string. You can follow the process outlined in our documentation on how to find and translate admin text strings: Translate Admin and Settings Strings and Finding Strings that Don't Appear on the String Translation Page.
Please note, if the strings originate from outside of WordPress, WPML may not be able to detect or translate them.

If this solution does not resolve your issue or 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 the problem persists, please open a new support ticket.

Problem:
If you're experiencing an issue where the header color on your translated site is not displaying properly,
Solution:
We recommend following these steps:
1. Navigate to WPML >> Settings.
2. Scroll down to the "Custom Fields Translation" section.
3. Click on the "Show system fields" link.
4. Search for the "_woodmart_whb_header" field.
5. Set it to "Copy" and press the "Save" button.
6. Re-save the default language home page to apply the field settings to the translated home page.
After completing these steps, please clear your mobile browser cache and check if the issue is resolved.

If this solution does not apply because it might be outdated or not suitable for your case, 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 the issue persists, please open a new support ticket.

Problem:
The client reported that the WPML plugin could not connect to wpml.org, and a warning appeared in the WordPress backend despite no changes being made to WPML settings.
Solution:
We suggested that the issue might be a false positive due to server caching and that it could resolve itself when the cache clears. To verify this, we recommended the following steps:
1. Navigate to Plugins > Add New > Commercial.
2. Click the "check for updates" button.
3. If the page refreshes and WPML shows as registered, then the warning is indeed a false positive.
The client followed these steps and confirmed that WPML is connected to the API, indicating that everything should work normally.

Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still experiencing issues, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket with us.