![]() If you’ve worked with repeater fields before and would like to test this out, please give it a try and let us know if you see any issues. With all that said, we’re really excited to have paginated repeaters available in this beta. We’re looking into adding a useful placeholder here to better illustrate that these new rows have been added, but cannot be reordered.Īlso, repeater pagination will not work for fields used inside an ACF Block, as there would be no performance benefit given the repeater data is already stored in the DOM. As such, there is currently no row number displayed next to these rows. Rows that have been inserted in between existing rows and duplicated rows cannot be reordered until the page has been updated. Once you designate a new row number and update the page, the row will be moved to the new location. Instead, we’ve added the ability to reorder rows by clicking the row number – this will reveal a number input which can be used to designate where the row should be moved to: This doesn’t work with paginated repeaters, as you may need to move an existing row to a different page. With standard repeaters, you could reorder rows via a drag-and-drop interface. Once enabled, a new “Rows Per Page” setting will be displayed as well:Īs mentioned above, there are some user experience changes unique to paginated repeaters. You can enable pagination by editing a repeater field and turning on the “Pagination” setting. Not all repeaters will benefit from this setting, as there are a number of user experience changes to allow for pagination. It is not enabled by default and will not be turned on for existing repeaters. Please note, the pagination setting is opt-in. With the 6.0 release we have introduced a new setting for the Repeater, which enables pagination of the records when editing the data. This can lead to memory issues, running into the PHP max_input_vars setting, and the data not being saved correctly. ![]() When the post is saved, ACF will send all the subfields for every row back to the server to be updated, even if the data hasn’t changed. Depending on the number of rows and subfields, this can take some time, increasing the overall admin page load time and blocking the user from performing actions like saving the post. ![]() This can result in performance issues for the users filling out the data.Ĭurrently, when a user loads the edit page in the WordPress dashboard, ACF loads all the rows of data with all the subfields for each row. Over the years we have had many support requests from users who have been storing a large amount of data in Repeater fields. ACF PRO v6.0.0-beta1 is now available with improved performance for Repeater fields with large datasets, and a new generation of ACF Blocks. We’re excited to announce the first beta release of ACF PRO 6.0.
0 Comments
Leave a Reply. |