Current status: Solving. . Done
Repeater Fields inside Flexible Field (on backend) not visible before first saving/publishing
  • Hi,

    first - this is the absolutely most incredible wp-plugin ever. :-) especially the flexible fields combined with repeaters ....

    and this is my point. i like it to configure nice and compact inputs to the backend. and there is a problem in a special usecase. i often configure repeater fields with a minimum and maximum rows of 1. i like to show input-options in table layout but without an "Add"-button. the only way i know is to set the rows limit both to 1.

    if i create a new post or add such a configuration as part of a flexible field, then there are no input-option. its always necessary to save/publish the post first to get these options visible.

    see attached screenshot ...
    repeater_fields_inside_flexible_fields.gif
    846 x 592 - 38K
  • Hi @dennis

    This sounds like a bad bug. So just to confirm,
    1. You create a flexible content field
    2. You add a repeater field as a sub field and set its min / mac rows to 1
    3. Editing a page / post shows the repeater sub field with no button and no rows

    I'll look into it
    Thanks
  • yes.

    "no button" is my intention. i use the repeater functionality for a nicer look and feel of the backend-configuration.

    "no rows" is the "bug". it seems to be necessary to save a post first and the there are the configured rows. sometimes its necessary to save twice. always when i nest repeater fields inside repeater fields.
  • FYI. I can confirm this bug and reported it on Oct 1. Glad to see it on the list of things to be looked at.

    (http://support.advancedcustomfields.com/discussion/3350/sub-repeater-min-and-max-rows-1-doesn039t-create-initial-row)
  • Yes, this obviously is the same bug. The biggest problem is the description for the client. i can handle this by myself, but my clients are a little bit confused with it. "oh, this is just a little bug - you have to save once or sometimes twice and then its all fine ..." :-)
  • I'm experiencing the same issue (using latest version). Glad I found this, thought I was doing it wrong.

    Additionally the initial value of my text fields in nested repeaters disappears (on the options page). Bug?
  • Thanks guys,

    I'll be fixing this in the next version