Source View: updated_option

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
376      /**
377       * Fires after the value of an option has been successfully updated.
378       *
379       * @since 2.9.0
380       *
381       * @param string $option    Name of the updated option.
382       * @param mixed  $old_value The old option value.
383       * @param mixed  $value     The new option value.
384       */
385      do_action( 'updated_option', $option, $old_value, $value );
386      return true;
387 }
388
389 /**
390  * Add a new option.
391  *
392  * You do not need to serialize values. If the value needs to be serialized, then
393  * it will be serialized before it is inserted into the database. Remember,
394  * resources can not be serialized or added as an option.