Problem: The client was unable to filter out products from a specific category on the front page using WPML for their multilingual WooCommerce site. The provided code snippet worked in the default language (Czech) but not in the translated language (English). Solution: We pointed out that the English category had only one product translated, and for the filter to take effect in the second language, the client needed to translate the rest of the products. If this solution doesn't look relevant, please open a new support ticket.
Problem: The client was experiencing a fatal error when trying to install WPML String Translation on their WordPress site. The error message indicated an undefined method call to
WP_Textdomain_Registry::reset()
.
Solution: We recommended that the client should upgrade the WPML String Translation plugin to version 3.2.3 or greater, as this version is required for WordPress version 6.1 or higher. Before upgrading, it is crucial to perform a full site backup. After the backup, the client should update the plugin and check if the issue persists. For more details on the upgrade process and the importance of compatibility with WordPress 6.1, the client can refer to our documentation:
Problem: You are trying to translate the messages and preview in Everest Forms on your website, but they do not appear in the items to translate. Solution: We recommend navigating to WPML => String Translation. Once there, search for the text that is missing translation, such as "Last Name". If you find the string that belongs to Everest Forms, ensure you translate it. If you are unable to locate the missing strings in String Translation, or if this solution does not seem relevant to your issue, please open a new support ticket with us for further assistance.
Problem: The client is using WPML with WooCommerce, a filter products plugin (WBW), and Divi to create a catalog of dogs for adoption. After installing the WooCommerce WPML plugin, the client translated the content but then realized the WBW filter plugin was not compatible with the translated versions. The client wants to revert the shop page to English only, as the filter does not work on the translated page, and has already deleted the Spanish version of the shop page and the WooCommerce WPML plugin.
Solution: We recommended the following steps: 1. Navigate to WPML > Translation Management. 2. Check the box on the left for the "Shop" page. 3. Scroll down and select "Duplicate". 4. Duplicate the content from the default language to the other one. This process does not translate the content but copies it from the default language, which could resolve the issue with the filter plugin.
If this solution does not seem relevant or does not resolve the issue, we encourage the client to open a new support ticket for further assistance. They can do so by visiting the WPML support forum.
Problem: The client is unable to download their translation invoices for specific months directly from the WPML website due to a bug that prevents the invoices from being displayed when clicking on the invoice tab. Solution: 1. We asked the client to check their email inbox, as invoices are typically sent out each month. 2. We emailed the requested invoices directly to the client. 3. We requested the client to mark the support ticket as resolved once they have received the invoices.
If this solution doesn't look relevant to your issue, please feel free to open a new support ticket.
Problem: If you're unable to see your contact forms in the backend and cannot edit them, even though they appear on the frontend, and you notice that the language tabs under Contact Form 7 are missing, despite having the Contact Form 7 Multilingual plugin installed. Solution: We recommend you follow the steps provided in the custom search results that address similar issues with Contact Form 7 and WPML. Here is the link to the search results:
Please try these solutions and let us know if your issue is resolved.
If this solution doesn't seem relevant to your situation, we encourage you to open a new support ticket with us for further assistance. You can do so by visiting the WPML Support Forum.
Problem: The client is experiencing a fatal error caused by an undefined function wp_enqueue_block_style() in the WPML plugin's block editor loader file.
Solution: If you're experiencing a similar issue, we recommend the following steps: 1. Create a full backup of your site. 2. Update WordPress to the latest version, currently 6.4.2. 3. Update WPML to the latest version, currently 4.6.9, and check if the issue persists. 4. If the problem continues, perform a compatibility check by: a) Switching to a default WordPress theme, like Twenty Twenty-Three. b) Deactivating all plugins except WPML CMS. c) Reactivating plugins in small groups to identify any conflicts. d) Reverting to your original theme. 5. If the issue is not resolved, provide us with your Debug Information following these steps: a) Navigate to WPML > Support > Debug Information. b) Copy the Debug Information. c) In the 'Additional Data' section of our support forum, expand the 'Debug Info' item and paste the copied information.
Please perform these actions on a staging site to prevent any disruption to your live site. For detailed information on the compatibility issue, you can refer to our errata page here: WPML and WordPress 4.7 Compatibility Issue.
If this solution doesn't seem relevant to your situation, please open a new support ticket in our forum: WPML Support Forum.
Problem: The client's website uses WPML and is built with WordPress on the Bedrock framework. The website does not show as registered, and attempting to register results in an error. The site's SiteURL and HomeURL are different, which may cause issues. Solution: We recommend making the SiteURL and HomeURL the same, which can be done in the wp-config.php file or through the WordPress admin settings. After aligning the URLs, follow these steps: 1. Temporarily remove your website from your WPML account sites list here: https://wpml.org/account/sites/ 2. Add the website again, ensuring the format matches the SiteURL (e.g., 'https://www.domain.co.uk/'), and copy the new key. 3. Update the wp-config.php file with the new key by setting the value of the constant OTGS_INSTALLER_SITE_KEY_WPML to the new key.
If this solution does not resolve your issue, please open a new support ticket with us for further assistance: WPML Support Forum
Problem: The client is unable to cancel old translation jobs and is encountering an error message stating 'This action does not apply to any of the jobs.' Additionally, the client needs to update translations of some pages but the latest text in the source language (EN) is not showing. Solution: If you're experiencing issues with old translation jobs that cannot be cancelled and need to update translations for your pages, we recommend the following steps: 1. Navigate to WPML->Translation Management->Dashboard. 2. Select the page you wish to re-translate. 3. Re-send the page for translation with automatic translation to refresh the translation. Alternatively, you can: 1. Edit the page you want to update. 2. Make a small edit and then update the page. 3. After updating, you should be able to send the page for translation. For issues related to translating Advanced Custom Fields (ACF), please install and activate the ACF Multilingual add-on plugin. You can download and activate the plugin by going to Plugins->Add new->Commercial tab. For further guidance, review the documentation on translating sites built with ACF:
Problem: The client is experiencing an issue where changes or additions to the layout of the default language page are not displayed on the front end after translating with the WPML Translation Editor. The ACF Flexible Content field is set to 'Copy once' and on 'Expert' option. Solution: We recommend setting the ACF Flexible Content field to 'Copy' instead of 'Copy once' when using the WPML Translation Editor to ensure that the layout changes are properly carried over to the translations. For more detailed guidance on setting the correct custom fields translation preferences for ACF and WPML, please refer to our documentation:
Problem: The client wanted to display only "Français" instead of "Français (French)" for the language in the header and was also unable to see the flags for the respective languages in the header navigation. Solution: We recommended the client to revert any changes made to the language translations columns in WPML > Languages > Site Languages > Edit Languages. Then, to customize the menu language switcher, we provided the following steps: 1. Navigate to WPML > Languages > Menu language switcher. 2. Click the pencil icon to edit the language switcher. 3. Enable the flag option. 4. Disable the "Language name in current language" option. 5. Save the changes.
Please note that this solution might be irrelevant if it's outdated or not applicable 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 at our support forum.
Problem: The client is trying to migrate data from the WPGlobus plugin to WPML and is looking for a tool or a quick method to facilitate this process. Solution: We do not have a direct export and import option from WPGlobus to WPML. However, we can provide some recommendations based on our colleague's advice. Please refer to the following documentation for guidance:
Problem: If you're experiencing issues when making changes to text or other elements within Elementor Pro, especially when the 'Nested Elements' experimental feature is enabled and a form is placed as a sub-element of a tab, this is due to a known bug. Solution: We recommend either turning off the 'Nested Elements' feature in the Elementor settings or not placing the Form as a child of the Tab element. If you prefer to adjust the code, follow these steps: 1. Edit the file
Problem: The client is receiving a pop-up warning when trying to save the English version of a page using the standard WordPress editor or the Avada Builder. The warning indicates that the site is configured to use the WPML Translation Editor. Solution: If you're experiencing this issue, we recommend switching to the manual translation mode. This will allow you to have full control over the translation and enable you to use the WordPress editor or the Avada Builder without receiving the pop-up warning. For detailed steps on how to use different translation editors for different pages, please refer to our documentation:
file of your theme and add the following code at the bottom:
add_filter('wpml_editor_capability', 'my_editor');
function my_editor(){
$user = wp_get_current_user();
if (in_array('shop_manager', (array)$user->roles, true)){
return 'shop_manager';
}
}
5) Clear all types of caches. We emphasized the importance of taking a full site backup before applying this workaround.
Subsequently, we released a new version of WPML (4.6.9 series) that included a fix for this issue. We advised the client to update to the latest version after ensuring a full site backup and check if the problem persists.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
