[Resolved] ACF relationship field search field disabled in translated posts in v2.1.x of ACFML

Thanks for the sandbox site, I've been taking a look at the settings and to replicate the issue you need to set the post types to "Translatable use translation if available or fallback to default language".

I'm not getting exactly the same behaviour, on the sandbox it is possible to interact with the field, but it does still show you a message saying the field will be ignored.

"Warning: ... Whatever you set in this field for a secondary language post (this post) will be ignored and values from original post will be used (if you set to copy or duplicate value for this field)."

Spanish edit screen with the warning message:

hidden link

I've not yet been able to work out why on my site the input is disabled and the sandbox site it's not disabled. The sandbox does show what I believe to be an incorrect message to the editor.

Would the disabled attribute be something WPML adds? Or do I need to look elsewhere?

Ok, I've figured out the disabled field problem, it seems to be related to the version of ACF, I've rolled the sandbox site back to ACF v6.3.0 and the field is disabled. So that should be an easy fix.

hidden link.

Are you able to file a bug report related to the incorrect warning? Even after I update ACF the backend is telling the editors "Whatever you set will be ignored" on the translated posts. (Which I've tested above and is not true, the translated values are used on the frontend).

Many thanks,

Hi,

The field disabling is coming from this file in ACFML:

wp-content/plugins/acfml/assets/js/admin-script.js

```js
jQuery( function( $ ) {
$('.wpml_acf_annotation').prev().prop('disabled', true);
$('.wpml_acf_annotation.relationship').prev().find('input').prop('disabled', true);
$('.wpml_acf_annotation.taxonomy').prev().find('input').prop('disabled', true);
} );

```

I'll stop investigating now and await your input. I believe I've taken this as far as I'm able to and that this is an ACFML bug.

Many thanks