Polylang from 2.0 and later + ACF 4.4.8 problem.

  • msolowski

    (@msolowski)


    9 years, 2 months ago

    Hello everyone.
    I’m using WordPress 4.6.1, Polylang 2.0.4 & Advanced Custom Fields 4.4.8.
    Today I think I found some bug. Probably bug exists from version 2.0. I think like this cause I tested every versions from 1.9.2 to 2.0.4
    In my theme I have few custom templates. One of them is named: Realizations. In ACF I created a rule to show a custom field only when I select template “Realizations” in Attribute page section from dropdown menu. When I’m creating a new page in default language (Polish) everything is fine (template “Realizations” is selected). I have the wordpress default textfield to write a name of this page and custom field below this. I’m adding some text to both of them and press Publish. Problem is starting when I try to translate this page. On screen with translated content, for example in English language I have only standard textfields: title & content. Custom field is not present. It’s weird cause the name of the template is still “Realizations”. Even when I’ll try to change to the other templates, nothing is happens. I have default view of adding a new page. By this problem I have to use Polylang 1.9.3 cause everything is working properly. Even in WP 4.6.1. and earlier.
    Is anyone have the same problem?
    Please for some advice. Thanks in advance.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Chrystl

    (@chrystl)

    9 years, 2 months ago

    Hi
    Have you the Polylang metabox in Custom fields > Field Groups?

    jasionn

    (@jasionn)

    9 years, 2 months ago

    I have the same problem – ACF seems not to be translated. I can’t see polylang metabox in field groups. Any ideas?

    jasionn

    (@jasionn)

    9 years, 2 months ago

    I’ve found temporary workaround – add this to your template’s functions.php:
    add_filter(‘pll_get_post_types’, ‘add_acf_to_pll’, 10, 2);
    function add_acf_to_pll($post_types) {
    $post_types[‘acf’] = ‘acf’;
    return $post_types;
    }
    It does nothing but adds acf post type to those being translated by polylang

    For me seems like it’s working but I’m still testing. Let me know if you’ll find better solution…

    jasionn

    (@jasionn)

    9 years, 2 months ago

    Small correction in add_filter function – function add_acf_to_pll accepts one argument not two :), so should be:
    add_filter(‘pll_get_post_types’, ‘add_acf_to_pll’, 10);
    (rest should be the same)

    Tooo fast…:)

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Polylang from 2.0 and later + ACF 4.4.8 problem.’ is closed to new replies.