Problem: The client deleted a field from a field group associated with a Custom Post Type (CPT) using a custom SQL query to remove all instances of
field_name
and
_field_name
due to a large number of posts.
Solution: We recommend updating the original post and then its translation. This action will remove the content from the translation editor and from the
icl_translation_status
table. To remove it from the
icl_translate
table, the client will need to write a custom SQL query. Additionally, we found an errata that might be related to the size of the
icl_translate
table. We suggest looking at the workaround provided in the errata to help reduce the size of the table:
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 with us.
Problem: The client is experiencing an unwanted 301 redirect on their website, which includes the "x-redirect-by" header with a value of "WPML". They have already cleared the WPML cache, but the issue persists. Solution: If you're experiencing a similar redirect issue, we recommend trying the following steps: Use the WPML hook to deactivate the WPML functionality that is causing the redirect. You can find the documentation for this hook here: https://wpml.org/wpml-hook/wpml_is_redirected/
After applying the hook, please check if the redirect issue has been resolved.
If this solution doesn't look relevant to your situation, please open a new support ticket with us for further assistance. You can do so by visiting the WPML support forum.
Problem: The client is trying to translate a page named (Project) into French using WPML, but encounters an issue where the advanced translation editor fails to detect and process certain text within Divi text modules. Solution: We recommend reviewing each Divi text module to ensure there are no instances of "strange random" text hidden within them. This text may be causing the translation editor to malfunction. If after checking the modules the problem persists, please open a new support ticket with us so we can assist you further.
Problem: The client is editing a page in two languages simultaneously using Elementor and wants to insert a link to a page that has versions in both languages. However, the link to the 'About us' page only appears in the language that was last selected in the WordPress Dashboard. Solution: We recommend translating URLs using our translation editor. Here is a step-by-step guide: 1. Choose the language you want to edit in the WordPress Dashboard before opening the Elementor editor. 2. Follow the workflow provided in our documentation to translate URLs using the Advanced Translation Editor: https://wpml.org/faq/how-to-translate-urls-shortcodes-and-html-attributes-using-the-advanced-translation-editor/
Problem: If you're trying to edit a translated page and encounter the error 'Deprecated: mb_strlen(): Passing null to parameter #1 ($string) of type string is deprecated', this is likely due to incompatibilities with PHP 8.2. Solution: We recommend you try the following steps: 1. Go to the affected page and make a minor modification to the content in the original language. 2. Attempt to translate the page again to see if the issue is resolved.
Please note that WordPress has known incompatibilities with PHP 8.2, which can cause warnings like this to appear. We have added your ticket to our internal tracking system and will address the issue in a future update. Keep an eye on our changelog for updates: WPML Changelog.
If this solution doesn't look relevant to your situation, please open a new support ticket in our forum: WPML Support Forum.
Problem: The client is inquiring about whether WPML cookies are essential or functional and whether they should add all WPML cookies to their cookie manager or just the ones that appear in their console. They also asked for the duration of specific cookies:
_icl_visitor_lang_js
and
wpml_browser_redirect_test
, which they can't find in their console. Solution: If you're experiencing confusion regarding WPML cookies, we recommend you to include only the essential cookies that WPML uses to function properly. WPML stores only essential cookies, and there are no optional cookies that you can activate or deactivate. All cookies listed in our documentation are important for the proper functioning of WPML.
Regarding the specific cookies
_icl_visitor_lang_js
and
wpml_browser_redirect_test
, if you don't see them in your console, it's likely because you do not have the "Browser language redirect" function active on your site. If you decide to use this feature in the future, you can find more information about setting it up here:
Problem: The client is experiencing accessibility issues with the language switcher on their website, as indicated by the PageSpeed Insights test. Solution: We acknowledge an existing internal development ticket regarding this issue, but we cannot provide a specific timeline for its resolution. We suggest adding an
aria-label
attribute with a descriptive name to the language switcher link to improve accessibility, like so:
<a href="https://www.spotix.app/he/spots/..." class="wpml-ls-link" aria-label="Descriptive Name of the Link"></a>
Additionally, we recommend checking the following documentation for a potential workaround regarding missing alt tags for flag images in the language switcher: Missing alt tag for flag image in a language switcher
Problem: The client has a bilingual website (Arabic and English) and is facing an issue where customer information appears in Arabic on the order page and on the invoice when a purchase is made in English using WooCommerce PDF Invoices, Packing Slips, and Credit Notes (Pro). Solution: 1. We recommend following the steps in our guide to change the language in the backend of the site: Setting the WordPress Administration Language. After doing so, you can instruct your client on how to change the backend language in their account. 2. We also suggest increasing the WordPress memory limit to at least 128MB. You can do this by adding the following code to your
Problem: The client is unable to create a redirect from a URL containing an accented character to a URL without the accent. Solution: We recommend encoding the special character in the URL and using a relative path for the old URL. The correct redirect rule in the .htaccess file should look like this:
Problem: The client updated the English version of a footer inside a reusable block by adding a new link called "Impressum" but it did not propagate to other languages. Additionally, the client removed a location from a page which also did not update in other languages. Lastly, the client needed to add an extra link only in the German version of a page.
Solution:
1. Navigate to WPML > Translation Management and search for the reusable block by its name.
2. Follow the instructions in our guide to translate it: Translating pages, posts, and custom post types.
3. After translating, if the link "Impressum" still isn't translated, go to WPML > Settings > Translate Link Targets and wait for the process to finish.
If the link was added internally and is not appearing in the translation editor, you can search for it there. If WPML detects it as an internal link, it should translate automatically once you update the translation via WPML > Translation Management.
For adding a link visible only in the German language, you need to localize the page by adding an empty link at the end of the paragraph:
<a href="URL of the page you want to add in German"> </a>
Then, use the translation editor to add the URL, making the link visible only in German.
Problem:
If you're experiencing issues with the language switcher not rendering content on a Bricks Builder Landing page, while other templates and pages translate fine, and you've noticed that the header and footer are translated correctly, this summary is for you. The client found that the language switcher worked on individual templates but not on the landing page, despite setting conditions for the templates to display based on the selected language.
Solution:
We recommend the following steps:
1. Edit the home page using Bricks and add a header element.
2. Update the page.
3. Translate the page using your translation management system.
4. Check if the translated pages show the translated header and template.
If you've followed these steps and the content is still not rendering correctly, or if this solution doesn't seem relevant to your issue, please open a new support ticket with us, and we'll be happy to help.
Problem: If you're experiencing a 500 internal error on your translated page after adding a product to the cart, and this occurs when certain plugins (Payment Plugins for Stripe WooCommerce, Sequential Order Numbers for WooCommerce, and Variation Swatches for WooCommerce) are enabled, it might be due to a compatibility issue with WPML.
Solution: We recommend reaching out to the authors of the plugins that are causing the issue and request a compatibility update with WPML. We provide extensive documentation to help developers make their plugins compatible. You can find this information at the following links:
Problem: The client is trying to set up a multilingual WooCommerce store and is experiencing random 500 errors on sites in the translated languages. The client tried regenerating .htaccess, increasing the memory limit, and checking WP logs without success. Installing the 'Fix .htaccess WPML language' plugin seemed to fix the issue, but the client is looking for a proper solution rather than using additional plugins. Solution: We recommend checking our errata page for information on issues with .htaccess being rewritten with language folders, which is not directly caused by WPML but could be due to a third-party plugin. Identifying the plugin causing the rewrite will allow us to provide further assistance. If this solution does not seem relevant, please open a new support ticket in our forum for personalized help.
Problem: The client wants to translate the string "Sort By" in the dropdown on their WooCommerce site, but it does not show up in the string translation. Solution: 1. We recommend scanning the "Woocommerce" plugin for strings that are not appearing on the string translation page. You can find the instructions on how to do this here: Scanning a theme or plugin for strings. 2. After scanning, recheck the String Translation to see if the "Sort By" string appears. 3. If the string is available, you can proceed to translate it as indicated in the provided screenshot.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
