Welcome, visitor! Log in
 

Source View: author_email

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
59  * Care should be taken to protect the email address and assure that email harvesters
60  * do not capture your commentors' email address. Most assume that their email address will
61  * not appear in raw form on the blog. Doing so will enable anyone, including those that
62  * people don't want to get the email address and use it for their own means good and bad.
63  *
64  * @since 0.71
65  * @uses apply_filters() Calls 'author_email' hook on the author email
66  */
67 function comment_author_email() {
68      echo apply_filters('author_email', get_comment_author_email() );
69 }
70
71 /**
72  * comment_author_email_link() - Display the html email link to the author of the current comment
73  *
74  * Care should be taken to protect the email address and assure that email harvesters
75  * do not capture your commentors' email address. Most assume that their email address will
76  * not appear in raw form on the blog. Doing so will enable anyone, including those that
77  * people don't want to get the email address and use it for their own means good and bad.