Problem: The client's log file is full of database errors indicating 'Duplicate entry' issues, and the server was overloaded, with CPU usage at 100%. The client also mentioned that they are unable to access the Translation Management tab and encountered an error 500 when trying to filter to posts. Solution: IThis is caused by a known error:
WordPress database error Duplicate entry. You can try running this query and see if it helps
DELETE FROM `wp_postmeta`
WHERE `meta_key` = '_icl_lang_duplicate_of';
DELETE FROM `wp_icl_translations`
WHERE `language_code` = '';
Problem: If you're trying to remove unused translated strings in WPML's String Translation and observe that after selecting domains and confirming removal, the strings are not deleted and the count remains unchanged, you might suspect a plugin issue. Solution: We have conducted extensive testing and confirmed that only untranslated strings can be removed using the Remove strings by domain feature. Translated strings must be deleted from the String Translation panel. If you're facing issues with menu strings, it may be due to menu syncs. For a visual guide.
If this solution doesn't seem relevant to your situation, please open a new support ticket with us and we'll be happy to assist you further.
Problem: The client reported an issue where a visitor (not logged in) adds a translated product to the cart, but the default language product is added instead. This problem occurred after making changes to the visibility of the English language and the product translation settings in a Woodmart theme environment.
Solution: We resolved the issue by enabling the "Language filtering for AJAX operations" option in WPML > Languages. This solution worked for both logged-in and logged-out users, ensuring that the correct language product is added to the cart. We confirmed that enabling this option should not cause any performance issues, so no further troubleshooting is necessary.
Problem: If you're experiencing a 403 error indicating that your site can't communicate with
https://api.wpml.org/
, follow these steps to resolve the issue. Solution: 1. Update your WPML plugin to the latest version and all related add-ons. You can find the latest versions in the 'My Account -> Downloads' section of the WPML site. For update instructions, visit http://wpml.org/faq/install-wpml/. 2. If the error persists, contact your hosting provider to ensure they are not blocking the following domains:
Problem: The client is experiencing an issue where a widget's title on their website is appearing in English instead of the correct language, despite the setup and translation of the widget seeming correct. Solution: 1. Navigate to WPML >> String Translation and click on the Translate texts in admin screens » link at the bottom of the page. 2. Search for the widget title text in the search box and enable the translation. 3. Return to the WPML >> String Translation page and add the translation. For more detailed instructions, please refer to our documentation:
Problem: The client is unable to disconnect a translated page from the original English page after mistakenly connecting it to the wrong translation. Solution: It was a known issue that is solved in WPML v4.6.8 as mentioned here: https://wpml.org/errata/wpml-4-6-7-issue-with-disconnecting-translations/
Problem: The client is trying to add different Ninja Tables to posts in different languages using WPML. The first issue is that after adding a Ninja Table to the English post, the traditional Chinese (TCH) translation was lost. The second issue is that after adding a Ninja Table to the TCH post, the content displayed in a mix of English and TCH. Solution: We recommend not mixing translation methods (WPML editor and manual editing) as it can lead to issues like content loss. To resolve this, you should: 1. Choose one method of translation for the page (either WPML editor or manual translation). 2. If you decide to manually edit the second language page, you can disable the WPML editor for that page following this documentation: Using different translation editors for different pages. 3. Continue using the chosen method consistently to avoid further issues. 4. For code modules, manual translation is suggested to prevent code from being improperly translated, which could break the website. More information can be found here: What if I've already mixed translation methods and lost translations?.
If this solution doesn't look relevant, please open a new support ticket here.
Problem: The client is experiencing an issue where duplicating an ACF block and then editing it results in the content of the block being deleted upon saving the page. This problem does not affect all blocks, only some. Solution: We recommend the following steps to work around this issue: 1. Edit the field group that is being used in the block. 2. Edit the clone field within the field group. 3. Change the display mode to
"group"
. 4. Save the field group.
If this solution does not seem relevant to your situation, please feel free to open a new support ticket with us.
Problem:
The client had two currency widgets displayed on his top header on the frontend.
Solution:
That was not a WPML issue. The theme had 2 different sidebars. Top-right and top-left and the language switcher was added to both.
Go to "Appearance > Widgets" and remove the unwanted language switcher from one of those two locations.
Problem: The client needed to change the appearance of the WPML language selector to have a transparent background and a custom SVG icon. Solution: We provided an example of custom CSS code that the client could use to modify the language selector. Here are the steps:
/* Targeting the WPML language switcher menu item */<br />#menu-item-wpml-ls-26-en {<br /> background-color: transparent; /* Set background to transparent */<br />}<br /><br />/* Targeting the submenu toggle button */<br />#menu-item-wpml-ls-26-en .sub-menu-toggle {<br /> background-image: url('path-to-your-svg-file.svg'); /* Replace with your SVG file URL */<br /> background-size: contain; /* Adjusts the size of the SVG to fit the element */<br /> background-repeat: no-repeat; /* Prevents the SVG from repeating */<br /> border: none; /* Optional: removes any border */<br />}<br /><br />/* Hiding the default plus and minus icons */<br />#menu-item-wpml-ls-26-en .icon-plus, #menu-item-wpml-ls-26-en .icon-minus {<br /> display: none; /* Hide the default icons */<br />}<br />
Additionally, to remove the border from the language switcher, the following CSS can be used:
Problem: The client is trying to link two sites within a multisite network to share translation credits and translation memory. They are unable to get the migration code because the 'Copy Migration Code' button is disabled on both sites. Solution: If you're experiencing this issue, it's important to note that you cannot link sites together to share credits and translation memory if both sites have active subscriptions. To resolve this, you need to cancel the subscription on one of the sites. Once you do that, the option to copy the Migration code will become available. You can then copy the code from the site where you canceled the subscription and enter it into the site with the active subscription. For detailed instructions, please refer to our guide on Automatic Translation Subscription for Multiple Sites.
If this solution doesn't seem relevant to your situation, please don't hesitate to open a new support ticket with us here.
Problem: The client is looking for a feature in Woocommerce Analytics to see product sales data for all currencies combined, rather than just per currency. Solution: We have included the client's request in our list of featured requests, which our developers will consider for future plugin updates. We do not have an estimated time of arrival (ETA) for this feature, as it depends on various factors such as the number of votes and client demand. The request is internal and not publicly accessible, so the client cannot follow it directly. However, we recommend checking the changelog file in future plugin releases and staying updated with our blog posts for any announcements regarding this feature.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
