Available Solutions

Problem:
The client's domain has been up and running for years, and WPML is asking to confirm the new site to the IP address, even though the client never uses the IP address to access their site.
Solution:
We recommend that if you're experiencing a similar issue where WPML is prompting you to confirm a site using an IP address instead of a domain name, you should select that you are using the domain and not the IP address. Before making any selections or changes, it's crucial to:
1. Create a full website backup. This ensures that you have a restore point in case anything goes wrong.
Server settings or changes can sometimes trigger notices like the one mentioned. As long as you confirm that you are using the domain, everything should work correctly.

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

Problem:
The client needed to prevent the "Pin it" button from appearing on the language flag images on their website. The "Pin it" button developer suggested adding a 'nopin' attribute to the images, but they were unable to do so as the images were added by the theme or translation plugin.
Solution:
We recommend considering a different approach since custom code modifications can be lost with future updates. The plugin that adds the button should ideally provide an option to exclude certain images or site areas from having the button applied. Alternatively, the client could switch to using language names or abbreviations instead of flags. If the client is not comfortable with coding, we suggest hiring a WPML contractor from https://wpml.org/contractors or a developer to implement the required changes. It is important to save any custom code and know where to reapply it after updates to avoid losing the modifications.

Please note that this solution might be outdated or not applicable to your case. If this doesn't resolve your issue, 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 you still need assistance, please open a new support ticket with us.

Problem:
The client needed assistance with editing and translating the 'About me' widget, as they were unable to find the correct string translation.

Solution:
1. We noticed that the client had already created a Dutch (NL) version of the widget, but it was set to display in both languages.
2. We directed the client to the Widgets section of their WordPress dashboard, where they could edit the widget's content and adjust language display settings.
3. We provided a screenshot to guide the client in selecting the correct option to ensure that each widget appears only in its respective language.
4. We also shared a link to our documentation on translating widgets with WPML for further assistance:
https://wpml.org/documentation/getting-started-guide/translating-widgets/

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 recommend opening a new support ticket. We also 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 further assistance is needed, please contact us in the WPML support forum.

Problem:
The client was trying to figure out why the main site logo was missing on pages that had been translated.

Solution:
1. We requested temporary access to the client's site to better understand the issue.
2. After debugging, we discovered that the ACF field group containing the Theme options was not translated, which likely caused the logo to only appear in certain languages.
3. We instructed the client to set the field group to "Different fields across languages" by following our documentation here: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/#choosing-how-to-translate-field-groups.
4. We then had the client go to the "Theme Options" and re-add the logo for each language by clicking "X" next to the image, re-adding it, and saving.
5. The client confirmed that the logo now appears correctly in each language.

If you're experiencing a similar issue, we recommend following the steps above. However, this solution might be irrelevant if it's outdated or not applicable to your case. If you need further assistance, please open a new support ticket and check related known issues at https://wpml.org/known-issues/. We highly recommend verifying that you have installed the latest versions of themes and plugins. For further assistance, please contact our support forum at https://wpml.org/forums/forum/english-support/.

Problem:
The client is receiving a message that the WPML plugin cannot connect to wpml.org, which is necessary for checking new versions and security updates. The issue might be due to network or security settings blocking outbound communication.
Solution:
We recommend checking if the issue is a false positive caused by server caching. To do this, navigate to Plugins > Add New > Commercial and click the "check for updates" button. If after the page refreshes, WPML still shows as registered, then it is likely a false positive and the notification should disappear once the cache clears.
If the problem persists, it might be because WPML is not currently registered. We will address the site key issue in a separate ticket.

Please note that this solution might not apply to your case if it's outdated or simply not relevant to your specific issue. 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 continues, please do not hesitate to open a new support ticket with us.

Problem:
The client installed WPML on their website and encountered issues with widgets not being translated correctly, particularly the text and link of a button within a widget. The widgets were only visible in the theme customizer and not in the legacy WordPress widget area.

Solution:
We noted that the Industrium theme used by the client is not officially compatible with WPML, but the theme's team does mention WPML compatibility. During our investigation, we focused on the 'Contact Us' button string in the footer widget. We located the widget in the 'Customize -> Top Footer bar' and found all possible strings in 'String Translation' and 'Admin screens' (WPML->String Translation->Translate Texts in Admin Screens), but the URL and translation remained in Italian. We advised the client to change the language of any strings picked up in the wrong language by selecting them and clicking on 'change language of selected' strings.

As a test, we installed the Classic Widgets plugin, which allowed us to register the string again in string translation, resulting in the string being correctly translated. We recommended the client to use the Classic Widgets plugin to revert to the classic view of 'Appearance->Widgets' for a more accurate and reliable translation of widgets.
Translating Widgets documentation

Please note that this solution might be irrelevant if it's outdated or not applicable to your case. 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 issue persists, please open a new support ticket.