I would be curious to see a solution where duplicating the fields isn’t required. Sometimes post archive templates look the same, but they are custom and each require unique fields/settings. I may have 20 CPT Archives that all look the same and would be neat if the option storage could be connected with page it’s on. So for a field called “_description”, the slug of the page could be stored with it like “_staff_settings_description”.
I’ve tried modifying the field names to just post values under different fields, but ACF must be looking up the “option_name” value with the field ID and always store it under that name. I’m looking for this code to see if I can modify it as well.
