Dynamic Fields Engine 1.2.1 has 29 actions and 26 filters, read directly from its source code on Nov 18, 2026. The list updates automatically when a new version is released.
How to use these hooks
Actions let you run your own code at a specific moment. Filters let you change a value before the plugin uses it. Put your code in a child theme's functions.php or a code-snippets plugin, never in the plugin's own files, because updates overwrite them.
// Run your own code when Dynamic Fields Engine fires an action
add_action( 'rdcfe_activated', function() {
// Your code runs here.
}, 10, 1 );
// Change a value Dynamic Fields Engine is about to use
add_filter( 'rdcfe_is_pro_active', function( $value ) {
// Change $value here.
return $value;
}, 10, 1 );Parts of a name in {braces} are filled in at runtime (for example a post type or field ID). Choose Example on any hook for a ready-to-edit snippet.
All hooks
-
/** * Filter to check if Pro license is active. */ apply_filters( 'rdcfe_is_pro_active', false ); -
/** * This filter is documented in app/Fields/FieldTypes/AbstractFieldType.php */ apply_filters( 'rdcfe_field_wrapper_attrs', $wrapper_attrs, $field, $field_type ); -
/** * This filter is documented in app/Fields/FieldTypes/AbstractFieldType.php */ apply_filters( 'rdcfe_field_wrapper_classes', $wrapper_classes, $field, $field_type ); -
/** * This filter is documented below. */ apply_filters( 'rdcfe_location_user_context', $context, null ); -
/** * Fires after the plugin has been activated. */ do_action( 'rdcfe_activated' ); -
/** * Fires after all DCFE CPTs and taxonomies are registered. */ do_action( 'rdcfe_after_registration', $this->errors ); -
/** * Fires after all field groups are saved for a post. */ do_action( 'rdcfe_after_save_fields', $post_id, $post ); -
/** * Fires after term meta is saved for all matching field groups. */ do_action( 'rdcfe_after_save_term_fields', $term_id, $term ); -
/** * Fires after user meta is saved for all matching field groups. */ do_action( 'rdcfe_after_save_user_fields', $user_id, $user, $form_type ); -
/** * Fires after database migrations have been run. */ do_action( 'rdcfe_after_schema_migration', $installed_version, self::DB_VERSION, $result ); -
/** * Fires after a config is created. */ do_action( 'rdcfe_config_created', $post_id, $config_type, $data ); -
/** * Fires after a config is deleted. */ do_action( 'rdcfe_config_deleted', $id, $config_type, $config_data ); -
/** * Fires after a config status is updated. */ do_action( 'rdcfe_config_status_updated', $id, $config_type, $status ); -
/** * Fires after a config is updated. */ do_action( 'rdcfe_config_updated', $id, $config_type, $data ); -
/** * Fires after the CPT meta-field assets have been queued for the current edit * screen. */ do_action( 'rdcfe_cpt_meta_assets_enqueued', $post_type, $meta_fields, $hook ); -
/** * Fires after CPT meta fields are saved. */ do_action( 'rdcfe_cpt_meta_fields_saved', $post_id, $post, $meta_fields ); -
/** * Fires after the plugin has been deactivated. */ do_action( 'rdcfe_deactivated' ); -
/** * Filter the export data before returning. */ apply_filters( 'rdcfe_export_data', $export_data, $types ); -
/** * Fires after a field value is saved. */ do_action( 'rdcfe_field_saved', $meta_key, $value, $post_id, $field ); -
/** * Filters the validation errors collected for a meta-fields submission. */ apply_filters( 'rdcfe_field_validation_errors', $errors, $meta_fields ); -
/** * Filter health check response. */ apply_filters( 'rdcfe_health_check_response', $response ); -
/** * Filter import payload after resolutions are applied. */ apply_filters( 'rdcfe_import_after_resolutions', $out, $resolutions ); -
/** * Fires after import is complete. */ do_action( 'rdcfe_import_complete', $result, $data ); -
/** * Fires after the plugin has been initialized. */ do_action( 'rdcfe_init' ); -
/** * Filter the resolved context value for a given location-rule param. Pro can * use this to map UI param names that don't have a direct context key (e.g. * `page_template` → `post_template`). */ apply_filters( 'rdcfe_location_context_value', $value, $param, $context ); -
/** * Allow add-ons (e.g. the Pro plugin) to fully override matching for specific * params that don't fit the standard equality compare — * `current_user_capability` for instance is a `current_user_can()` check, not * a value match. */ apply_filters( 'rdcfe_location_match_rule', null, $param, $operator, $value, $context ); -
/** * Filter the options-page context array used by the location matcher. */ apply_filters( 'rdcfe_location_options_context', $context, $page_slug ); -
/** * Filter the post context array used by the location matcher. Pro can extend * it with extra keys like `post_author`, a flattened `post_taxonomy`, * `current_user_role`, etc. */ apply_filters( 'rdcfe_location_post_context', $context, $post ); -
/** * Filter the term context array used by the location matcher. */ apply_filters( 'rdcfe_location_term_context', $context, $term ); -
/** * Filters instruction/description placement for field-group metaboxes on post * screens. */ apply_filters( 'rdcfe_metabox_instruction_placement', $instruction_placement, $field_group ); -
/** * Fires after an options page is registered. */ do_action( 'rdcfe_options_page_registered', $menu_slug, $config ); -
/** * Fires after a post type is registered. */ do_action( 'rdcfe_post_type_registered', $slug, $result, $config ); -
/** * Fires after default field types are registered. */ do_action( 'rdcfe_register_field_types', $this ); -
/** * Filter the post type args before registration. */ apply_filters( 'rdcfe_register_post_type_args', $args, $config ); -
/** * Filter the taxonomy args before registration. */ apply_filters( 'rdcfe_register_taxonomy_args', $args, $config ); -
/** * Fires after RDCFE REST routes are registered. */ do_action( 'rdcfe_rest_routes_registered', $this ); -
/** * Fires after RDCFE plugin settings are updated via REST. */ do_action( 'rdcfe_settings_updated', $updated, $current ); -
/** * Fires after taxonomy meta fields are saved. */ do_action( 'rdcfe_taxonomy_meta_fields_saved', $term_id, $taxonomy, $meta_fields ); -
/** * Fires after a taxonomy is registered. */ do_action( 'rdcfe_taxonomy_registered', $slug, $result, $config ); -
/** * Fires after a user meta field is saved. */ do_action( 'rdcfe_user_field_saved', $meta_key, $value, $user_id, $field ); -
/** * Filter the field group validation result. */ apply_filters( 'rdcfe_validate_field_group', $result, $config ); -
/** * Filter the post type validation result. */ apply_filters( 'rdcfe_validate_post_type', $result, $config ); -
/** * Filter the taxonomy validation result. */ apply_filters( 'rdcfe_validate_taxonomy', $result, $config ); -
/** * Fires when field groups should be included. */ do_action( 'rdcfe/include_fields' ); -
/** * Fires when options pages should be registered. */ do_action( 'rdcfe/include_options_pages' ); -
/** * Fires when post types should be registered. */ do_action( 'rdcfe/include_post_types' ); -
/** * Fires when taxonomies should be registered. */ do_action( 'rdcfe/include_taxonomies' ); -
/** * Alternative hook name for familiarity. */ do_action( 'rdcfe/init' ); -
apply_filters( 'rdcfe_location_user_roles', $roles ); -
apply_filters( 'rdcfe_relations_post_types', $post_types ); -
apply_filters( 'rdcfe_relations_roles', $roles ); -
apply_filters( 'rdcfe_relations_taxonomies', $taxonomies ); -
apply_filters( 'rdcfe_upgrade_url', 'https://wpmet.com/plugin/dynamic-field-engine/pricing/' ); -
apply_filters( 'the_content', (string) $value );
Generated from Dynamic Fields Engine's GPL-licensed source code. Hooks inside bundled third-party libraries are not listed.
Done for you
Rather have it built for you?
Tell us what should change and we’ll write and test the code using these hooks.
Custom hook snippet
from $49
A small, update-safe change built on the plugin’s own hooks.
- Code written against the plugin’s actions and filters
- Tested on a staging copy of your site
- Install instructions included
Typical turnaround: 2–3 business days
Choose thisPlugin customisation
from $149
New features or changed behaviour, without editing the plugin’s files.
- Built as a companion plugin, so updates never wipe it
- Exact quote before we start
- Tested on staging, then deployed
Typical turnaround: 3–7 business days
Choose thisNot sure which fits? Describe what you need and we’ll suggest the simplest option.
Can't find the right hook?
We can build the customisation for you. Describe what you need: