I’ve created a repeater field where a row contains 4-5 fields for text/date/number and one field containing an image. I’ve created a gallery in the frontend out of that repeater. Now that I have 106 rows I have a problem updating my site. At first it said memory exhausted, then I bumped memory and now I am getting timeout errors, uploading takes way too long and then breaks.
My question: is it a problem with the repeater? can I translate the structure to something else? What is a better alternative to that? Is it possible to paginate the repeater in the backend so that I dont need to download all rows at once?
Pagination of the repeater field is something that is on the to do list of the plugin’s author and will be making it into the plugin sometime soon(we do not have a timeline yet).
Regarding the issue at hand, it is recommended to make use of Custom Post type to breakdown the structure of the repeater so that the values can be entered on different pages. This will ease the timeout issues once the number of rows peaks.
@acf-support@robgordon@james Do you know if there is any update on this “Pagination of the repeater field is something that is on the to do list of the plugin’s author” – 4 years later any update? Thanks. Seems like such a basic concept to remove memory issues on repeaters.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
ACF PRO’s Flexible Content field allows you to create smaller pieces of UI and compose them into whole flexible patterns. In our latest article, we show how to use it to create swappable site sections and integrate it all in a theme.https://t.co/ZRocH8oJSp