For my sake, I went ahead and switched the way I was saving/loading the data. Would it make sense to instead save each player’s completion to a custom post type post? That way, each save only saves those 16 fields, and each load only has to loop through the post type.
John,
Thanks very much for the reply. Your explanation of why the backend fields cannot be saved as a serialized array makes much more sense to me, so I appreciate taking the time to explain. I am familiar with calling the post meta fields without the ACF functions on the front end, and tend to follow that pattern on most custom sites I build, should the clients ever accidentally/unintentionally disable/remove ACF.
As a follow-up on this (1.5 years later), I too am experiencing slow saves on roughly 150 repeater fields with about 5 fields in each. I’ve read that some plugins out there save all custom field data to 1 post meta field as a serialized array, but can’t find anything explaining if that’s even possible with ACF Pro. I assume no one has figured out a better way to handle this yet?
Anyone? I feel like this should be a fairly simple thing to answer.
Have you tried using the_field('county');
instead? Because if you’re just using get_field()
, it won’t display your results without writing it as echo get_field('county');