Getting qTranslate-X to work with Advanced Custom Fields

No, ACF just adds very basic, generic class attributes. Here’s an example field:

`<input type=”text” id=”acf-field-catalogue_item_metadata_contributor” class=”text” name=”fields[field_536b984656093]” value=”” placeholder=””>

Thanks for your help, John, but that isn’t the issue. I have indeed set up the fields via their ID value, and that works fine on the form itself.

But it doesn’t work when the data is saved and passed through the $_POST array…because that uses the “name” attribute. Because of the way that qTranslate-X changes the field names, you end up with input name attributes like this:

fields[field_536b984656093]_edit

…which results in the data not coming through correctly in the $_POST array. When you change it to:

edit_fields[field_536b984656093]

it all works fine.

Having done some further testing, it looks as if the only thing which stops it from working is that the custom fields are loaded into the taxonomy form via AJAX and so aren’t present when the initial qTranslate field setup takes place.

If I add something like this into edit-tag.js:

setTimeout(function() {
            qtx.addContentHookByIdC('acf-field-category-subtitle', form);
        }, 5000);

then the addContentHookByIdC call takes place after ACF’s AJAX call has returned and the acf-field-category-subtitle field is set up correctly for qTranslate.

(I realise that’s a very crude method! It hopefully demonstrates that the timing of the addContentHookByIdC call is the only problem, though.)

Thanks, John. Yes, it looks like that works very well. Great stuff.