User:Arlen22/WordPress

Pluggable functions were introduced in WordPress 1.5.1 These functions let you override certain core functions via plugins. The most up-to-date list of core functions that WordPress allows plugins to override is available in. WordPress loads the built-in functions only if they are undefined after all plugins have been loaded.

Note: A function can only be reassigned this way once, so you can’t install two plugins that plug the same function for different reasons. For safety, it is best to always wrap your functions with, otherwise you will produce fatal errors on plugin activation.

Reference

 * get_currentuserinfo : Grabs the information of the current logged in user, if there is one. Essentially a wrapper for get_userdata, but it also stores information in global variables.
 * get_userdata($userid) : Pulls user information for the specified user from the database.
 * get_userdatabylogin($user_login) : Pulls user information for the specified user from the database.
 * wp_mail($to, $subject, $message, $headers = '' ) : A convenient wrapper for PHP's mail function.
 * wp_login($username, $password, $already_md5 = false) : Returns true if the specified username and password correspond to a registered user.
 * auth_redirect : If a user is not logged in, he or she will be redirected to WordPress' login page before being allowed to access content on the page from which this function was called. Upon successfully logging in, the user is sent back to the page in question.
 * wp_redirect($location) : Redirects a browser to the absolute URI specified by the <tt>$location</tt> parameter.
 * <tt> wp_setcookie($username, $password, $already_md5 = false, $home = , $siteurl = ) </tt> : Sets the WordPress cookies for a logged in user. See WordPress Cookies.
 * <tt>wp_clearcookie</tt> : Clears the cookies for a logged in user. See WordPress Cookies.
 * <tt> wp_notify_postauthor($comment_id, $comment_type='') </tt>: Emails the author of the comment's post the content of the comment specified.
 * <tt>wp_notify_moderator($comment_id)</tt> : Informs the administrative email account that the comment specified needs to be moderated. See Administration > Settings > General.

Example
An example of what you can do with a pluggable function is replace the default email handler. To do this, you'd need to write a plugin that defines a <tt>wp_mail</tt> function. The default <tt>wp_mail</tt> function looks like this:

function wp_mail($to, $subject, $message, $headers = '') { if( $headers == '' ) { $headers = "MIME-Version: 1.0\n". "From: ". get_settings('admin_email'). "\n". "Content-Type: text/plain; charset=\"" . get_settings('blog_charset') . "\"\n"; }

return @mail($to, $subject, $message, $headers); }

But, for example, if you wanted to CC all your mail to another address, you could use this code in a plugin:

if(!function_exists('wp_mail')) : function wp_mail($to, $subject, $message, $headers = '') { if( $headers == '' ) { $headers = "MIME-Version: 1.0\n". "From: ". get_settings('admin_email'). "\n". "Cc: dummy@example.com\n"; "Content-Type: text/plain; charset=\"" . get_settings('blog_charset') . "\"\n"; }

return @mail($to, $subject, $message, $headers); } endif;

Notice that if you plug a core function like this the original is no longer available. I.e., the elegant solution here would have been to write a function that tacks our Cc header on the end of the exising <tt>$headers</tt> string then call the original <tt>wp_mail</tt> with the extra header. However this would not work as the original <tt>wp_mail</tt> does not exist if you plug it.