This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Tagged: Documentation request
This topic contains 4 replies, has 2 voices.
Last updated by Prosenjit Barman 1 year, 6 months ago.
Assisted by: Prosenjit Barman.
Author | Posts |
---|---|
December 4, 2023 at 10:56 am #14985437 | |
edwinv-4 |
Hello there, I have some issues with a website. I'm using the new Advanced Translation Editor. I've set ACF with Expert settings. Translating it works okay, but I notice the strings of ACF Flexible Content parts are also being translated. When I translate these, the sections disappear on the website. I've seen a support article on the website, which excludes this: https://wpml.org/errata/advanced-custom-fields-multilingual-the-group-fields-title-and-labels-are-translatable-by-default/. This doesn't solve it, sadly. Even when deleting the pages in the other languages, they stay when creating the new language. Is this because of the Translation Memory? Any idea how to solve? Using the Advanced Translation Editor now is very hard, because the strings keep appearing on the page and it has to be set manually. Thanks in advance! |
December 4, 2023 at 2:01 pm #14987603 | |
edwinv-4 |
I think deleting the Translation Memory will solve this question. I read on forums that this is only possible through support. Is that correct? In that case, can you delete it for: These strings are in Translation Memory stuck I guess? When resetting that they won't be sent anymore, or am I wrong? 🙂 |
December 5, 2023 at 8:04 am #14993513 | |
Prosenjit Barman WPML Supporter since 03/2023
Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00) |
Hello There, I understand the issue you're having and will try my best to assist you in this matter. The constant you've defined should hide the Title and Label from the Translation editor. However, if these elements have already been translated, they will continue to appear in the editor. Once you've set the constant, when you create a new post with ACF fields and attempt to translate it, those extra fields will not be visible in the Translation Editor. For the existing posts, you can try the following and check if that helps to solve the issue. - Delete the Translate of existing posts, even from the Trash bin I hope it will help to solve the issue. We generally don't recommend clearing the Translation memory but if the issue persists, please let me know. I will check for other options and try my best to address the issue for you. Best regards, |
December 5, 2023 at 8:22 am #14993751 | |
edwinv-4 |
Hey Prosenjit, Thanks for your reply. I tried to do this. I deleted all page, but not edited it. This would take me at least 40+ hours as the site has 500+ pages, sadly. I also tried to create a complete new environment, delete all translation pages, reset WPML from the Troubleshoot page, but no luck. Everything was still in the translation memory, and that's why it still showed the labels. Is there another way? Would clearing the translation memory solve this? Editing all the pages would take ages and that is sadly not a good solution for us. Maybe it's a weird suggestion, but I'm seeing some people having exactly my issue. Why isn't the Advanced Translation Editor noticing this constant in wp-config.php and doing something with it after the translation is made? That would help a lot. Thanks in advance. 🙂 |
December 6, 2023 at 3:39 am #15003503 | |
Prosenjit Barman WPML Supporter since 03/2023
Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00) |
Hi There, Please be aware that ATE is capable of identifying this constant and will ensure the Field group label and title remain hidden within the ATE. However, this happens only if the constant is added before you start the translation process. If you save your translation without setting this constant first, the translations for the label and title will be saved in the database along with the content translation. As a result, these additional fields become visible in the ATE when you try to update the translation even after defining the constant. I hope you can understand the reason. As outlined in our Errata and documentation, after defining the constant, you need to resend the page for translation by making a minor modification to the default page. But, at this moment, there are no alternative solutions available for this problem. If you want us to reset the translation memory for you, please let me know. I can do that for you. However, could you please confirm whether this issue still occurs when translating new pages that were created after defining the constant? If this is the case, do let me know. I will look into it and provide you with an update. Best regards, |
December 7, 2023 at 9:41 am #15015033 | |
edwinv-4 |
Hey there, When doing a minor update, checking the page, and finishing again that works! Thanks for the help. Clearing the memory isn't necessary. Cheers, |