WP hooks navigation: Home/browse • Actions index • Filters index
To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).
The best way to understand what a hook does is to look at where it occurs in the source code.
do_action( "hook_name" )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.
| Line | Code |
|---|---|
| 386 | /** |
| 387 | * Filters an option before its value is (maybe) serialized and updated. |
| 388 | * |
| 389 | * @since 3.9.0 |
| 390 | * |
| 391 | * @param mixed $value The new, unserialized option value. |
| 392 | * @param string $option Name of the option. |
| 393 | * @param mixed $old_value The old option value. |
| 394 | */ |
| 395 | $value = apply_filters( 'pre_update_option', $value, $option, $old_value ); |
| 396 | |
| 397 | /* |
| 398 | * If the new and old values are the same, no need to update. |
| 399 | * |
| 400 | * Unserialized values will be adequate in most cases. If the unserialized |
| 401 | * data differs, the (maybe) serialized data is checked to avoid |
| 402 | * unnecessary database calls for otherwise identical object instances. |
| 403 | * |
| 404 | * See https://core.trac.wordpress.org/ticket/38903 |