Problem: After updating the WPML translation plugin, you are unable to translate messages. Clicking the translation icon leads to a screen that continuously reloads without allowing translations. Solution: We recommend you test the translation again. There has been an update that should resolve this. If this solution does not resolve your issue or 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 at WPML support forum for further assistance.
Problem: If you're experiencing issues with the English version of your page not displaying, specifically on the rooms page, and encountering a 404 error similar to the one discussed in the WPML forums, we have a solution that might help. Solution: We recommend the following steps: 1. Navigate to WPML → String Translation. 2. Remove the translation for the Accommodation slug from String Translation. 3. Go to WPML → Settings. 4. Retranslate the Accommodation slug.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the 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 needed. You can do so at WPML support forum.
Problem: You are setting up WPML for the first time and have enabled translation for custom post types created with the ACPT plugin. However, when these are enabled, the Translation Management page crashes Solution: First, ensure that the custom post types are compatible with WPML. Although not officially tested by our team, the ACPT plugin, has developed an integration with WPML. You can find more details here: https://docs.acpt.io/integrations/wpml
But you need to make sure that the 'hierarchical' parameter for your custom post types is explicitly set to either true or false during registration. If this parameter is omitted, it may default to null, causing the error.
If these steps do not resolve your issues or the solution 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 problems persist, we recommend opening a new support ticket at our support forum.
Problem: If you're using WPML with WooCommerce and have enabled automatic translation, you might encounter an issue where duplicating a published WooCommerce product causes it to start translating immediately, even though you want the duplicated product to remain as 'drafts' and not be translated until it is published. Solution: Currently, there isn't a direct option in WPML to prevent automatic translation for duplicated products that are still in 'draft' status. A potential workaround is to disable automatic translation for the product post type until the product is ready to be published. 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 more personalized assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: The client has added a language switcher to the header of their WordPress site using WPML and wants the secondary and tertiary languages to be visible immediately upon landing on the homepage, without needing to click a drop-down arrow. Solution: If you have added the language switcher block, you can change its layout in the template where you added it. For detailed instructions, please refer to our documentation here: https://wpml.org/documentation/getting-started-guide/language-setup/language-switcher-options/#add-language-switcher-template. Additionally, you might find this screencast helpful: https://www.loom.com/share/6be801c66f3c44049ca47b657f6850b6?sid=b71b4d2d-138b-436a-a7a5-a83819873070. If these steps do not resolve your 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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problema: O cliente estava enfrentando um problema na página de finalização de compras do seu site. Não estava claro o que era esperado versus o que estava sendo exibido, mas o problema foi identificado como um conflito com um código CSS. Solução: Após a análise, descobrimos que o problema era um conflito com um código CSS. Recomendamos verificar e ajustar o CSS em questão para resolver o problema. Se você estiver enfrentando um problema semelhante, recomendamos que verifique o código CSS do seu site para possíveis conflitos.
Se esta solução não for relevante para o seu caso, ou se ela estiver desatualizada, sugerimos abrir um novo ticket de suporte. Recomendamos fortemente que verifique os problemas conhecidos, confirme a versão da correção permanente e verifique se você instalou as versões mais recentes de temas e plugins. Para assistência adicional, visite nosso fórum de suporte.
Problem: The client is managing multiple websites with a WPML plan and is unsure why each site has different credit numbers for translations. Only one site has been translated automatically into Spanish, while others have manual translations. Solution: We explained that in WPML, credits are managed per website from a shared pool, meaning each site has its own separate credit balance. The differences in credit numbers can be due to: 1. Different initial credit assignments to each site. 2. Variations in credit usage based on the amount of automatic translation performed on each site. For more detailed information on how credits work and their management, we recommend checking the following documentation links:
If this solution does not apply to your case, or if it seems outdated, please open 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, visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: You are using WPML to manage translations for your website with separate domains for different languages. The language switcher works on the .pl domain but not on the .com domain. Additionally, saving settings in WPML->Languages results in a red void/invalid message on the .com domain. Solution: First, ensure that all your domains (or subdomains) point to the same WordPress site where WPML is installed. For more information, please visit this documentation. Next, deactivate the "Validate on save" option, enter your second domain, save your changes, and then test the domain to see if it works. The validation message might be a false positive. After translating the page, check if you can access it using your secondary domain. If it doesn't work, your second domain might not be configured correctly. Additionally, check your config.php file for these lines:
Commenting out these lines can resolve the issue with the language switcher.
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: You are trying to edit some words after automatic translation using WPML, but when you select the text you want to edit, only a blank screen appears in the Advance Translation Editor. Solution: We recommend trying to access the Advance Translation Editor in a different browser or in incognito mode with all browser extensions disabled. This issue might be caused by browser extensions interfering with the editor. Additionally, when you encounter the blank screen, check for any errors in your browser console. Here is how you can view your browser console: Using Your Browser to Diagnose JavaScript Errors.
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. Additionally, you can open a new support ticket for further assistance at WPML Support Forum.
Problem: The client renewed their WPML license, but the system still indicates that their plan has expired. They are unable to access the plugin installation page. Solution: We confirmed that the client's account status is Active. The issue might be because the domain is not registered with us. We recommend following the steps in this article to resolve the issue: https://wpml.org/faq/how-to-remove-site-is-registered-on-wpml-org-as-a-development-site-notice Additionally, ensure you are using the latest versions of the WPML plugins. You can download them from your WPML account here: https://wpml.org/account/downloads Please install the plugins manually. Removing and reinstalling the plugins will not affect your existing WPML translations or settings.
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 unable to activate the OTGS Installer after renewing WPML and is having trouble installing the license key. Solution: 1. Remove your site from the allowed list by visiting https://wpml.org/account/sites/ and selecting 'Remove your site'. 2. In your site's backend, navigate to Plugins -> Add new -> Commercial tab, and click on 'Unregister WPML from this site'. 3. Click on the link below the field to enter the new registration key, which will redirect you back to your wpml.org account to generate a new registration key. 4. Paste the new registration key in Plugins -> Add new -> Commercial tab.
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 further assistance is needed, please open a new support ticket at WPML support forum.
The client is experiencing a PHP deprecation warning on custom post type pages when using the WPML SEO plugin with PHP version 8.3.19. The error message appears under the header, as indicated in the debug log.
Solution:
We have identified that this issue stems from a compatibility problem with PHP 8.3.19. Although this warning does not affect the functionality of the plugin or the site, it can be visually disruptive. We recommend disabling the debug mode in WordPress to prevent such warnings from being displayed. You can do this by editing your wp-config.php file and ensuring the following line is included:
1
define('WP_DEBUG_DISPLAY', false);
For more details on managing debug mode in WordPress, please refer to this article: Debugging in WordPress.
Please note that this solution might become 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 the issue persists, please open a new support ticket.
Problem: The client is using the Jobzilla Theme with WPML and has set German as a different language. They expected the default language home page to be 'http://nicl12.sg-host.com/', but it redirects to 'http://nicl12.sg-host.com/de/'. The client wants the default language home page to not include '/de/'. Solution: We advised the client to go to WPML -> Languages -> Language URL format and deactivate the option to show a directory for the default language. After this, they should save the changes and re-save the permalinks. This action should resolve the issue of the default language home page redirecting incorrectly. Additionally, we clarified that WPML cannot remove the language directory only for the frontpage of the default language. Instead, we suggested creating a root page, which is different from the frontpage in the default language, as described in our guide: Setting up a root page. If the client needs behavior outside the scope of WPML's standard features, such as custom coding, we recommended contacting one of our certified partners at WPML Contractors.
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 with us for further assistance.
Problem: If you're experiencing issues with shipping cost calculations in the translated version of your WooCommerce store, specifically for the EU zone, where the shipping cost cannot be calculated while other zones work fine, follow the steps below for a potential fix. Solution: 1. Go to your shipping settings. 2. Change the shipping calculation from "per order" to "per class". 3. Save the changes. 4. Then, switch it back from "per class" to "per order" and save again. 5. Test to confirm if the issue is resolved.
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.
Problem: You are trying to translate the alt tags of images on your website using the 'media translation' menu, but after translating the page, the alt tags remain in English. Solution: We recommend you to backup your site first. Then, follow these steps: 1. Open the file
After making these changes, check the translated page and inspect the image alt texts.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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.
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자의 추가 기록 없이, 이 목적으로 저장되거나 검색된 정보는 일반적으로 귀하를 식별하는 데 사용할 수 없습니다.
