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