Problem: The client uploaded and activated a plugin, but it remained inactive. They were also unsure about the next steps after activation, expecting an automatic duplication of website pages for translation. Solution: We clarified that if the 'Multilingual CMS' plugin is active, the 'OTGS Installer' plugin will stay deactivated as it is only used for installing WPML. If WPML was previously installed on the site, the OTGS Installer would deactivate automatically. We accessed the client's site backend, confirmed WPML was previously installed, and reinstalled but did not activate the 'WPML Multilingual CMS' plugin, allowing the client to activate it at their convenience. For further steps and detailed guidance, we opened a new support ticket specifically addressing the client's questions about what to do next.
Please note that the solution provided might be outdated or not applicable to your specific case. If the issue persists or the solution does not apply, 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 needed, do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You need to change the email address associated with your WPML account and transfer the account management to your client. Solution: To transfer the account to your client, follow the steps outlined in our documentation here: Transferring Account Renewals to Your Clients. This process will ensure that when the subscription is due for renewal, it will renew under your client's account instead of yours. You do not need to pay any additional fees for transferring the account. For any specific actions regarding your current account, such as changing the email address, please contact our Accounts team at hello[at]wpml.org, as we can only assist with technical issues.
If this solution does not resolve your issue or seems irrelevant, we 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 open a new support ticket.
Problem: The client reported issues with their multilingual site where the translated menu was not displaying in Polish, and the HOME button in the Polish version redirected to the English homepage instead of the Polish one, despite having run 'Translate Link Targets' and 'Menu Synch'. Solution: We first needed to identify whether the floating menu was a feature of the theme or a third-party plugin. Upon discovering it was managed by a third-party plugin, we found that the required functionality to redirect the HOME button to the Polish homepage was only available in the PRO version of the Floating Menu plugin. We proceeded by duplicating the floating menu and configuring the language option to ensure it redirects correctly.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: After upgrading from WPML 4.6.3 to 4.6.11, a significant performance regression was observed, specifically with the 'WPML Multilingual CMS' and 'WPML String Translation' plugins. This issue was evident in REST API calls, where the time to execute 7 queries increased from approximately 10 seconds to 55 seconds. Solution: We recommend implementing a workaround by modifying the logic in the plugin files to exclude REST requests. Specifically, in the file
method to check for REST requests before executing hooks. Here is the suggested change:
public function add_hooks() {
if (!strpos($_SERVER['REQUEST_URI'], 'wp-json')) {
add_action('acf/update_field_group', [$this, 'registerGroupAndFieldsAndLayouts']);
add_filter('acf/load_field_group', Fns::withoutRecursion(Fns::identity(), [$this, 'translateGroup']));
add_filter('acf/load_field', [$this, 'translateField']);
add_action('acf/delete_field_group', [$this, 'deleteFieldGroupPackage']);
}
}
Important: Please ensure to make a full site backup (files and database) before implementing this workaround.
Update!
We are soon to release a new version of ACF Multilingual, version 2.1.4. The update will overwrite the fix suggested in this ticket. (In the file: wp-content/plugins/acfml/classes/Strings/FieldHooks.php). Our developer suggests a better workaround that will work with version 2.1.4. Add the following function.
It is important to note that the above snippet will only work with ACF Multilingual version 2.1.4
It's recommended that the snippet be added as a Must-Use plugin. Alternatively, you can add the function to the functions.php file of your theme.
**** Important! Please make a full site backup (files and DB) before you proceed with those steps****
Note: wp_is_serving_rest_request introduced in WP 6.5 relies on the REST_REQUEST global. But keep in mind that standard HTTP requests could also call REST endpoints internally (to pre-load REST request results with the normal request). The client might want to disable the ACF entity translation on a wider scope.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
to create translations of products and find that it does not copy product attributes, you might encounter difficulties in achieving complete product translations. Solution: First, ensure that in WPML > Settings, under Taxonomy translation, the translation preference for Attributes is set to "Copy". If this does not resolve the issue, you can manually copy product attributes using custom code. Here's a step-by-step guide: 1. Create an independent translation of the post in the target language using
4. Set these attributes to the translated product with
$translated_product->set_attributes($attributes);
5. Save the translated product with
$translated_product->save();
If you need further customization, consider hiring a developer from WPML Contractors.
Please note that this solution might be outdated or not applicable to your specific 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 the issue persists, please open a new support ticket at WPML Support Forum.
Problem: If you're experiencing issues with blank fields in the Advanced Translation Editor preventing you from finalizing the translation, we recommend following these steps to resolve the problem.
Solution: 1) Ensure you take a full backup of your site and database before making any changes. 2) Deactivate all plugins except for WPML to check if there is a conflict causing the issue. 3) Delete the existing translation of the problematic page or post. You can find detailed instructions on how to do this at https://wpml.org/faq/how-to-delete-the-translation-of-a-page/. 4) Make changes to the content in the default language, save, and then update the translation. 5) Check if the issue still occurs.
If these steps do not resolve your issue or if they seem outdated or irrelevant to your specific 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: After switching the language URL format from 'Language name added as a parameter' to 'Different languages in directories' in WPML>Languages, the client experienced issues with tag links not updating correctly, resulting in multiple broken links and 404 errors.
Solution: We reviewed the client's website and confirmed that some links were indeed not updated and led to 404 errors. However, upon further inspection, other parts of the site showed links correctly formatted as per the new 'Different languages in directories' setting. This inconsistency might suggest a caching issue. We recommend clearing your site's cache thoroughly and resaving the permalinks. If you're experiencing this issue, try these steps and also run 'Translate Link Targets' from WPML>Settings to ensure all links are correctly updated.
If the problem persists, it might be due to an outdated solution or a different underlying issue. 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 these steps do not resolve the issue, please open a new support ticket at WPML support forum for further assistance.
Problem: You are unable to find the bottom blocks of your theme in the WPML string translation interface, and you are finding the new version of WPML confusing.
Solution: First, ensure you have checked the Admin Strings section as some strings might appear there. Additionally, follow the steps in our guide on Finding Strings that Don't Appear on the String Translation Page to bring those strings into String Translation. If the blocks are part of a widget or an element from a theme or page builder, you might need to make them recognizable by WPML. For detailed instructions, please visit How to Register Page Builder Widgets for Translation.
If this solution does not apply to your case because it might be outdated, or if you are still experiencing issues, 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client was unable to see the German translations on their website despite having translations pending for review. The issue was twofold: SQL server settings interfering with the query execution and unregistered custom Elementor widgets not appearing in the translation editor. Solution: First, we identified that the SQL server's ANSI_QUOTES mode was causing the term 'local' to be misinterpreted. We recommended the client to request their server support team to disable the ANSI_QUOTES mode globally for MySQL. After this adjustment, the translations queue began to function correctly.
Secondly, the issue of English content still appearing on the translated pages was due to the use of default Elementor widgets from a theme not listed in our compatible theme directory. We advised the client to register these widgets for translation by following our guide: Registering Custom Elementor Widgets for Translation. Additionally, we suggested contacting the theme author to join the WPML Go-global program to ensure compatibility.
If these solutions do not resolve your issues or seem outdated, we 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.
Problem: If you're experiencing issues with translating individual words in the Animated Headline Widget from Elementor using WPML, where the plugin treats all the words as one long sentence instead of recognizing them as individual strings, resulting in the translated version displaying all the words together rather than rotating them. Solution: We recommend the following steps: 1. View the translated version of your page. 2. Click on "edit with Elementor" from the WordPress topbar to open the translation in the Elementor editor. 3. Manually edit the widget to add the translations for each word and then update.
If this solution does not resolve your issue or 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 the problem persists, please open a new support ticket.
Problem: You are trying to change the default currency that was automatically set up according to the country of your website, specifically from Bulgarian Lev to Euro. Solution: We recommend managing the default currency through WooCommerce settings. Here are the steps you can follow: 1. Sign in to your WordPress dashboard. 2. In the left-side menu, select WooCommerce, and then select Settings. 3. Ensure that the General tab is selected on the top menu. 4. Scroll down to the Currency options section. 5. Next to Currency, select the currency you want to use, in this case, Euro. 6. Select Save Changes. For more detailed guidance, refer to the WooCommerce documentation on changing shop currency: WooCommerce Currency Settings.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML Support Forum.
Problem: The client is unclear about the publishing process and status management of translated pages using WPML, including how to view, publish, draft, or delete translated pages. Solution: To manage the publishing status of translations, navigate to WPML → Settings and scroll to the Translated documents options section. Here, you can set translations to be saved as drafts or have the same status as the original language content. For more details, visit documentation.
Depending on the translation mode, different review options are available under WPML → Settings → Translation mode. These options include reviewing translations before publishing, publishing translations and reviewing them later, or publishing translations without reviewing. For further information, check out documentation.
To view a translated page, you can either review the page and use the option to view it or switch to the translation using the language switcher on the default language version of the page.
If a translated page is published and needs to be made invisible, you can change its status to draft or under review by going to pages/posts, clicking on the secondary language, finding the page/post, and using 'quick edit' to switch to 'draft'.
To delete a translated page, navigate to pages, click on the secondary language, select the translation, and delete. This can also be synced so that deleting the default language page will also delete the translation. More details can be found at documentation.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also highly suggest 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.
Problem: If you're experiencing an issue where attempting to access a translated page URL like /es/try/ results in a 301 redirect to a different page such as /es/work/trial/, this might be due to the non-existence of the /es/try/ URL in your site's sitemap, causing WordPress to redirect to the closest possible match. Solution: We recommend checking the actual URL of the translated page. You can do this by visiting the page at /es/am-descarga/. Once there, click on 'edit page' in the WordPress top bar to open the WP editor. Here, you should edit the permalink to change it from /am-descarga/ to /try/. This should resolve the redirect issue.
If this solution does not apply because it's outdated or not relevant 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 the issue persists, please open a new support ticket.
Problem: The client was unable to translate certain custom fields using Advanced Custom Fields (ACF) and WPML's Advanced Translation Editor (ATE), despite setting the fields as translatable. The issue was due to multiple fields having the same name across different field groups, which caused WPML to apply the same translation settings to all similarly named fields. Solution: 1. Verify that the field groups in ACF are set to 'translatable' under ACF -> Fields groups. 2. Ensure that in WPML -> Settings, the field groups for ACF are set to 'untranslatable' if they should not be translated. 3. For fields that need to be translated, ensure each field name is unique across all field groups to avoid conflicts in translation settings. 4. If the issue persists with existing content, make a minor edit in the default language and update the page. Then, access the translation editor where the field should now be available for translation.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, we 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is using Avada Builder for their website and wants to automatically translate German pages into English using WPML and DeepL. However, not all texts on the pages are being translated. Solution: We identified that the Rank Math SEO plugin is causing issues with redirection that might affect the translation process. We recommend checking the redirection rules set in Rank Math SEO -> Redirection and consider disabling unnecessary redirections that could interfere with WPML's translation capabilities. Additionally, it's important to ensure that the homepage is translated into all required languages (Czech, Dutch, French, Italian, and Russian) to enable proper functioning of the Language Switcher and other links.
If this solution does not resolve your issue or 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. Should further assistance be needed, please open a new support ticket at 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
