Problem: You are working on a site under development and need to understand the implications of changing the WPML license key if the client changes providers in the future. You are concerned about whether they will need to unregister their WPML and get a new license key, and if they will lose any translations in the process. Solution: If your client has a WPML.org account, they can manage their sitekey directly from their account. Here are the steps we recommend: 1. Create a new sitekey on their WPML.org account. 2. Unregister the site using the old sitekey. 3. Re-register the site with the new sitekey. Changing the sitekey will not affect the translations on the site.
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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: You are trying to register for Pay as you go on your site and receive a message about an outstanding debt, but there is no link provided to view or pay the invoice. Solution: We have located the unpaid invoice for you. You can view and settle your outstanding invoice by following this link: View Invoice.
If this solution does not resolve your issue or seems irrelevant, we 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 is using Astra Theme and Spectra Blocks and is unable to translate a button on their website. Solution: We recommend adding the following code to WPML > Settings > Custom XML Configuration:
<wpml-config>
<gutenberg-blocks>
<gutenberg-block type="uagb/call-to-action" translate="1">
<xpath>//*[self::h1 or self::h2 or self::h3 or self::h4 or self::h5 or self::h6]</xpath>
<xpath>//p[@class="uagb-cta__desc"]</xpath>
<xpath>//*[@class="uagb-cta__buttons"]</xpath>
<xpath>//a[@class="uagb-cta__button-link-wrapper"]</xpath>
</gutenberg-block>
</gutenberg-blocks>
</wpml-config>
After adding the code, make a small modification and save, then update the translation.
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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are using MotoPress to build your site and have translated the accommodation type. However, the menu switcher does not display its drop-down menu on translated pages, showing only the default language flag and language. Solution: If you're experiencing this issue, we recommend ensuring that the page, post, or taxonomy is fully translated and published (not in Draft mode). This is often the cause when the second language does not appear in the language switcher. After verifying this, if the problem persists, please provide us with the page URL where the issue is visible. Additionally, we may need more information about your site. You can share your debug information by following the instructions in this article: https://wpml.org/faq/provide-debug-information-faster-support/
If this solution does not resolve your issue or seems irrelevant due to updates or differences in 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 needed, please do not hesitate to open a new support ticket for further assistance at our support forum.
Problem: The client is using ACF Pro with a Gallery field set to 'Hide from library', which works correctly in the primary language by hiding images from the WP Media Library. However, in the secondary language (Swedish), the images are still visible in the media library. Solution: We first clarified that the 'Hide from library' feature might be misunderstood as it is intended to limit file selection to those uploaded to the post, not hide them from the Media Library entirely. We also identified that the 'Frontend Admin' plugin, which is not compatible with WPML, might be causing the issue. We recommended contacting the plugin author to request compatibility with WPML through our Go Global program (https://wpml.org/documentation/support/go-global-program/).
If this solution does not resolve your issue or seems irrelevant, we highly recommend checking related known issues (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.
Problem: After auto-translating a product, it remains unpublished and appears as a draft in the 'yoast_indexable' table. Solution: If you're experiencing this issue, we recommend that you publish the translated products manually. You can do this by navigating to Products, switching to the desired language using the language switcher at the top bar, and then selecting the products to publish in bulk. This action should update the post status in the 'yoast_indexable' table to reflect the published state.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: The client is experiencing an issue where the German flag on their WordPress site appears smaller than other flags despite setting all flags to a uniform size of 30x30 in WPML > Languages. The issue persists even after adding custom code to prevent resizing. The problem seems to be related to the Blocksy theme, as changing to a different theme resulted in consistent flag sizes. Solution: We recommend checking the original size of the uploaded flag images, as the German flag might be smaller in its original dimensions. If the flags are not uniform in size, consider uploading new images that match the desired dimensions. Additionally, since the issue is theme-specific, contacting the theme's support for insights or considering a theme change might be necessary if consistent flag sizes are crucial. For now, setting all flags to 'auto' ensures they appear consistent across different pages, albeit smaller.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening a new support ticket here.
Problem: The client has issues with pages and translations being stored in the default language (DE) instead of their respective languages (EN) after importing content via XML. The English translations are visible in the German backend but are not paired with their German counterparts. Solution: We recommend setting the language for each page or post manually in the Language section of the editing screen. After setting the language, you can link the translations. Detailed instructions can be found in our guide on how to link already translated pages: https://wpml.org/faq/how-to-link-already-translated-pages/
If this solution does not apply to your case, or if it seems outdated, please check our related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if further assistance is needed. You can do so at our support forum: https://wpml.org/forums/forum/english-support/
Problem: You are trying to change the default language in WPML, but after doing so, you cannot switch to other languages. Solution: First, ensure that you have saved the WordPress Permalink settings after changing the default language. This step is crucial as it updates the URL structure to accommodate the new language settings. Next, check for any errors under WPML > Languages > Site URL format in your WPML settings. If there are issues here, they might be preventing the language switch. Further, please verify if there are any redirects in place that are not coming from WPML.
If these steps do not resolve the issue, it might be due to specific configurations or conflicts that are not covered here. We recommend visiting our known issues page to see if there are any similar cases. Also, ensure that you are using the latest versions of all themes and plugins.
Problem: You are trying to make admin texts visible on the front-end of your site but they are not appearing even after scanning and translating strings using WPML, and clearing the cache. Solution: First, ensure that your WP Memory limit is sufficient. We recommend setting the WP Memory limit to 256M as WPML requires a minimum of 128M to function properly under minimal conditions. To do this, add the following code to your
wp-config.php
file:
define('WP_MEMORY_LIMIT', '256M');
Place it just before:
/* That's all, stop editing! Happy blogging. */
After updating the memory limit, verify the current settings under WPML > Support > WordPress. If your hosting provider limits these settings, you might need to contact them to request an increase. Once you have adjusted the memory limit, try completing the translation process again. If the issue persists, further details about the string's origin and its registration in PHP might be necessary.
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. If needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is unable to translate the text 'chiama o whatsapp' displayed by the Chaty plugin using WPML. Solution: First, navigate to WPML > String Translation and click on the link 'Translate texts in admin screens' at the bottom. Search for 'WhatApp' to find the string
[cht_social_whatsapp]title
. Add this string to String Translation and attempt to translate it. However, note that the translation might not appear on the frontend as the plugin uses a different logic for displaying strings on hover.
If you are trying to translate a Call to Action Text for the widget, search for the string
cht_cta
. Adding and translating this string should work as expected. Remember, these strings will be registered in the site's default language. If the source language differs from the literal string text, you need to change the source language for the strings inside String Translation. You can learn how to do this here: How to change the source language of strings.
If these steps do not resolve your issue, it may be due to the plugin not supporting frontend translation for certain strings. We recommend contacting the plugin author for further assistance on this matter.
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.
Problem: You are experiencing an issue where translating your header results in a different header builder being applied, adding an additional header to the original one. Solution: We found that the 'hide page's title' toggle was not checked on the translated page. We recommend checking this toggle for your home page. To do this, you can edit the translated page by navigating to Pages -> All Pages in your WordPress dashboard, then switch the language from the top admin bar and make the necessary adjustments.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend opening a new support ticket. Additionally, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, you can also visit our support forum at https://wpml.org/forums/.
Problem: The client wants to display language switch links as 'DE | EN' in the navigation bar, but currently, they appear as separate links 'English' 'German'. The client is looking for a way to add the language switch as an HTML widget in the navigation bar and to display the links together without too much space in between. Solution: To display the language names in the desired format ('DE' instead of 'German', etc.), you should go to WPML > Languages > Edit Languages and rename the languages as needed, then save the changes. To add a vertical line between the language switch links, we recommend checking out the following public tickets for guidance on adding a vertical line to the language switcher separator: here.
If this solution does not apply to your case, or if it 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 you still need assistance, please open a new support ticket here.
Problem: You need to allow your client to communicate with translators without giving them access to your agency WPML account. Solution: We recommend transferring the site to the client from your WPML.org account. This will provide the client with a one-site account, which enables them to manage translations directly. For detailed instructions on how to proceed, please read our guide on transferring account renewals to your clients.
If this solution does not apply to your situation, or if it 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 you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are receiving deprecation notices about the creation of dynamic property in the Whip_RequirementsChecker class due to a feature in PHP 8.2. This issue appears in the logs or query monitor plugin at wp-content/plugins/sitepress-multilingual-cms/vendor/yoast/whip/src/Whip_RequirementsChecker.php:37. Solution: We are aware of this issue and our developers are working on updating the yoast/whip package to v2 in one of the future releases of WPML. This update will resolve the deprecation notices you are encountering.
If this solution becomes irrelevant due to updates or if it does not apply to your case, 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. For further assistance, please visit our support forum 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
