Problem: If you're experiencing a critical error on your translated site pages, it might be due to a PHP Fatal error indicating a type mismatch. Specifically, the error occurs because the code expects an array but receives a string instead. This issue often arises with ACF custom fields that are not correctly handled in translations. Solution: We recommend checking the ACF custom fields used in your template. Ensure that fields such as 'section_details', 'section_info', and 'section_map' are properly registered for translation with WPML and are returning arrays as expected. Here's what you might see in your code:
$salon_details = get_field('section_details');
$salon_info = get_field('section_info');
$salon_map = get_field('section_map');
$map_link = $salon_details['map_link'];
$address = $salon_info['address'];
$coords = $salon_map['lat_lang'];
Please confirm where these fields are defined: Are they attached to a specific page, a custom post type, or an ACF Options Page? If this solution does not resolve your issue or seems irrelevant due to being 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 problems persist, please open a new support ticket.
Problem: If you're experiencing a looping issue even after deactivating all plugins except WPML, and it seems to loop faster, the problem might be related to your .htaccess file. Solution: We recommend generating the default WordPress .htaccess file and replacing the current one with it. This change might resolve the looping issue. If the default .htaccess file resolves the issue, you should then update or modify the needed mod_headers rules accordingly.
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 WPML support forum for further assistance.
Problem: The client renewed their WPML license and received a total of 92,000 credits. Despite assigning these credits to their website through the WPML.org account, only 352 credits are visible and usable for translations in the WordPress backend under the WPML → Translation Dashboard → Translation Tools tab.
Solution: 1. Verify the centralized and per-site balance of credits in the WPML.org account and cross-check against the registered site’s URL. 2. Check for discrepancies in the credit log or misapplied assignments in the backend. 3. Confirm that the site registration matches between WPML.org and the site backend, ensuring there are no duplicate registrations or domain mismatches. 4. Do not repeat standard credit assignment instructions or dashboard checking steps as these have already been tried. 5. If the issue persists, escalate internally for backend investigation due to a possible synchronization or billing anomaly.
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 problem continues, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing the issue where translations are not working and encountering the error message 'Unable to retrieve job details' when trying to translate a numeric value in the Advanced Translation Editor (ATE), it's because WPML by default excludes numeric values in the job data sent to ATE. Solution: We recommend adding the following custom code to the file
functions.php
in your theme or child theme folder. This code allows the translation of numeric values. After adding the code, re-send the string to translation:
Please ensure to backup your database and website before proceeding. For more details, you can refer to our forum discussion on translating numbers.
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 at WPML support forum.
Problem: The client reported an issue where the French mobile menu was displaying the incorrect label 'Certificats Cadeaux Vivanti' instead of 'Certificats Cadeaux'. Solution: We recommended the client to check and correct the navigation menu settings for the French language. Here are the steps we suggested: 1. Access the header templates at your WordPress admin area. 2. Edit the header template named Global Header Vivanti Final. 3. Ensure the primary-language template is updated and then retranslate it. After following these steps, the navigation menu should display the correct translated version.
If this solution does not resolve your issue or 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 the problem persists, please open a new support ticket.
Problem: The client experienced a site crash when updating the WPML String Translation to version 3.4.1 on PHP version 8.3.29. The error indicated a missing class 'WPML\Infrastructure\WordPress\Port\Persistence\DatabaseWrite'. Solution: We recommended removing the current WPML installation and reinstalling it. A fresh installation of WPML resolved the issue. It is crucial to make a full site backup of files and database before proceeding with these steps. For further details on privacy and security when providing debug information for support, please visit: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/
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 issues persist, please open a new support ticket at WPML support forum.
Problem: The client was experiencing an issue where their site did not meet WPML's minimum requirements because the WordPress REST API was not responding correctly. This was initially suspected to be due to WPML's requests to the REST API being blocked or not properly authenticated.
Solution: 1. The client was advised to modify the
WordPressRestApiStatus.php
file within the WPML plugin directory to include cookie authentication in addition to the existing basic authentication. 2. After implementing the suggested changes, the issue persisted, leading to further investigation. 3. It was eventually identified as a false positive caused by a minor bug in WPML's code. A workaround was provided by the second-tier support, and a permanent fix is expected in the next WPML version.
If this solution does not resolve your issue or seems irrelevant due to being 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are experiencing an issue where media grid images disappear after translating them using the Classic Translation Editor. Solution: 1. We suspect this might be a compatibility issue with the specific element. To test this, please follow these steps: - Log in to a fresh WP site with WPML installed by using the provided auto login URL. - Install WPBakery Page Builder and configure it as on your site. - Create a test page with a Media grid element in the default language and attempt to translate it.
2. If the issue persists, try this workaround: - Navigate to WPML > Settings > Custom Field Translation. - Click on Show System Fields. - Search for
_vc_post_settings
. - Change the setting from "Do not translate" to "Copy". - Save the changes. - Edit the default language page, make a small change in the page title to reload the translation, then edit the secondary language page in WPML Translation Editor and press the Save & Close button.
Please check if the images display correctly in the secondary language after following these steps. If the issue remains unresolved 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're unable to activate the WPML plugin and encounter a fatal error indicating an issue with a non-countable type in the 'functions.php' file, this might be due to a specific database entry causing the problem. Solution: We recommend checking your database for the option named
auto-translation-job-creation-error
in the 'wp_options' table and deleting it. After removing this entry, try reactivating the WPML plugin. This solution is a temporary fix until the issue is permanently resolved in WPML version 4.9.
Please note that this solution might be outdated or not applicable to your specific case. If the problem persists, 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 needed, do not hesitate to open a new support ticket for further assistance.
Problem: The client is experiencing 404 errors on the order confirmation page and the endpoint 'order-paid' in translations. The issue temporarily resolves by saving the permalinks but reoccurs the next day. Deactivating the WPML String Translation plugin stops the error. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Navigate to WPML → String Translation and ensure that the endpoints are set to their original English values (not translated). 2. Save the permalinks again to resolve the current 404 errors. 3. Return to WPML → String Translation and translate the endpoints as needed. Important: After translating the endpoints, please do not save the permalinks again. We are aware of this issue and are actively working on a permanent solution.
We already have a development ticket for this problem and are actively working on a permanent solution in future releases.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket here.
Problem: The client's site does not display the translated footer despite attempts including a full WPML reset, making minor changes in the footer template, and re-adding the footer to the translation queue. The site is built using Full Site Editing (FSE). Solution: We recommend applying a workaround suggested by our second-tier support. for more details: WPML forum discussion on FSE template issues. Please test this solution and let us know if it resolves the issue.
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 the problem persists, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: The client is planning to create an introductory page where site visitors can choose either English or German, and then be redirected to the respective language version of the site. They are also concerned about whether this setup will affect the SEO of their multilingual website. Solution: We recommend using the built-in features of WPML for language redirection, so there is no need to purchase an additional plugin. You can set up a language directory by following the instructions here: Setting up a language directory. Additionally, we confirm that using WPML for this purpose will not negatively impact your website's SEO.
Please note that this solution might be irrelevant if it's 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 you still encounter issues, please open a new support ticket at WPML support forum.
Problem: You are experiencing an issue where your WPML account and credits are not properly linked to your site, showing conflicting information between WordPress and the WPML account dashboard. Although automatic translation is enabled and credits appear available within WordPress, the WPML dashboard indicates no account or website is linked to the credits being used. Additionally, WPML does not recognize the site as connected despite the plugin registration appearing active. Solution: 1. Delete the existing site key on WPML.org and re-register the plugin using a newly generated key. This ensures that your credits will not be lost during re-registration. 2. Check for WPML site movement/copy notices and respond as appropriate. 3. Verify that the WordPress Address (URL) and Site Address (URL) fields match the live domain. 4. Double-check if the correct, new site key is entered under Plugins → Add New Plugin → Commercial tab. 5. Re-log into WPML.org and refresh the account settings. 6. If WPML detects the translation as English to English, resolve this by enabling "Fallback Untranslated Content to Default Language" or duplicate the page into the secondary English language and adjust the content as needed. More details can be found in the documentation: here and 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with car listings not appearing correctly on translated pages using the Motors theme. Specifically, the 'fuel' field does not copy or persist across languages, and the 'Types' field in the secondary language does not maintain multiple selections. Solution: We have confirmed the issue with the listings. While the fields are saved correctly in the database and work as expected on the front end, they do not appear or change in the backend for translated listings. To resolve this, set the custom fields as translatable and configure them per language. This adjustment allows each language version to maintain its specific selections and ensures that the fields behave correctly across different languages.
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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: You are setting up a new site to merge multiple WordPress instances for managing content in different languages. After migrating users from the old sites to the new backend, you've noticed an issue where some users can click on the plus icon in the "All Posts" section for all languages, while others see grayed-out plus icons. There are no translation managers in WPML settings, and only one translator, which is your account. Solution: We recommend using the Toolset Access plugin to control what different users can see and do on the translation dashboard. This plugin allows you to manage translation permissions effectively. For detailed guidance on how to use this plugin, please visit the following documentation: How to Use Access Plugin to Create Editors for Specific Language.
If this solution does not resolve your issue, or if it 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. Additionally, you can open a new support ticket for further assistance 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
