Problem: The client is experiencing issues with the search tool on their website, which works fine in the primary language (French) but does not return any results in the secondary language (German). The theme used, Zourney, is not officially compatible with WPML, which might be causing the issue. Solution: We recommend contacting the theme's author to discuss a potential quick fix, as the theme needs to adapt its code to handle translated posts/results in multiple languages. Specifically, they can implement WPML hooks such as
Additionally, you can invite the theme developers to join our GoGlobal program, where our developers will assist in making the theme compatible with WPML. More information can be found here: https://wpml.org/documentation/support/go-global-program/.
If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket at WPML support forum.
Problem: The client reported that while duplicating booking objects (Custom Post Type) on their multilingual website, the tours page displayed correctly in French and English, but no content was shown in Italian and German. Solution: We discovered that the issue was related to the settings of the BABE plugin not being consistent across different languages. To resolve this, we advised the client to: 1. Navigate to BA Settings > General tab. 2. Switch to the Italian language. 3. Set the option
Return search results without checking availability if no dates are specified
from 'No' to 'Yes'. 4. Save the changes. This adjustment ensures that the plugin's behavior aligns across all languages, as it supports saving options per language.
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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.
Problem: The client needed assistance with translating slug strings for a page, which worked in some languages but not in others. Solution: We recommended that if you're experiencing issues with translating slug strings, you should first try to edit the page in the original language and then switch to the second language to change the page slug. Additionally, we provided a step-by-step guide on how to translate page slugs using the Advanced Translation Editor. You can follow the instructions in our documentation here: Translating Page Slugs.
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 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 don't hesitate to open a new support ticket in our forum: WPML Support Forum.
Problem: If you're using The Events Calendar plugin and have translated the events slug in WPML, but the language switcher doesn't show the other languages unless you access the page directly via link (e.g., /it/events), where the switcher then displays normally. Solution: First, ensure that you have translated the Events into the respective languages. If the Events are not translated, they will not appear in the language switcher. For example, if the Event archive displayed only French in the language switcher, it indicates that Events are only available in French. Once you translate an Event into another language, such as English, the language switcher will start to include that language as an option.
If you want to show the default Events (in French) for other languages when translations are not available, you can adjust the WPML settings. Go to WPML > Settings > Post Type Translation and set the translation preference for the "Events" post type to "Translatable - use translation if available or fallback to default language". This setting will allow the default language events to be displayed in the language switcher even if they are not translated into other languages.
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 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 you still need assistance, please open a new support ticket.
Problem: The client was experiencing issues with translations being lost upon refreshing the dashboard page and difficulties adding some strings to the basket for translation.
Solution: We recommended the following steps: 1. Create a minimal environment by deactivating all non-WPML plugins and switching to the standard WordPress theme. 2. Navigate to WPML > Support > Troubleshooting and click on the button "Show custom MO Files Pre-generation dialog box". Additionally, we emphasized the importance of backing up the database and website before proceeding, suggesting the use of the Duplicator plugin.
For the specific issue with the BABE plugin settings not being saved, we clarified that each language has its own settings and advised the client to switch languages using the language switcher at the top bar and save settings for each language individually, rather than using 'All languages'.
If these steps do not resolve the issue or if the solution does not seem relevant, please open a new support ticket with us for further assistance.
Problem: When attempting to switch languages on the website, an error occurs, which seems to be related to the theme file
class-ba.php
on line 199. Solution: We recommend contacting the theme author to inquire about the functionality of the specific line that is causing the error. It is likely that the issue is not directly related to WPML but may be due to some configuration or an element that requires translation. Once the theme author provides clarification on the error, please inform us so that we can assist further.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
