s1de7

for opening the ticket, i was to lazy…

thanks! but altering the clauses may actually be a bad idea because it breaks caching. it doesn’t matter in your case but on frontend the comments query is cached using a unique key based on the query string. if you dynamically alter the clauses and use a persistant cache it returns the same cache for the same query string and possibly different clauses.

i ended up using the comments_array which doesn’t break the cache but is not so ideal performance-wise. would be nice if pre_get_comments would work again as expected…

this one is new since one of the latest dev versions:
add_filter('comments_clauses','qtranxf_excludeUntranslatedPostComments',10,2)
this function doesn’t even exist in earlier versions.

i get a WordPress database error Unknown column 'wp_posts.post_content' in 'where clause' for query SELECT * FROM wp_comments […]
but only on some sites of my multisite network. still investigating.

unfortunately i could not reproduce the error with a clean 2015 – BUT get_comments() still returns an empty array! the 2015 recent comment widget DOES return the comments, but ALL, also for untranslated posts, though.

@john: i am still investigating the database error. i’ll get back to you asap, in the next few hours.

well, the hook would be ‘wpmu_activate_user’ and – of course – i added an action to it with the snippet above. (slightly changed.) i did

NOT EDIT ANY CORE FILES!!

this is absolutely not recommended and i am sorry that i wasn’t clear about this before.

this is the code i used:

function custom_login_new_user( $user_id, $email, $meta ) {
	$user = new WP_User( (int) $user_id );
	$creds = array();
	$creds['user_login'] = $user->user_login;
	$creds['user_password'] = $meta['user_pass'];
	$creds['remember'] = true;
	$user = wp_signon( $creds, false );
	wp_set_current_user($user->ID);
	if ( is_wp_error($user) ) {
		echo $user->get_error_message();
	} else {
		// safe redirect to actually login the user - otherwise they would need to manually refresh the page
		// PLUS: this clears the activation confirmation page with the plain text password printed on screen
		wp_safe_redirect( get_home_url() );
		exit;
	}
}
add_action( 'wpmu_activate_user', 'custom_login_new_user', 10, 3 );

As a workaround, you can edit the plugin and remove the line

* Network: true

You can than activate it individually and it works fine. 🙂