Problem:
I'm seeking assistance with loading header menu and footer from external files and ensuring their text content is automatically translated. Additionally, CSS styling for the translation switcher on index.php is not being applied.
Solution:
For the header menu, if it's a WordPress menu, you can follow WPML documentation for translating menus: https://wpml.org/documentation/getting-started-guide/translating-menus/. If it's not a standard WordPress menu, you'll need to wrap all text inside PHP code with the gettext method and then translate them using WPML String Translation.
For the footer, if it's widget-based, follow steps for translating widgets: https://wpml.org/documentation/getting-started-guide/translating-widgets/. If it's directly added to the theme, wrap text in PHP code with the gettext method, scan the theme for strings, and translate them using WPML String Translation.
To apply CSS to the translation switcher on index.php, wrap all direct text in PHP code with functions like __() and then scan the theme for strings. Translate them using WPML String Translation, and the CSS should apply automatically.
Problem: The client was experiencing an issue with the splitting of Arabic letters in titles on their slider. Solution: We informed the client that the issue with the splitting of Arabic letters seems to be related to the slider itself and not WPML. To confirm this, we suggested the following steps: 1. Deactivate WPML. 2. Create a new page and add the slider. 3. Insert Arabic words into the slider. 4. Observe if the same issue occurs with WPML deactivated. If the issue persists, it confirms that it is not related to WPML and the client may need to check the slider settings or contact the slider's support team for further assistance.
Please note that the solution provided 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 help, please open a new support ticket with us.
Problem: The client needed assistance with two issues: first, the European Union logo on their site was not changing to display "European Union" in the international versions of the site. Second, they were experiencing problems with having different contact forms for each language version of the site using UX Builder, as translations would revert to the default Polish version. Additionally, they inquired about handling forms from Pipedrive and Contact Form 7 plugin for different language versions.
Solution: For the logo issue, we did not receive information about the solution provided. Regarding the contact forms, we suggested two steps: 1. To translate the Webform URL, search for "HTTP" using the provided search form and replace the URL with the correct language form URL. 2. To have separate forms for each language, create a distinct form for each language. This approach is necessary because translating the form using WPML's contact option will not create separate versions for secondary languages. For more information on using Contact Form 7 with WPML, visit this documentation.
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 you still need assistance, please open a new support ticket here.
Problem: The client is experiencing an issue where emails sent from the translated Contact Form 7 are not being delivered to the intended recipient's email address, but instead to a different one. Solution: If you're experiencing this issue, we recommend following our guide on Using Contact Form 7 with WPML. To check the email notification settings of the translated form, please follow these steps: 1. Edit the original form. 2. Switch to the translated form using the top admin bar. 3. Check the email settings under the "Mail" tab.
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 you still need assistance, please open a new support ticket.
Problem: The client's website went down after updating WPML, and they encountered an error list from the debug.
Solution: 1) We suggested that the issue might be due to an incorrect update process, resulting in missing files. We recommended manually downloading and installing the necessary files from the provided links:
Additionally, we recommended creating a full website backup before proceeding with any changes to ensure there is a recovery option available.
The client later confirmed that updating the translation and multilingual components resolved the issue, and they disabled auto-updates to prevent similar problems in the future.
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 you still need assistance, please open a new support ticket.
Problem: The client was experiencing issues with translating individual links in the menu. While the pages were translating correctly, custom links such as "Unterkünfte" or "Über uns" were not translating and were directing to the wrong language version.
Next, we suggested the client to adjust the links to point to the correct language version by: 1. Going to WPML -> Settings. 2. Clicking on "Translate Link Targets". 3. Clicking the "Scan now and adjust links" button.
Finally, for links within Elementor templates, we instructed the client to: 1. Switch to the desired language. 2. Edit the page with Elementor. 3. Click on the element that contains the link. 4. Change the link address in the element settings.
We advised the client to follow these steps for each link that needed translation and to check if the issue was resolved.
If the provided solution does not apply or is outdated, or if further assistance is needed, 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 the latest versions of themes and plugins are installed.
Problem: The client is experiencing issues with the Affirm payment gateway on their bilingual English and French Canadian WooCommerce site. When trying to checkout in French, the Affirm checkout flows remain in English. The client suspects this might be due to the default locale values being set to "en_US" and "fr_FR" instead of "fr_CA" for the Canadian locale.
Solution: We confirmed that default locales are editable and that the client correctly changed the locale to "fr_CA". However, changing the locale can cause issues with WooCommerce translations because they are tied to the default locale. To address this, the client can either translate the missing strings themselves or install the French Canadian language pack. For the Affirm issue, we suggested checking if the Affirm WooCommerce plugin integration can be translated via String Translation. Additionally, we pointed out that the Affirm documentation requires adding a script with specific locale and country code parameters. Since WPML requires two locales for bilingual sites, the client might need to load a different script for French pages. We acknowledged that this is a complex issue that may require the cooperation of the Affirm author and suggested that the client contact one of our contractors for further assistance.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If so, 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 you need further assistance, please contact us on the WPML support forum.
Problem: The client needed to migrate or change the language of multiple posts from the default language to another language within a custom post type created using ACF multilingual. Solution: We informed the client that WPML Export and Import can be used to export and import posts into different languages. However, it is necessary to import the posts in the default language first and then import the translations to establish the correct connections between them. We provided the client with documentation links for detailed instructions:
If the provided solution is not relevant due to being outdated or not applicable to your case, we recommend opening a new support ticket. We also highly suggest 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.
Problem: The client unintentionally translated their page builder, Beaver Builder, when adding new languages and is unsure about which settings to adjust to prevent or reverse this. Solution: We recommend checking the "WPML > Settings > Post Type Translation" section. Here, you can set the translation preference for Templates (identified as
fl-builder-templates
) and Layouts (
fl-theme-layout
) to "Translatable" if you wish to translate them. If you do not want these to be translated into new languages, you should set their translation setting to "Not Translatable" within the same section. If this does not resolve your issue or if the problem is different, please provide us with more details or screenshots to better understand the situation and assist you further.
Please note that the solution provided 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, do not hesitate to open a new support ticket. You can do so by visiting the WPML support forum.
Problem: The client was experiencing an issue where the language switcher was not redirecting to the Greek version of the site when selecting 'EL'. The language switcher was implemented as a shortcode in Woodmart's Header builder under 'Header Minimalism'. Solution: We identified that a block of code in the .htaccess file related to the GTranslate plugin was causing the issue. The code looked like this:
### BEGIN GTranslate config ###
...
### END GTranslate config ###
After removing this block of code from the .htaccess file, the language switcher started working correctly. If you're experiencing a similar issue, we recommend checking your .htaccess file for any remnants of the GTranslate plugin or similar configurations that might be interfering with the language switcher functionality.
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 need further assistance, please don't hesitate to open a new support ticket with us.
Problem: The client reported that despite having installed, activated, and licensed the WCFM Ultimate Plugin, the dashboard was still prompting to purchase the plugin. Solution: We first confirmed that there are no known compatibility issues with the WCFM Ultimate Plugin, except for the "Policy" page, which is documented here: https://docs.wclovers.com/wcfm-wpml/. We then suggested that the issue might be related to permalinks settings, which differed from those in our Sandbox environment. We recommended that the client contact WCFM support for further assistance, as the issue could not be reproduced from scratch, indicating that it might not be a general compatibility issue that we could address with a code patch.
If you're experiencing a similar issue, we recommend checking your permalinks settings and reaching out to WCFM support for help. 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 need further assistance, please open a new support ticket with us: WPML support forum.
Problem: If you're experiencing performance issues when copying Advanced Custom Fields (ACF) to translations with WPML, such as slow operations or timeouts, this might be due to inefficiencies in the code handling the copy process.
Solution: We recommend modifying the
SitePress::copy_custom_fields
and
WPML_Copy_Once_Custom_Field::copy
methods to improve performance. Here are the steps to follow:
These changes should optimize the process by reducing the number of instances where the entire post meta is fetched and looped through, thus improving the performance when copying ACF fields to translations.
Problem: The client has migrated their database from pre-production to production and encountered an error message regarding the use of automatic translation credits on both environments. Solution: We recommend selecting the 'Yes (copy)' action to share credits between the sites. This will allow the client to manage the credits independently while ensuring that the translation memory is shared, regardless of whether the sites have different content. For more detailed guidance, we suggest consulting our documentation on Automatic Translation Subscription for Multiple Sites.
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 open a new support ticket in our support forum.
Problem: The client reported that automatic translation was not starting on their website.
Solution: We found that the site UUID on the client's site did not match the one on our server. We corrected this issue, and now the automatic translation should work properly.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the problem 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 open a new support ticket.
Problem: The client is unable to connect to the WPML Advanced Translation Editor.
Solution: For this issue, we recommend the following steps: 1. Navigate to Plugins > Add new > Commercial tab. 2. Un-register and then re-register your site with a new sitekey. 3. Go to WPML > Settings > Translation Editor. 4. Select Editor for new translations: Classic Translation Editor and save. 5. Reload the page and switch back to the Advanced Translation Editor. For detailed instructions, please refer to our documentation:
Please note that the solution provided 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 necessary, do not hesitate to open a new support ticket for further assistance. You can do so at the WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
