Support

Account

Home Forums Add-ons Options Page Nested Repeaters not working for Options Page when using WPML

Solving

Nested Repeaters not working for Options Page when using WPML

  • *UPDATE* I have noticed that the problem only occurs when using get_fields(‘options’), when I call the field directly e.g. get_field(‘add_social’, ‘option’) they seem to work. The bug must happen within the get_fields function. Unfortunately I am using Timber so would like to use this function.

    I am trying to use a nested repeater with an Options Page, but when I save the nested repeater fields are blank. I checked the output and no variables are getting saved (they are NULL and string(0)), though it has registered that a new row has been added to the repeater. When I assign the same nested repeater to a page or custom post type it works perfectly so the problem must lie with the Options Page.

    To go into further detail:

    When I duplicate the Options Page fields for another language and then try to save (country specific data) the fields show up blank for the Default Language (English). Strangely this only affects repeater fields and I feel is almost certainly a bug as the ‘id’ fields are showing the correct data, but the ‘name’ fields are showing NULL. I am really concerned now as have a major deadline looming and desperately need this functionality. Below is a print of the variables (this is from the repeater field) to show how the data is being saved perfectly to the ‘id’ fields, but not to the ’name’ fields:

    To summarise, this bug occurs when you have duplicated an options page into a different language and saved it. It seems to only break the repeater field content in the default language (english). The repeater fields work for the other languages, which gives me hope this is a bug and fixable.

    Many thanks in advance,

    Dave

    [“add_social”]=>
    array(6) {
    [0]=>
    array(6) {
    [“field_54a32febc6b44”]=>
    string(9) “Facebooks”
    [“field_54a32fddc6b43”]=>
    string(3) “790”
    [“field_54a33accc6b45”]=>
    string(23) “http://www.facebook.com”
    [“social_title”]=>
    NULL
    [“social_icon”]=>
    NULL
    [“social_url”]=>
    NULL
    }
    [1]=>
    array(6) {
    [“field_54a32febc6b44”]=>
    string(9) “Instagram”
    [“field_54a32fddc6b43”]=>
    string(3) “792”
    [“field_54a33accc6b45”]=>
    string(24) “http://www.instagram.com”
    [“social_title”]=>
    NULL
    [“social_icon”]=>
    NULL
    [“social_url”]=>
    NULL
    }
    [2]=>
    array(6) {
    [“field_54a32febc6b44”]=>
    string(9) “Pinterest”
    [“field_54a32fddc6b43”]=>
    string(3) “794”
    [“field_54a33accc6b45”]=>
    string(24) “http://www.pinterest.com”
    [“social_title”]=>
    NULL
    [“social_icon”]=>
    NULL
    [“social_url”]=>
    NULL
    }
    [3]=>
    array(6) {
    [“field_54a32febc6b44”]=>
    string(7) “Twitter”
    [“field_54a32fddc6b43”]=>
    string(3) “795”
    [“field_54a33accc6b45”]=>
    string(22) “http://www.twitter.com”
    [“social_title”]=>
    NULL
    [“social_icon”]=>
    NULL
    [“social_url”]=>
    NULL
    }
    }

  • Hi Dave

    I have the exact same issue, and I am using Timber as well.

    Did you happen to get this up and running by any chance?

  • Same here,
    anyone has a solution?

  • Do you have the PRO version or the free version? I think this is fixed in the PRO version.

    Pro is version 5 at this point, where the free version is version 4.

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

You must be logged in to reply to this topic.