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 |
---|---|
1810 | * @since 3.0.0 |
1811 | * @since 4.4.0 The `$option` parameter was added. |
1812 | * @since 4.7.0 The `$network_id` parameter was added. |
1813 | * |
1814 | * @param mixed $value New value of the network option. |
1815 | * @param mixed $old_value Old value of the network option. |
1816 | * @param string $option Option name. |
1817 | * @param int $network_id ID of the network. |
1818 | */ |
1819 | $value = apply_filters( "pre_update_site_option_{$option}", $value, $old_value, $option, $network_id ); |
1820 |
|
1821 | /* |
1822 | * If the new and old values are the same, no need to update. |
1823 | * |
1824 | * Unserialized values will be adequate in most cases. If the unserialized |
1825 | * data differs, the (maybe) serialized data is checked to avoid |
1826 | * unnecessary database calls for otherwise identical object instances. |
1827 | * |
1828 | * See https://core.trac.wordpress.org/ticket/44956 |