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 |
|---|---|
| 235 | * @param string $username User's username. |
| 236 | * @param string $password User's password. |
| 237 | * @return WP_User|bool WP_User object if authentication passed, false otherwise |
| 238 | */ |
| 239 | public function login( $username, $password ) { |
| 240 | /* |
| 241 | * Respect old get_option() filters left for back-compat when the 'enable_xmlrpc' |
| 242 | * option was deprecated in 3.5.0. Use the 'xmlrpc_enabled' hook instead. |
| 243 | */ |
| 244 | $enabled = apply_filters( 'pre_option_enable_xmlrpc', false ); |
| 245 | if ( false === $enabled ) { |
| 246 | $enabled = apply_filters( 'option_enable_xmlrpc', true ); |
| 247 | } |
| 248 | |
| 249 | /** |
| 250 | * Filters whether XML-RPC methods requiring authentication are enabled. |
| 251 | * |
| 252 | * Contrary to the way it's named, this filter does not control whether XML-RPC is *fully* |
| 253 | * enabled, rather, it only controls whether XML-RPC methods requiring authentication - such |