Problem: After migrating a regional language site from /mx/ to /es/ and deactivating the old MX language, a number of ES posts went missing. Initially, there were 43 blog posts, but after the cleanup, only 19 remained. Solution: We recommend checking the following settings in WPML: 1. Navigate to WPML->Settings->Posts and pages synchronization and ensure that the options 'When deleting a post, delete translations as well' and 'When deleting a taxonomy (category, tag or custom), delete translations as well' are unchecked. 2. Go to WPML->Support->Troubleshooting and click the following buttons: + Clear Cache in WPML + Set Language information + Fix element types collation + Remove ghost entries from the translation tables + Assign translation status to duplicated content These steps should help recover the missing posts.
If these steps do not resolve your issue or if the solution 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 the problem persists, please open a new support ticket at WPML support forum.
Problem: If you're trying to renew your WPML subscription and encounter the error message "The country is not supported" when using a credit card from Türkiye, this issue might be due to restrictions or settings in the payment system. Solution: We recommend checking with the payment system you are using to ensure that there are no restrictions for payments from your country. If the issue persists, please contact us directly so we can escalate the matter to our sales team for further assistance. They will investigate the issue and provide a resolution.
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 problem continues, do not hesitate to open a new support ticket at WPML support forum.
Problem: The client was unable to find the 'Edit' button for translating a contact form on their website and was unsure if the issue was due to having the wrong language selected or another reason. Solution: We confirmed that the original contact form was created in German, even though the site's default language was set to English. This discrepancy was why the 'Edit' button was not visible when the site was viewed in English. To resolve this, the client needs to ensure that the German language is selected when attempting to edit the German-created form. This can be done via the WPML Translation Dashboard or directly from the contact form's settings page in German.
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: If you're experiencing a fatal error with WPML when another plugin tries to read the configuration of your shop, and you're using PHP 8.4, this might be due to deprecated warnings triggered by the new checks introduced in PHP 8.4. Solution: We recommend switching to a PHP version prior to 8.4 as a temporary workaround while we address these compatibility issues. This change should help avoid the fatal error you're encountering.
Please note that this solution might be outdated or not applicable to your specific case. If this does not resolve your issue, we highly recommend checking related 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: When translating pages into Spanish, they do not display correctly. Solution: We found that the issue was caused by an incorrect closing of a div tag in the HTML widget containing the form. We corrected the div tag from
<div />
to
<div></div>
, which resolved the display issue. Please verify by checking the Spanish home page.
If this solution does not apply to your case, or if it seems outdated, 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 https://wpml.org/forums/forum/english-support/.
Problem: The client experiences issues with previously translated posts whenever a new translation is saved. This includes potential content loss, formatting issues, or language mix-ups. Solution: 1. Disable automatic translation to prevent background processes from interfering: * Navigate to WPML → Translation Dashboard. 2. Cancel any in-progress automatic translation jobs: * Go to WPML → Support → Troubleshooting. 3. Test translating a new post after performing the above steps. 4. If issues persist, increase the WordPress Memory Limit as it might be below the minimum requirement for WPML. 5. Ensure all WPML plugins are updated to the latest version by checking in WP > Plugins > Add new > Commercial Tab.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your case, we recommend opening a new support ticket. Additionally, please check related known issues at https://wpml.org/known-issues/ and verify you have installed the latest versions of themes and plugins. For further assistance, you can also contact our support directly at WPML support forum.
Problem: 1. The 'Blog' menu item shows as 'uncategorized'. 2. The 'Need help' button on the menu is not translated, and the popup form does not appear on translated sites. 3. All sub-pages under 'theme trip' are missing. 4. The bottom of the home page is not translated, and the contact us form is missing. Solution: 1. For the 'Need help' button, translate it using WPML-> Strings Translation-> Admin Screen Texts. For detailed steps, refer to this guide. 2. Ensure that the menus and the pages used in the menus are translated to see the correct items in different languages. For more information, visit this guide. 3. To translate the footer form, navigate to WPML-> Translations Dashboard, select the form, and send it for translation. More details can be found in this guide.
Please note that the solution provided might be 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, do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is experiencing warnings from the WPML REST API endpoint despite it returning valid data. The issue is suspected to be due to a low WP Memory Limit. Solution: 1. Increase the WordPress memory limit by editing the
wp-config.php
file. Add the following line above the 'That's all, stop editing! Happy publishing.' line:
define('WP_MEMORY_LIMIT', '256M');
If the memory limit is already defined, update it to at least 256M, preferably 512M for optimal performance with WPML and other plugins. 2. If the issue persists, check the
php.ini
file for the
memory_limit
setting, or contact the hosting provider to ensure it's set to at least 256M. 3. After making these changes, clear all caches and re-test the REST API endpoint. 4. If the problem continues, deactivate any security plugins like WordFence and consult with the hosting provider about any firewall or security settings that might be affecting the REST API.
If these steps do not resolve the issue or if the solution 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. For further assistance, please open a new support ticket at WPML support forum.
Problem: You are experiencing CSS issues with your BeTheme site, specifically with the styling of all language menus, including the main menu, sticky menu, and two mobile phone menus. The flags in the language switcher are not aligned vertically as desired. Solution: 1. Clear All Caches: If you are using any caching plugins or your host provides server-side caching, please clear all caches to ensure that any changes are immediately reflected on your site. 2. Inspect and Adjust CSS: Use your browser's developer tools to inspect the problematic menu CSS. Look for any conflicting or overriding CSS rules and adjust them accordingly. You might need to temporarily disable custom CSS globally and in the WPML Language Switcher to isolate the issue. 3. Manual CSS Adjustments: Since the issue is specific to BeTheme, we recommend manually reviewing and adjusting the CSS related to the language switcher elements and menu wrappers within the BeTheme customizer or a child theme.
If these steps do not resolve your issue or if the solution 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client created a global container in Avada with three blocks, each having a background image. However, when viewing the container in Dutch or German, the images disappeared despite being translated via media translation. Solution: We discovered that syncing the options to all languages for Avada resolved the issue. For further guidance on setting theme options for different languages in Avada, please refer to our documentation: https://wpml.org/documentation/theme-compatibility/using-wpml-with-the-avada-theme/how-to-set-theme-options-for-languages-in-avada/
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client experiences 404 errors across the site, mainly with portfolio posts, after copying and translating a page. The issue persists even after setting up redirects and involves unexpected changes in URLs when setting up translations in different languages.
Solution: 1. Ensure the PHP version is fully supported by WordPress, preferably versions 8.1 or 8.2. 2. In an incognito window, check if the issue still occurs. If it does, follow these steps: - Navigate to WPML->Support->Troubleshooting. - Clear the WPML Cache. - Go to WP Engine and clear the website cache. 3. Check if there are any active 301 redirects that might be affecting the URLs. 4. In WPML settings, under 'Translated documents options' -> 'Page URL', ensure the correct settings are applied based on whether the translation language uses encoded URLs. If necessary, adjust the language settings to 'Encoded' or set it to 'Translate' for more control over the URL slugs in the translation editor.
If these steps do not resolve the issue or if the solution 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. If problems persist, please open a new support ticket.
Problem: The client is experiencing an issue where the button text on a Loop template page displays in Spanish, despite the page not being translated. The button text 'Read More' does not reflect the default language when displayed on the front end. Solution: We recommend checking the translation settings for your post types and language switcher. First, navigate to WPML->Settings->Post Types Translations and ensure that the pages are set to Translatable - only show translated items. This setting helps in displaying content only in the translated language without falling back to the default language if a translation is not available. Next, go to WPML->Languages->Language Switchers and check the option for How to handle languages without translation. Make sure that "Skip languages" is enabled. This setting prevents the display of languages that do not have translations.
If these adjustments do not resolve the issue, or if the solution seems 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 problem persists, please open a new support ticket with us for further assistance.
Problem: The client inquired about uploading full translated texts in bulk to their multilingual site using WPML, rather than translating content part by part. They also sought to preserve the original English layout when adding translations and inquired about discounts for high-volume auto-translation credits. Solution: 1. To upload full translated content directly, open any page in the default language in Edit mode, enable the WordPress Editor from the Languages metabox, and paste the complete translated text in the translated page. For more details, see this documentation. 2. To preserve the original layout, duplicate the default language page into the secondary language and replace the content with the translated text. Alternatively, use the XLIFF export/import method for translating content externally and importing it back while keeping the original layout. More information can be found here. 3. For auto-translation, consider the pay-as-you-go subscription for more cost-effective options compared to purchasing large translation credit packages. Check options and pricing here.
If this solution does not apply to your case, or if it seems outdated, 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.
Problem: The client is unable to replace a logo image with its English version when the site is translated using Elementor and Woodmart child template. Solution: We recommended checking the translated image ID in the WPML String Translation page. Here are the steps we followed: 1. Navigate to the WPML String Translation page. 2. Search for the original image ID. 3. Replace it with the English version image ID. 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: After migrating and redesigning a site using WPML, the English language selector is missing on several pages, and the English main menu is not displaying correctly, showing only the site logo and the language selector. Solution: 1. Confirm that the site is registered with the correct WPML site key for the live domain in Plugins → Add New Plugin → Commercial tab. 2. Check if the translated pages are in the Trash and either permanently delete them or restore them, as pages not in a published state will not display the language switcher. 3. Ensure proper synchronization of the navigation menu by following the steps in this documentation: https://wpml.org/documentation/getting-started-guide/translating-menus/ 4. If these steps do not resolve the issue, we recommend opening a new support ticket. Additionally, it is advisable to 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, please contact us through the 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
