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 |
|---|---|
| 979 | * @param string $content Content of the notification email. |
| 980 | * @param string $domain Site domain. |
| 981 | * @param string $path Site path. |
| 982 | * @param string $title Site title. |
| 983 | * @param string $user_login User login name. |
| 984 | * @param string $user_email User email address. |
| 985 | * @param string $key Activation key created in wpmu_signup_blog(). |
| 986 | * @param array $meta Signup meta data. By default, contains the requested privacy setting and lang_id. |
| 987 | */ |
| 988 | apply_filters( |
| 989 | 'wpmu_signup_blog_notification_email', |
| 990 | /* translators: New site notification email. 1: Activation URL, 2: New site URL. */ |
| 991 | __( "To activate your site, please click the following link:\n\n%1\$s\n\nAfter you activate, you will receive *another email* with your login.\n\nAfter you activate, you can visit your site here:\n\n%2\$s" ), |
| 992 | $domain, |
| 993 | $path, |
| 994 | $title, |
| 995 | $user_login, |
| 996 | $user_email, |
| 997 | $key, |