Problem: You are trying to translate the yacht search bar and results on your site, but despite following previous instructions, the translations are not appearing. Solution: The issue is due to incorrect text domain translations. For example, the "Search Destinations" placeholder in the search form was using the "YACHTER" text domain incorrectly. Here’s how you can fix it: 1) Enable the auto-register option in WPML > String Translation. Follow the steps here: Enable Auto-Register Strings. 2) Visit your site to allow WPML to search for and register all available getText() calls. For example, open this link. 3) Refresh the String Translation page to translate the "YACHTER" text domain directly. Visit: String Translation Page.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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 visit our support forum at WPML Support Forum.
Problem: If you're trying to implement a floating language switcher on your website and it stays in the footer instead of floating as intended, even after adding CSS to the Additional CSS section and clearing the cache. Solution: We recommend inserting the following custom CSS code into WP > Appearance > Customize > Additional CSS:
This should help position your language switcher correctly as a floating element on your page.
If this solution does not resolve your issue, or if it seems outdated or not applicable to your case, please check the related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if the problem persists. You can do so at WPML support forum.
Problem: The client was unable to edit translations on their site, encountering a white page when attempting to access the translation editor. This issue was initially suspected to be related to server resource limits, but even after increasing these limits, the problem persisted. Additionally, the client mentioned that the search bar on the homepage was not translating. Solution: We first addressed the potential server resource issue by suggesting the client to share the error log with their hosting provider, which indicated a memory size exhaustion. This was resolved by the hosting provider. However, the white page issue continued until the client tried accessing the site using the Safari browser instead of Chrome, which resolved the issue. This suggests that the problem was browser-specific. For the untranslated search bar, we created a separate support ticket to handle that specific issue.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to 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 problems persist, please open a new support ticket at WPML support forum.
