ACF looking for translated WPML field when translations for fields disabled

• joleksow

• February 13, 2016 at 8:15 am

I’m running the latest versions of WPML and ACF Pro.

I have translations for Field Groups and Fields set to “Do Nothing”.

I’m attempting to retrieve a value from an options page.

When ACF runs its acf_get_valid_post_id function, it’s appending a language suffix to the $post_id, despite translations being disabled. I would expect it to remain “options,” but, for example, on Arabic pages it’s getting converted into options_ar.

Is there a check missing to see if translations are desired for these fields before updating the $post_id value when viewing a translated version of a page?

• Elliot

• February 19, 2016 at 10:14 am

Hi @joleksow

Thanks for the question.

ACF will always modify the $post_id param during save/load irrelevant of the WPML setting to translate the field groups.

If you have an options page, and you don’t translate fiedl groups, you can still create independent values for all languages.
This is becuase ACF modifies the $post_id with the current language string.

I don’t I understand what the issue is here. Can you elaborate on why this is causing an issue?

• joleksow

• February 20, 2016 at 1:54 am

Thanks for the response, Elliot. What I’m trying to accomplish is being able to use the same field value for all locales without having to create separate instances for each locale. Does that make sense?

Specifically this is for an image, where it wouldn’t make sense to have different versions of it for different languages.

• John Huebner

• February 20, 2016 at 11:31 am

Try this https://gist.github.com/senlin/4fd15ba7a19533ceb9fe

• Elliot

• February 22, 2016 at 9:49 am

Hi @hube2

Great find! This is perfect,

@joleksow – I’ve also left a comment on that snippet with an even simpler way!

Thanks
E

• joleksow

• February 23, 2016 at 1:45 am

This looks great, many thanks to you both!