Problem: The client is new to WPML and is confused about why the OTGS Installer is deactivated and cannot be activated. Additionally, the client is waiting for the new version of WPML to appear on the WP plugin page. Solution: We informed the client that the WPML 4.6.10 version has been released and recommended visiting Plugins > Add New > Commercial tab and clicking on the Check for updates button to refresh the installer caches and get the automatic upgrade links for the latest version of WPML. We also clarified that the OTGS Installer is not mandatory for upgrading WPML and is mainly used for the initial installation of the plugin.
If this solution does not apply to your situation because it might be outdated or not relevant to your case, we suggest opening a new support ticket. 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 further assistance is needed, please contact us on the WPML support forum.
Problem: If you're experiencing this issue *The Advanced Editor jobs synchronization has failed*, we have identified a bug and have released an errata. Solution: 1. Please refer to the errata article for more details: WPML 4.6.9 Advanced Editor Job Synchronization Warning. 2. Our developers have fixed this bug in the latest version of WPML. We recommend you to upgrade to the latest version (4.6.10 series) after a full site backup. 3. You can find more details about the update here: WPML 4.6.10 and WCML 5.3.6 Ready for WordPress 6.5.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists after following the steps above, we highly recommend checking related known issues at WPML 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 was experiencing an issue with extra white space appearing between the first and second line in the Dutch version of their website header, which was not present in the English version. Solution: First, we recommended checking our documentation on Translating Elementor Templates to ensure the translation process was followed correctly. Upon further inspection, we noticed that the text
<p>Dr. Edwin Winkel Consultancy</p>
contained an extra
<p></p>
HTML element, which was causing the additional space. We suggested that the client edit the text "Dr. Edwin Winkel Consultancy", make some changes to the original, and then re-save the translation to see if the issue with the extra HTML elements persists.
If the solution provided here is not relevant to your case, either because it's outdated or it doesn't apply to your situation, 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 unable to see the language switcher on the English version of the front page, and when clicking the logo, they were redirected to the Dutch 404 page. The client had already tried duplicating the page with Yoast Duplicate Post as suggested by another supporter, but the issue persisted.
Solution: We recommended the following troubleshooting steps to try and reconnect the translation to the page: 1. Make a full backup of the website. 2. Navigate to WPML > Support and click on the Troubleshooting link. 3. Click on the following buttons:
Clear the cache in WPML
Remove ghost entries from the translation tables
Fix element_type collation
Set language information
Fix WPML tables collation
Assign translation status to duplicated content
Fix terms count
Fix post type assignment
Cleanup and optimize string tables
After performing these steps, we asked the client to check if the translation appeared.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 wanted to display the flags in the WPML Language Switcher without rounded corners, as they were appearing with rounded corners contrary to their expectation.
Solution: We suggested that the client add custom CSS to their site to override the default styling. We provided the following CSS code to be inserted into WP > Appearance > Customize > Additional CSS:
img.wpml-ls-flag {border-radius:0px!important;}
We also reminded the client that any code snippet provided is for educational purposes and is not part of our support scope, which means we do not maintain or debug custom code.
If this solution does not apply to your situation, or if it seems outdated, we recommend opening a new support ticket. We also 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 further assistance is needed, please contact us through the WPML support forum.
