Problem: You are trying to translate entries via the WPML Translation Editor and expect to see all ACF fields from the page. However, you only see some of the fields, specifically starting from 'field-questions_3_answer_summary', and skipping the ones with indexes 0, 1, and 2. Solution: If you're experiencing this issue, it might be due to using the same field name across different fields. We recommend ensuring that each field has a unique name, regardless of whether the fields are from the same group or in different groups. For more details, check the documentation here: Using the same fields across languages.
Additionally, we suggest updating the 'Advanced Custom Fields Multilingual' addon to the latest version, which is currently 2.1.2. After updating, edit the fields on the original content and test the translation again. You can find the changelog and update instructions here: ACFML Changelog.
If these steps do not resolve your issue, the 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 for further assistance.
Problem: The client was experiencing an issue where updating the translation on one of the Portuguese pages caused all the layout content to disappear, resulting in a broken page. The Advanced Translation Editor (ATE) was not appearing, and when using the duplicate option, the page could be edited normally through the WordPress Editor, but automatic translations were not available.
Solution: We resolved the issue by ensuring that the field name "field-page_section-0" (intro) was consistent across languages. It was translated to Portuguese in ATE, while for French, it remained the same as English. We corrected the translation, and the Portuguese page started working correctly. We also advised the client that ATE does not usually translate special content like CSS, JS, HTML, JSON, IDs, etc. If automatic translation results in incorrect field names, the client can manually edit the translation in ATE and update the translation memory for future consistency. Additionally, we suggested using the Glossary feature to handle special words. For more information on translation memory, visit Translation Memory documentation, and for the Glossary feature, see Glossary Entries documentation.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If you're still facing issues, 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 the problem persists, please open a new support ticket with us.
Problem: The client is experiencing an issue where updating the default language page causes the pages in other languages to break. This seems to be due to the translation of ACF field group names, which should not be translated to maintain correct association with the templates. Solution: We recommend that the client ensures consistency in the translation method. If using the WPML Translation Editor, avoid manually editing the translated pages. Conversely, if preferring manual translations, switch to the WordPress Editor. This can be done by selecting the "WordPress Editor" option in the sidebar to prevent layout or configuration issues.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, we encourage you to open a new support ticket. We also highly recommend checking 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 contact us through the WPML support forum.
Problem:
After installing WPML, the client is unable to save translated labels for ACF button fields in other languages. The labels revert to the original English version, and changes are not reflected across different languages despite the "Same fields across languages" setting.
Solution:
If you're experiencing this issue, we recommend the following steps:
1. To change the translation across all translations of the field, edit the translation of the page where they appear by going to your Pages tab, selecting a translation, and editing it.
2. If you want to translate the links individually:
- Change the field groups translation option to "Expert".
- Navigate to WPML > Settings and set the desired fields to "Translate". This will include all variations such as "buttons", "buttons_0_link", "buttons_1_link", etc.
- Make a small change in the default page or post to update the translation.
- Proceed with the translation as desired.
Please note that this solution might be irrelevant if it's outdated or not applicable 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 the issue persists, 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자의 추가 기록 없이, 이 목적으로 저장되거나 검색된 정보는 일반적으로 귀하를 식별하는 데 사용할 수 없습니다.
