Support

Account

Home Forums Backend Issues (wp-admin) Repeater fields with File field don't show in edit page

Solving

Repeater fields with File field don't show in edit page

    • likipe

    • January 29, 2014 at 1:33 am

    When a Repeater field with a File field have entries, it doesn’t show when editing that post. The field seems to be skipped. It shows when creating a new post, or when editing a post that doesn’t have entries in that field.

    • James

    • January 29, 2014 at 6:14 am

    Hi @likipe,

    I am not quite sure I follow you.

    So you have a File field that is repeated using the Repeater. When you populate the data in the post, it does not show when you edit it again?

    • likipe

    • January 29, 2014 at 7:10 am

    Hi,

    yes, that’s correct. I have a File field that is repeated using the Repeater. When I upload files using that field, it does not show when I edit the post again.

    • James

    • January 29, 2014 at 12:54 pm

    Hi @likipe,

    This might be a bug. If you wouldn’t mind, I’d like to get some more information from you:

    What version of ACF and WP are you using?

    Is there any other fields attached to the post (within, or outside the repeater field in question), and do they appear when editing?

    Cheers

    • Elliot

    • January 29, 2014 at 12:54 pm

    Hi @likipe

    Are you able to take a screencast of the issue? This would help us diagnose where the issue is coming from.

    Also, can you you try other combinations of sub fields? Is it only the file field which does not save?

    Thanks
    E

    • likipe

    • January 29, 2014 at 4:09 pm

    Hi @elliot,

    I tried your suggestion and added another simple text field to the repeater. After that the repeater field shows when editing the post, I then removed the text field and the repeater with File field still shows now. So I guess the problem is solved now and perhaps it was because the custom field layout didn’t saved properly in the db?

    • Elliot

    • January 30, 2014 at 9:56 am

    Hi @likipe

    Thanks for the follow up. Without seeing the before and after, I’m still not exactly sure what was going wrong. But if the issue has resolved itself, yes, lets hope it was a DB error and the problem is now solved!

    Thanks
    E

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

You must be logged in to reply to this topic.

We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Cookie Policy. If you continue to use this site, you consent to our use of cookies.