Problem: The client needed to add alternative text to flag icons for SEO purposes. They were able to add alt text to SVG icons using the Optimole plugin but encountered issues when trying to add alt text to custom flags uploaded through WPML, as WPML only allows uploading flags from computer files. Solution: We informed the client that it is not possible to add alt text to custom flags through the media folder in WPML. However, alt text for flags should automatically be activated when the language switcher is set to display only flags, without the language name. We provided a link to the documentation on how to add a custom flag: https://wpml.org/documentation/getting-started-guide/language-setup/language-switcher-options/custom-language-flags/#how-to-add-a-custom-flag Additionally, we referenced a forum post that might help with the issue: https://wpml.org/forums/topic/accessibility-issues/#post-15063367
If this solution does not apply to your case, or if it is outdated, 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. For further assistance, please contact us in the WPML support forum.
Problem: The client was experiencing issues with translating pages using Advanced Custom Fields (ACF). Some ACF fields were available for translation in certain languages but not in others. Additionally, even when ACF fields were translated, they sometimes did not display correctly on the website. Solution: 3. We were unable to access the PHP templates to check how the blocks were created and displayed on the frontend. However, we reminded the client of the importance of ensuring unique field names across different field groups, as mentioned in our documentation. We noticed that the fields named "title" and "description" might be too standard and could be causing conflicts.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, 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 with us.
Problem: The client noticed server activity logs showing an "Unknown Guest" with an IP address (44.213.71.100) suspected to be related to WPML. This activity was recorded when the client's developer was editing translations through WPML's Advanced Translator.
Solution: We investigated the issue and determined that the IP address is from the United States - Virginia, which could be an AWS server or someone using a VPN. We asked the client to consider if anyone else had access to the site, if credentials were shared publicly, or if they worked with a supporter who might be from the United States or using a VPN. We also recommended changing credentials for safety. After further investigation and communication with our development team, we concluded that the activity might not be related to WPML. The client's hosting service, Rocket.net, uses a server-side tool that we do not have control over, and it is difficult to determine the source of the activity. Our team also noted that during translation updates, multiple requests are sent, not just two, which the tool logged. Since the tool operates server-side and not within WordPress, and there are no other similar reports, it is challenging for us to provide a definitive solution.
If you're experiencing similar issues with activity logs and suspect it might be related to WPML, we recommend checking your server logs for any unusual activity and considering the points we raised with the client. However, please note that this solution might be irrelevant due to being 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 need further assistance, please open a new support ticket.
Problem: If you're experiencing issues with translating the 'Read More' button text in the Kadence Post Grid block, we have a solution for you. Solution: First, add the following custom XML configuration to your site:
You can do this by navigating to WPML > Settings > Custom XML Config. After adding the custom XML, edit the button text on your homepage, save the page, and translate it again. We have also escalated the issue to our compatibility team and updated the wpml-config.xml file for Kadence. We are currently testing the plugin and collaborating with the author to resolve any issues. If this solution doesn't seem relevant to your problem, please open a new support ticket with us.
Problem: After migrating from staging to live, some pages in WPML Advanced Translator were showing incorrect domain links, pointing to the staging site instead of the live site. Solution: If you're experiencing incorrect domain links in WPML Advanced Translator after a site migration, we recommend the following steps: 1. Open the post in the editor and check if the link is pointing to the correct location. If it's still directed to the staging site, update the link manually or use the Better Search and Replace plugin to update the links throughout your site. 2. After updating the links, navigate to WPML > Settings and scroll down to the "Translate link Targets" section. 3. Click on the "Scan now and adjust links" button and wait for the process to complete. 4. Check if the staging site link is still appearing in the Advanced Translator Editor (ATE). If this solution doesn't look relevant to your issue, please open a new support ticket with us.
Problem:
I'm receiving a warning that the WPML plugin can't connect to WPML.org, and I need this checked in my logs.
Solution:
There's a significant chance that what you are seeing is a false positive that has been cached on the server. This notification will likely be automatically removed when the cache clears on its own.
To verify if it's a false positive, follow these steps:
1. Go to your WordPress dashboard.
2. Navigate to "Plugins" > "Add New" > "Commercial."
3. Click the "check for updates" button.
If the page refreshes and WPML is still showing as registered, then it is indeed a false positive, and you don't need to worry about it.
