Gravity Support Forums Topic: New Filters & Action Hooks Requests

Gravity Support Forums Topic: New Filters & Action Hooks Requests https://legacy.forums.gravityhelp.com/topic/new-filters-action-hooks-requests Gravity Support Forums Topic: New Filters & Action Hooks Requests en-US Sun, 19 Apr 2026 23:39:01 +0000 http://bbpress.org/?v=1.0.1 <![CDATA[Search]]> q https://legacy.forums.gravityhelp.com/search.php randomwalk on "New Filters & Action Hooks Requests" https://legacy.forums.gravityhelp.com/topic/new-filters-action-hooks-requests#post-20179 Tue, 08 Mar 2011 19:14:21 +0000 randomwalk 20179@https://legacy.forums.gravityhelp.com/ Hiya, I'm writing a plugin to GravityForms that adds some custom field types, and other miscellaneous bits. It's going well, but there's a couple places in GravityForms that would be lovely to have the apply_filters() and do_action() calls actually in there natively, so I don't have to 'hack core' (so to speak). They are: /js.php In the midst of the massive switch() statement, within the SetDefaultValues() function, if you could add (somewhere in there) the following: <code><?php do_action("gform_editor_js_set_default_values"); ?></code> that would enable people to add 'catchers' for the custom field types. --- /form_display.php Toward the end of the function get_form(), if you could change the return statement <code>return $form_string;</code> to: <code>return apply_filters("gform_get_form_filter",$form_string);</code> that would enable modules to use preg_replace and custom placeholder strings to let forms generate dynamic options for dropdowns and the like, along with any number of other customizations that I've not even dreamed of. --- /form_detail.php At the very end of the file, in the save_form() function, if you could add two actions, both just before the die() statements ... before <code>die("EndUpdateForm($id);");</code>, add <code>do_action( "gform_edit_existing_form", $id, $form_meta );</code> and before <code>die("EndInsertForm($id);");</code>, add <code>do_action( "gform_add_new_form", $id, $form_meta );</code> These changes would let developers trigger events on people either saving a new form, or updating an existing form. For example (as in my use case), creating a new post (custom post type) automatically, whenever a form is made, to streamline workflow. --- Thanks! I may have some other places to request hooks later on, but that's it for now (I think). It strikes me as these filters and hooks would be the work of a moment to include on your end, and increase significantly the extensibility of your plugin.