Source View: edit_term

To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).

Understanding Source Code

The best way to understand what a hook does is to look at where it occurs in the source code.

  • Action hooks look like this: do_action( "hook_name" )
  • Filter hooks look like this: apply_filters( "hook_name", "what_to_filter" ).

Remember, this hook may occur in more than one file. Moreover, the hook's context may change from version to version.

Source View

Line Code
3528      /**
3529       * Fires after a term has been updated, but before the term cache has been cleaned.
3530       *
3531       * @since 2.3.0
3532       *
3533       * @param int    $term_id  Term ID.
3534       * @param int    $tt_id    Term taxonomy ID.
3535       * @param string $taxonomy Taxonomy slug.
3536       */
3537      do_action( "edit_term", $term_id, $tt_id, $taxonomy );
3538
3539      /**
3540       * Fires after a term in a specific taxonomy has been updated, but before the term
3541       * cache has been cleaned.
3542       *
3543       * The dynamic portion of the hook name, `$taxonomy`, refers to the taxonomy slug.
3544       *
3545       * @since 2.3.0
3546       *