Problem: You want to assign prepaid credits to your website, but it is not listed in the manage credits section. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Go to Plugins → Add New and click the Commercial tab. If you see an 'Unregister WPML from this site' button, click it. If not, proceed to the next step. 2. After the page loads, click on 'Register WPML'. You will see a message asking you to enter the site key. Click on 'Get a key for this site'. 3. Complete the site key wizard in your WPML account. 4. Copy your new key and paste it in the Commercial tab. Then, delete your old site key in your WPML account. 5. Now, you should be able to assign the credits to your site.
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.
Problem: The client was updating their website when they encountered a conflict between WPML and BetterDocs Pro, causing the website to stop functioning. Solution: We identified that the error originates directly within the BetterDocs Pro plugin. We recommend updating all WPML plugins to the latest version, specifically to version 4.7.3, as this may resolve the issue. If the problem persists after updating, we advise contacting the developer of BetterDocs Pro, as they might already have a solution to this error. Please let us know the outcome.
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.
The client was experiencing issues with broken CSS on their multilingual site pages using the Bricks theme. The CSS conflicts occurred because the Bricks theme custom fields were set as 'Don't translate', preventing styles and alignment preferences from being copied to secondary language pages.
Solution:
We resolved the issue by adjusting the WPML settings to ensure that the Bricks theme custom fields are copied to translations:
1) Navigate to WPML>>Settings>>Custom Fields Translation. 2) Click on the Show system fields link. 3) Search for 'bricks' fields. 4) Select the Copy option for these fields and save the changes. 5) Open the Contact page for editing in Romanian and update the page. 6) Update the English translation of the Contact page. 7) Repeat steps 5 and 6 for the Order page.
We recommend clearing your site's caches after these changes.
If the issue persists or if this solution becomes 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 necessary, do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: You need to export product attributes and their translations into a single table using SQL or the WP ALL EXPORT plugin, but currently, they export as separate rows. Solution: We tested the WP All Export Pro and WP All Export - WooCommerce Export Add-On Pro plugins and found that each translation has a separate Term ID, causing each term to start on a new line in the export file. To organize the data in a single table, you can add the custom fields _wpml_import_language_code and _wpml_import_translation_group. After adding these fields, sort your spreadsheet based on _wpml_import_translation_group to group the English term with its translations. Additionally, consider using AI to reorganize the spreadsheet if necessary, as it might be simpler than custom coding.
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.
The client was unable to send a Global Header with base64 encoded fields for translation using WPML. Attempts to configure custom XML to handle the encoding were unsuccessful, resulting in errors and the removal of content from the translation job.
Solution:
We recommended updating the XML configuration in WPML settings to properly handle base64 encoded fields. Here is the correct XML configuration:
This configuration should be added under WPML->Settings->Custom XML Configuration. Additionally, we provided links to relevant documentation and known issues:
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 updating the WPML plugins, the backend of the WordPress site stops working, and the browser times out. Disabling the WPML main plugin resolves the issue temporarily, indicating a potential database-related problem. Solution:
1. Edit wp-config.php and insert the following lines (just before /* That's all, stop editing! Happy publishing. */ part)
1
2
3
define( 'WP_DEBUG', true);
define( 'WP_DEBUG_LOG', true);
define( 'WP_DEBUG_DISPLAY', false);
2. Reproduce the issue
3. Locate the debug log in: /wp-content/debug.log
4. You should see the actual error that causes the issue.
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 at WPML support forum for further assistance.
Problem: You are experiencing site downtime when attempting to show translations in WPML on your WordPress site. This issue occurs when trying to retrieve all translations, causing the site to go down for 2-3 minutes. Solution: We recommend checking your server's RAM capacity as insufficient RAM can lead to such issues. In this case, the client resolved the problem by upgrading their server plan, which provided additional RAM, thus handling the load of retrieving translations without causing downtime. Before making any changes, ensure to back up your database. If you're experiencing similar issues, it might be due to insufficient server resources. We suggest upgrading your server or optimizing your current resources.
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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: You are trying to update the homepage translation into Italian, but the updated and translated part is not displaying properly. Translated items are scattered, and pictures are missing. Solution: We accessed your site using the previously provided details and made a minor edit to the homepage in English, then updated it. Subsequently, we updated the Italian translation. This approach should resolve the display issues on the Italian version of the homepage. Please check the Italian homepage to confirm if everything appears as expected.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also advise checking the related known issues and verifying that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.
Problem: The client is unable to edit the URL of a hyperlink when the entire line of text in a cell is the link text, as experienced while translating a blog post using WPML. Solution: We recommend modifying the HTML structure of the hyperlink. This change should allow WPML to recognize and provide the option to edit the URL in the translation editor.
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.
Problem: The client is experiencing issues with URLs and an image in the sidebar slider not translating correctly after updating WPML and Elementor. The URLs used to appear in the Advanced Translation Editor (ATE) and the image used to translate both the URL and the image itself. The client has added XML for other translations but is unsure if the same approach can be applied to the sidebar image and URL, which are managed via String Translation. Solution: We recommend translating the strings associated with the sidebar image and URL in the 'widgets' text-domain. This should resolve the issue with the translations not appearing correctly on the frontend. If you're experiencing this issue, ensure that you translate both the URL and the image source strings.
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 persists, please open a new support ticket.
Problem: The client is experiencing issues with large MySQL data tables due to the 'Translate Everything Automatically' feature in WPML, which is translating more content than necessary. The client is also unable to exclude specific post types from being translated and is concerned about the increased costs and database size.
Solution: Our developers are aware that WPML's tables can grow to a huge amount of data and they are looking into optimizing the dataflow in WPML 4.8. Further, in case you need more control about what should be translated in which way, we recommend disabling the 'Translate Everything Automatically' option. This can be done at WPML > Translation Management > Dashboard on the top right. By disabling this option, the client can manually select which content to translate or assign it to other translators. For further guidance on managing translations, we suggest reading this guide: https://wpml.org/documentation/translating-your-contents/.
If the solution provided does not resolve the issue or seems outdated, or if it does not apply to your specific case, please open a new support ticket. 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, visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: You are trying to edit a CN translation of a post on your bilingual website but receive an error message stating, "You attempted to edit an item that doesn't exist. Perhaps it was deleted?" even though the post is live. Solution: We have identified that this issue is not directly related to WPML but is a known WordPress issue. You can find more details and a suggested workaround on our errata page. Please visit the following link to resolve the issue: WordPress 6.7 - You attempted to edit an item that doesn't exist with translated post type slugs.
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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is using WPML with the Avada theme, and on their site, the translated pages are displaying the correct language-specific widgets, except on two pages. Specifically, the English version of the site is showing Dutch widgets on the pages for 'speed skating lesson' and 'contact' instead of the translated English widgets. Solution: We resolved the issue by following these steps: 1. Navigate to WPML -> String Translation. 2. Open the 'Not seeing strings that you are looking for?' tab. 3. Click 'Admin Texts Translation'. 4. Search for the needed strings. 5. Select the strings. 6. Click on the 'Add to String Translation' button. 7. Then click on the '« Return to String Translation' link. 8. Translate the strings, clear the cache, and check the front end. For more detailed guidance, please refer to our guide on translating texts in the admin texts screen: Translating texts that don't appear on the String Translation page.
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 the problem persists, please open a new support ticket for further assistance.
Problem: You are experiencing issues with language switching on your website using WPML with three domains. Specifically, when switching back to the default Dutch domain (dogmills.nl) from either the English (dogmills.eu) or German (dogmills.de) domains, the link does not revert to .nl as expected. Additionally, accessing the backend of dogmills.nl sometimes redirects to dogmills.eu, causing incorrect WPML language settings. Solution: We found that the problem is linked to one of the must-use plugins on your site, which seems to be configured for handling temporary domains. To resolve this issue, we recommend disabling these must-use plugins. You can do this by renaming the must-use plugin folder. After renaming, check if the language switching and domain redirection issues are resolved. If necessary, consult with the plugin author to understand the purpose of these plugins on your site and whether they are still needed.
If this solution does not apply to your situation, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If problems persist, we highly recommend opening a new support ticket with us for further assistance.
Problem: The client is experiencing an issue where the translated pages display a menu that blocks the entire page and cannot be closed. This problem arises because WPML automatically translated the ID from #traveller-megamenu to #viaggiatore-megamenu, causing functionality issues. Solution: If the IDs and class names are added through custom fields, we recommend setting these fields as not translatable in WPML. If they are part of the page content, you should use the translation editor to manually copy the default language values to ensure the IDs and class names do not change in the translation.
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
쿠키 동의 관리하기
당사는 웹사이트와 서비스를 최적화하기 위해 쿠키를 사용합니다.
사용자의 동의를 통해 탐색 행동과 같은 데이터를 처리할 수 있습니다.
동의하지 않으면 일부 기능에 영향을 미칠 수 있습니다.
기능적
항상 활성화
웹사이트가 올바르게 작동하고 통신하는 데 필요합니다.
기본 설정
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
통계
당사는 이를 사용하여 사이트의 통계를 분석합니다.
수집된 정보는 완전히 익명으로 처리됩니다. 익명 통계 목적으로만 사용되는 기술적 저장 또는 접근입니다. 소환장, 인터넷 서비스 제공자의 자발적인 협조 또는 제3자의 추가 기록 없이, 이 목적으로 저장되거나 검색된 정보는 일반적으로 귀하를 식별하는 데 사용할 수 없습니다.
