Problem: The client was experiencing issues with synchronization in WPML with Crowdin. There were three pending jobs that could not be processed or cancelled, specifically related to the 'Dark Homepage' and a 'Borrower Loan popup BTN'. The synchronization seemed to be stuck, and attempts to manually finish or cancel the jobs were unsuccessful. Solution: We resolved the issue by following these steps: 1. Navigate to WPML > Translation Management. 2. Select 'Dark Homepage' and send it for automatic translation to Dutch and Polish. 3. Go to WPML > Translations and approve the translations. This approach typically resolves issues where translations are stuck. We recommend trying the same steps for the 'Borrower Loan popup BTN' that was also mentioned.
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.
Problem: You are experiencing issues with the WPML plugin on your site, specifically it stopped working because it cannot load configuration files. The logs indicate a cURL error 28: Resolving timed out after 10000 milliseconds, and the WPML plugin cannot connect to wpml.org to check for new releases and security updates. Solution: First, verify if the /wp-json on your site is accessible as this might be a false negative. If it is accessible, the next step is to contact your hosting support for further investigation into the cURL error and the connection issues. They can provide more specific guidance on resolving these network-related issues.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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 experiencing issues with the integration between WPML and Crowdin on a WordPress site supporting 20+ languages. The integration picks up unnecessary strings, and syncing between the two systems is unreliable, making it difficult to understand why updates are not reflected. Solution: We cannot provide a custom integration between WPML's automatic translation and Crowdin Translation Service as the translation memory systems of the two are incompatible. However, if you're facing issues with the current integration with Crowdin and need further investigation into what is not working, we are ready to assist you. Additionally, if you are considering moving to WPML's automatic translation option, please provide more details on what you aim to achieve and share your site's Debug information with us. You can find instructions on how to provide this information here.
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 here.
Problem: The client was unable to send a template string to their Translation Service (CrowdIn). The string appeared in the basket before sending but got lost during the process. This issue did not occur with a similar string in a different template.
Solution: We investigated and suggest the following steps: 1. Verify if the template "Front Landing TMPL" has been sent to Crowdin and check if it has been translated and delivered. 2. Check the WPML Jobs tab for the status of the translation jobs. If jobs were opened in a local translator and then canceled, they might not appear in WPML. 3. If you manipulated the database and emptied the icl_translate_jobs table, this could cause the issue. Instead, follow our recommended method to reduce the size of WPML tables: Reducing the size of WPML tables. 4. For the specific string that is not being sent, you can: A. Copy the translation from another language, as done with Bulgarian. B. Send the template to a local translator and use the Classic Translation Editor. C. Delete the problematic string in String Translation, update the template, and translate it again, possibly using translations from a similar string.
Please ensure to back up your site before making any changes.
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 WPML Known Issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If necessary, please open a new support ticket in our support forum.
Problem: The client needed to activate only 3 specific languages on certain pages using WPML, while keeping other pages with the full set of languages. They also requested documentation for the languages array and information on variables inside
1
[wpml_language_switcher]
and
1
[wpml_language_selector_widget]
shortcodes, as well as how to get the current language flag URL outside of the shortcode using PHP.
Solution: We recommended the client to review the following documentation:
Additionally, we suggested checking our hooks reference for more advanced customization options: WPML hooks reference.
If the provided solution is not relevant 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 you still need assistance, please open a new support ticket in our forum: WPML support forum.
Problem: The client is experiencing issues with accessing the editor menu in Bricks Builder on their development site. They encounter a WPML banner with a message indicating the site is registered as a development site and then get redirected back to the Site Dashboard. Additionally, they face a 302 redirect when trying to edit with Bricks, and receive communication errors when pulling in translation data. The Tools and Jobs pages do not load and display errors. The issue was found to be related to a custom function added by a developer that broke the /wp-json endpoint.
Solution:Remove a function that is added from the dev with a script to console log
Problem: The client is confused about the functionality of the WPML Automated Translation Editor (ATE) and its interaction with the Crowdin translation service. They are experiencing issues with translations being overwritten, pages not rendering without approval in ATE, and the necessity of using ATE when automated translations are turned off. Additionally, they are seeking clarification on how to manually edit translations and how to update translations from Crowdin to WPML.
Solution: 1. ATE and Crowdin use different translation methods and cannot be used simultaneously. If you prefer not to use automated translations, switch to manual translations. 2. A page may not render if it's not translated 100% in ATE. Check the icon status for the translated page. 3. To avoid ATE and use manual translations, disable ATE and switch to the WordPress editor. For detailed steps, see our documentation on using different translation editors for different pages. 4. ATE cannot be used with the translation service method as they do not share a translation memory. 5. To update translations from Crowdin, send the page for translation, and once completed, send translations back from the dashboard. WPML will then sync the translations. For more information, visit our documentation on updating translations without resubmitting them to a translation service. 6. Any new changes in the default language page require re-translation.
If this solution doesn't look relevant, please open a new support ticket in our support forum.
Problem: The client is trying to detect strings for translation within a Bricks Builder element named "code". The client attempted to use existing documentation for Elementor and HTML but found that these guides did not work for their specific case.
Problem:
If you're experiencing issues with the language switcher not rendering content on a Bricks Builder Landing page, while other templates and pages translate fine, and you've noticed that the header and footer are translated correctly, this summary is for you. The client found that the language switcher worked on individual templates but not on the landing page, despite setting conditions for the templates to display based on the selected language.
Solution:
We recommend the following steps:
1. Edit the home page using Bricks and add a header element.
2. Update the page.
3. Translate the page using your translation management system.
4. Check if the translated pages show the translated header and template.
If you've followed these steps and the content is still not rendering correctly, or if this solution doesn't seem relevant to your issue, please open a new support ticket with us, and we'll be happy to help.
당사는 웹사이트와 서비스를 최적화하기 위해 쿠키를 사용합니다.
사용자의 동의를 통해 탐색 행동과 같은 데이터를 처리할 수 있습니다.
동의하지 않으면 일부 기능에 영향을 미칠 수 있습니다.
기능적
항상 활성화
웹사이트가 올바르게 작동하고 통신하는 데 필요합니다.
기본 설정
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
통계
당사는 이를 사용하여 사이트의 통계를 분석합니다.
수집된 정보는 완전히 익명으로 처리됩니다. 익명 통계 목적으로만 사용되는 기술적 저장 또는 접근입니다. 소환장, 인터넷 서비스 제공자의 자발적인 협조 또는 제3자의 추가 기록 없이, 이 목적으로 저장되거나 검색된 정보는 일반적으로 귀하를 식별하는 데 사용할 수 없습니다.
