We would like to deploy ACF into a site that has a number of other plugins that make use of custom fields. In order to minimize confusion, we would like to make sure that someone using ACF cannot accidentally create a field that uses the same field name as a field vital to one of the pre-existing plugins.
Is there a way to let ACF know that certain field names are out-of-bounds. For example, is there a filter to validate a new field being created so that we could check the field_name entry and throw an error if it is on our “protected” list of names?
