Problem: The client is experiencing an issue where despite having 15000 credits assigned to their website, they receive a message stating no credits are available. Solution: We advised the client to check the Automatic Translation Usage Report by navigating to WPML > Translation Management > Tools > Payment and settings > Automatic Translation Usage Reports. Upon review, it was discovered that a total of 20,000 credits had been assigned and completely used, which explains why no credits were available for further translations. For more details on how to access and understand your Automatic Translation Usage Reports, please visit WPML documentation.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client wants to display the permalink of the Japanese page in English instead of Japanese characters. Currently, the URL shows Japanese characters, which they want to change to English. Solution: First, ensure that the WPML settings are correctly configured to copy the permalink from the original language if the translation language uses encoded URLs. You can check and adjust these settings under WPML->Settings->Page URL. Additionally, set the encoding URL option for Japanese to 'YES' under WPML->Language->Edit Languages. If there are mixed parts in English and Japanese, you will need to resend the content for translation to ensure all parts are correctly updated. We also 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 solution does not resolve your issue or seems outdated, please open a new support ticket at WPML support forum.
Problem: The client needs to manually translate individual strings on their site but is unable to do so because all the strings are stuck on 'Waiting for translator'. The client has tried to solve this issue by following a forum topic but couldn't cancel the 'waiting for translator' status as the strings were not selected in 'Jobs'. Solution: We recommended that the client should ensure that all required languages are assigned to their user profile. This can be done by visiting the WPML Translators Management page and clicking on the pencil icon to add other languages to the user profile. Here is the link to manage translators: https://wpml.org/documentation/support/wpml-admin-capabilities/#add-translator After adding the languages, the client should navigate to the Translation Management Jobs page, filter by 'strings', and check if they can now manage the translation jobs.
If this solution does not resolve the 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 the problem persists, please open a new support ticket at https://wpml.org/forums/forum/english-support/ for further assistance.
Problem: You are trying to translate Gutenberg templates (both archive and single) for your site and encountering a JSON error when attempting to create translations directly in the backend. Solution: We recommend not creating a different template for each language. Instead, use Translation Management to translate the template from your site's default language. Please follow this guide for detailed instructions: Translating sites that use full site editing.
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. Should the problem persist, please do not hesitate to open a new support ticket for further assistance at WPML support forum.
Problem: You are working on a site under development and encountering issues with WPML. Specifically, you face an error when trying to translate link targets ('Error! Reload the page and try again'), and custom post URLs are not being translated. Solution: For the issue with translating link targets, we recommend enabling WordPress Debug by following this guide. After enabling, use the Link Target feature again and check the WordPress Debug log for any errors. Share these errors with us for further assistance.
Regarding the custom post URLs not being translated, ensure that the CPT slug has been registered correctly. For guidance on adding multilingual support for CPT slugs, refer to this documentation. If the problem persists, please provide the link to the page/post where the slug is not showing correctly.
Additionally, a '504' server error was identified, which suggests issues with the server or the Content Delivery Network (CDN). Contact your server support for this matter. As a temporary measure, deactivating all plugins except for WPML might help, as it did complete the process successfully in our test.
If these steps do not resolve your issues 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, do not hesitate to open a new support ticket for further assistance.
Problem: The footer of your website is no longer being translated into English and French, and the associated translation strings are not found. Solution: If you find that the footer of your website is no longer being translated, we recommend checking the translation of the footer block. We have updated the translation for the page with the ID in the WPML String Translation Tool. You can check this by clicking here.
If this solution is outdated or does not apply to your problem, we recommend opening a new support ticket. We also recommend checking the page with known issues (https://wpml.org/known-issues/), verifying the version of the permanent solution, 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/de/forums/forum/support-in-german/.
Problem: The client is experiencing an issue where links within their multilingual site revert back to the primary language instead of leading to the correct language-specific URLs as configured in WPML. Solution: 1. Ensure that links are manually translated as explained in the WPML documentation on translating links with the Advanced Translation Editor. 2. If the issue persists, perform a full backup of your site. 3. Temporarily deactivate and then reactivate most of the plugins to check if this resolves the issue. 4. If the problem continues, it may be necessary to allow the WPML support team to troubleshoot directly on the production site, with precautions such as full backups and possibly escalating the issue to 2nd Tier Support.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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 encountered a fatal error related to the WPML plugin and other associated plugins, which was identified through error logs indicating issues with non-countable or null array types in specific PHP files. Solution: We recommended updating the WPML plugin and its add-ons to the latest version, specifically to version 4.6.12, to incorporate the latest bug fixes and improvements. This update process includes checking for the latest versions under 'My Account -> Downloads' on the WPML site and following the update instructions available at http://wpml.org/faq/install-wpml/. Additionally, updating WordPress, other related plugins, and the current theme was advised. It is also important to backup the database before proceeding and to clear the log after updating to verify if the errors persist.
If this solution does not resolve the issue or seems irrelevant due to its nature or because it might be outdated, please check related known issues at https://wpml.org/known-issues/ and confirm that you have installed the latest versions of themes and plugins. If problems continue, we highly recommend opening a new support ticket for further assistance.
Problem: You have translated the footer of your website using WPML, but it does not appear in the German language. You are unsure how to enable 'Translate texts in admin screens' and why the translated footer is not appearing. Solution: To resolve this issue, please follow these steps: 1. Copy the footer template ID. 2. Navigate to WPML-> String Translation. 3. Scroll down and click on the Translate texts in admin screens » link. 4. Search for the ID. 5. Select the string. 6. Click on the "Add to String Translation" button. 7. Then click on the "« Return to String Translation" link. 8. Translate the ID.
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.
Problem: You want to add an extra website to your WPML subscription and translate only selected pages automatically. Solution: First, install the WPML plugin on your new website and start the configuration process. Next, generate a new site key for this website through your account on wpml.org. During the installation, choose the "Translate What You Choose" method to ensure that only the pages you select are translated automatically. For more details on sending content for automatic translation, visit https://wpml.org/documentation/translating-your-contents/#sending-content-for-automatic-translation.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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 contact us through the WPML support forum.
Problem: The client was unable to access the translation of custom ACF select fields, despite following the documentation. The issue was that the translation editor was not functioning properly. Solution: We first ensured that the field group 'Spark Mentor Info' had a translation method configured, which was set to 'Same fields across languages'. This setup allows the translation of custom fields within the Advanced Translation Editor (ATE) when translating any post from the CPT containing the field group. To access the ATE, the client needed to edit a mentor in the main language and click on the pencil icon in the language section. Alternatively, it could be accessed from WPML -> Translation Management by sending the Mentors for translation, assigning the job, and then accessing it through WPML -> Translation.
If the solution provided here does not resolve your issue, or if it seems outdated or irrelevant to your case, 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 further assistance is needed, please open a new support ticket.
Problem: You are finishing the translation of your main site and the Swedish version, and you need to add a Danish translation. You are concerned about whether switching between using different directories for languages and using different domains for each language will affect your translations. Solution: We assure you that you can switch between using different directories for languages and using different domains without affecting your translations. Start by using different directories while working on your Danish translations and then switch back to using different domains for each language. WPML will handle this transition smoothly, and your existing translations will remain intact. Remember to re-save your permalinks after making these changes to ensure everything updates correctly.
If this solution does not resolve your issue or seems outdated, we 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 at our support forum.
Problem: You are trying to translate pages that include custom ACF Blocks using WPML's Advanced Translation Editor, but the ACF Block content is not appearing in the translation interface. Solution: First, ensure that your ACF Pro is updated to version 6.3.5, ACF Multilingual to version 2.1.3, and String Translation to version 3.2.14. After updating, you need to select a translation option for your field groups. We recommend following the steps outlined in this guide. If after completing these steps the ACF content still does not appear correctly in the translation editor, it might be due to an outdated solution or a different issue. 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: You are experiencing issues with your staging site not accepting the WPML license key that was used on your local site. Solution: If you're experiencing this issue, we recommend you generate a new license key when the URL changes. Here are the steps to follow: - Go to Plugins >> Add new > Commercial tab and click the 'Unregister WPML from this site' link if that link exists. - Click the 'Register WPML' link. - Click the 'Get a key for this site' link. - It will automatically generate the Key for your site with the updated URL. - Copy the key and paste it back into the input box and press the Register button, or you can add the key in the wp-config.php file. For more details, check the documentation here: https://wpml.org/faq/install-wpml/#register
If this solution does not apply to your case because it might be outdated or not relevant, 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 has a custom Gutenberg block with a heading attribute and content. The heading translates correctly when there are no nested blocks, but fails to do so when nested blocks are present, with only the nested blocks being translated. Solution: We resolved the issue by registering the custom blocks for translation. Here are the steps we recommend you follow: 1- Navigate to WPML-> Settings-> Custom XML tab. 2- Add the following code:
3- Save the changes. 4- Edit the page in the default language. 5- Click the Update button. 6- Update the translation using the translation editor. For more information on registering blocks for translation, please check this guide.
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 issue persists, please open a new support ticket.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
