Problem:
Client was using custom code where some strings were not being detected for translation, despite using proper gettext methods.
Solution:
It turned out there were unnecessary spaces in the strings and in the related ACF fields. Removing those fixed the problem.
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 the problem persists, please open a new support ticket.
Problem: You are trying to run custom actions when translated posts are saved using WPML, but the standard
1
save_post
hook no longer works after switching to automatic translation. Solution: We recommend using WPML-specific hooks that are triggered during the translation process. A useful hook for your case is
1
wpml_pro_translation_completed
, which fires when an automatic translation is completed. Here's how you can use it:
1
add_action( 'wpml_pro_translation_completed', function( $post_id) {// Custom action for translated posts});
If you need to catch updates to translated posts in general, another option is
1
wpml_sync_duplicate_content
, depending on your specific setup.
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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues where repeater field rows disappear in translations when the source language of a post is updated, this might be due to the translation settings of your fields. Specifically, if the field settings were changed from 'Copy once' to 'Translate' in WPML, updates to the original post require retranslation to maintain the repeater fields in the translated versions. Solution: We recommend using the 'minor edit' option when updating posts that have been translated. This approach helps in preventing the disappearance of repeater fields in translations when the source post is updated. If the translation still does not reflect the changes correctly, you may need to manually update the translation through WPML's Advanced Translation Editor (ATE) or adjust the field's translation preference settings back to their original state if feasible.
Please note that this solution might not be applicable if it's outdated or not relevant 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: You are trying to use a one-click translation solution with WPML for a WYSIWYG Editor Advanced Custom Field named 'description', which is set to 'Translate'. Previously, this field was set to 'Don't translate' and was manually translated in the WordPress editor. After changing the setting and using Automatic Translation, the field does not translate unless you modify the English version, save it, and resend for translation. Additionally, you encountered PHP errors related to 'post_content' and 'post_type' being null. Solution: We recommend applying the workaround detailed in our errata page. Please visit Changing Translation Preferences for Custom Fields. Alternatively, you can try editing the original 'description' field on the original content, save the page, and then let the translation process run again.
If this solution does not resolve your issue or seems outdated, please check for 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 highly recommend opening a new support ticket for further assistance at WPML support forum.
Problem: The client was unable to use the Advanced Translation Editor (ATE) as the server appeared to be down, which was affecting their work. Solution: We asked the client to inform us about the specific error they were encountering and to attempt accessing ATE once more to check if the issue persisted. We then advised the client to clear their browser cache or try accessing ATE from a different browser, as recommended by our colleagues from the ATE department.
If you're experiencing similar issues with ATE, we recommend you first check the error message and try accessing the service again. If the problem continues, clear your browser cache or switch to a different browser. This should resolve the issue.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket with us.
당사는 웹사이트와 서비스를 최적화하기 위해 쿠키를 사용합니다.
사용자의 동의를 통해 탐색 행동과 같은 데이터를 처리할 수 있습니다.
동의하지 않으면 일부 기능에 영향을 미칠 수 있습니다.
기능적
항상 활성화
웹사이트가 올바르게 작동하고 통신하는 데 필요합니다.
기본 설정
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
통계
당사는 이를 사용하여 사이트의 통계를 분석합니다.
수집된 정보는 완전히 익명으로 처리됩니다. 익명 통계 목적으로만 사용되는 기술적 저장 또는 접근입니다. 소환장, 인터넷 서비스 제공자의 자발적인 협조 또는 제3자의 추가 기록 없이, 이 목적으로 저장되거나 검색된 정보는 일반적으로 귀하를 식별하는 데 사용할 수 없습니다.
