Good idea John (apols for previous ‘Jon’!). Ticket raised. Thanks for the responses (and your broad support and commenting across the forums).
Thanks Jon. I was aware of those two solutions but I should have included them as links in my post to make it obvious. My apologies for laziness!
In my eyes, delete_sub_field is not a valid sub-field version of delete_field due to it setting the value to null rather than deleting the data, which over time will create a lot of empty and unnecessary custom field data.
I have coded my own workaround for now but I was surprised to find this wasn’t a core function in this otherwise super-thorough mega plugin. 😀
Hi
Does no-one else have this issue when there are a lot of ACF fields on a page? I assumed this was a helpful topic to raise and hoped for a solution but perhaps no-one else has the issue.
Or am I doing something wrong or approaching the solution the wrong way? I’d be more than happy to have that pointed out to me if it fixes the issue for me as currently we’re having to consider moving away from ACF which is a shame for such a feature-rich commercial plugin we’ve invested a lot of time in.
Thanks.
Ben
