Background of the issue:
Since WPML 4.7 it says a message something in the line of:
Starting with version 4.7, WPML will also automatically translate texts (strings) coming from ACF Field Group, Gravity Form.
WPML will not translate existing texts of this type, but any new texts you create will be translated automatically. If you prefer, you can start translating existing content now.
We do NOT want this to happen for ACF Field Group. How can we turn this OFF?
Symptoms:
WPML automatically translates texts from ACF Field Group, which I do not want.
Questions:
How can I turn off automatic translation for ACF Field Group in WPML? Any filter for this?
Adding a field updates affected post types and adjusts them. This may take time. Once the scan is complete, the issue should be fixed. Please check if the issue persists after the update.
The define allows you to disable the fields labels from Automatic Translations Jobs, but since you are using translate everything automatically, it will also translate the strings even with the define in wp-config.php, it's not possible to disable translations for labels and choices with "Translate Everything Automatically"
Well I did as you said and I waited. But this still happens. The fatal error. This only happens after I change my ACF.
Somehow it is translating the field-names (not the labels) of all the ACF fields I have.
So the label for example is "Content 1 koloms" and the name is normally "content_1_koloms".
But after adding my fields, the name becomes 'content_1_columns' in English.
It NEVER should change the names! Labels, no problem, but names is a big issue!
This can never happen because the name is linked to the function get_row_layout() from ACF.
The "content_1_columns" string is found in wp_2020_postmeta somehow. Nowhere else. This just does not make any sense.
After I update the page/post (without any real changes), it changes back in the database to what it needs to be.
To debug this issue further, I would need to check your site settings once, for this I would need temporary access (wp-admin and ftp) to your site.
So could you please provide me with those details, you will find the needed fields for this below the comment area when you log in to leave your next reply. hidden link
I added some content to the post, hidden link content_0_content and translated it, checked the postmeta for it's translations and I can't see the content_0_content being translated on the staging site.
Yeah you did this for new content, I don't know about that. My problem is in existing content. But please take a look at the homepage for example.
---------------
This is NL: hidden link
This is EN: hidden link
Now you can clearly see it not working in the EN right?
This is because the flexible row layout name (not the label) got translated.
And this goes wrong because we do an include of the flexible row name, e.g. "content_1_koloms".
Code example:
include(locate_template('components/' . get_row_layout() . '/' . get_row_layout() . '.php'));
---------------
So what happens as far as I can see:
1.
All is fine on the website (all pages etc).
2.
Then you add an ACF field in the flexible content.
3.
WPML does it's thing syncing stuff.
4.
Translated EN pages somehow get the names (not labels) of the flexible content rows translated.
And what happens at step 4 should never happen.
---------------
Take a look here: hidden link
That is the "content_1_koloms". This should always be the case. Never be translated.
But in the EN pages it's "content_1_columns". So this happens after we add an ACF field. This you can see in the 'postmeta' table in phpMyAdmin.
---------------
I hope to hear from you. If you need any other info, let me know.
Maybe i can make the test-site working correctly again and than make a video of the whole process and all steps I do when things get broken.
