Thanks for taking the time to answer my question @jonathan! That’s definitely a sufficient answer. 🙂
I understand that putting a number on repeater rows is difficult, so I’ll take that in mind for the future when I’m thinking about adding a repeater field. Up till now I didn’t realize that could have been a problem. I’m not a backend developer (but a frontend developer), so I’m not very experienced in servers, databases, PHP and their limits.
I already switched my setup from a repeater field to a CPT. And to be honest, it’s already making way more sense. 😉
I’ve read the article from 10up, thanks for the link, pretty interesting stuff too!
Hi @jonathan I stumbled upon this topic trying to learn more about big data in the repeater field.
You mention more and worse issues with dumping big data in a repeater field. Can you elaborate on this? What would you consider to be feasible for the repeater field?
So I found a solution that made it work for me. I noticed that all metaboxes are added in ‘high’ priority, except those positioned on the side. Luckily there is filter in ACF to change this. So I changed the priority to ‘core’ and the remove_meta_box started working.
add_filter('acf/input/meta_box_priority', 'custom_meta_box_priority', 10, 2);
function custom_meta_box_priority($priority, $field_group) {
$priority = 'core';
return $priority;
}
Yes, that was a the next solution I wanted to look at. Thanks for your help. So it might be the wrong approach but I’m stil wondering why it isn’t working.
Hm, thought so too. But same thing. Only works if the metabox is added to the sidebar.
Currently, like this:
add_action('admin_menu', 'remove_menus', 99);
function remove_menus() {
remove_meta_box('acf-group_56fe3f88b745d', 'post', 'normal');
}
I also played with the priority, but that didn’t help.
I’m sorry, but I can’t seem to get the filter working…
Why is using remove_meta_box such a bad idea anyway? My question is still why this isn’t working when the position is set to something else than ‘side’.
