Source View: check_is_user_spammed

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
132
133 /**
134  * For multisite blogs, check if the authenticated user has been marked as a
135  * spammer, or if the user's primary blog has been marked as spam.
136  *
137  * @since 3.7.0
138  */
139 function wp_authenticate_spam_check( $user ) {
140      if ( $user && is_a( $user, 'WP_User' ) && is_multisite() ) {
141           $spammed = apply_filters( 'check_is_user_spammed', is_user_spammy(), $user );
142
143           if ( $spammed )
144                return new WP_Error( 'spammer_account', __( '<strong>ERROR</strong>: Your account has been marked as a spammer.' ) );
145      }
146      return $user;
147 }
148
149 /**
150  * Number of posts user has written.