The Login Logger WordPress plugin sounds a great idea and it works fine with standard situations. However, go beyond these and things start to go awry. An example is where you have to use unique database table prefixes because you use shared hosting. This is certainly something that I do and it breaks Login Logger. Thankfully, the fix for this is easy enough: just amend the database query on line 22 in the manage.php file as follows:
Before:
$query = “SELECT distinct wp_users.user_login,”.$table_name.”.username FROM wp_users LEFT OUTER JOIN “.$table_name.” ON wp_users.user_login = “.$table_name.”.username WHERE “.$table_name.”.username IS NULL”;
After:
$query = “SELECT distinct ” . $table_prefix . “users.user_login,”.$table_name.”.username FROM ” . $table_prefix . “users LEFT OUTER JOIN “.$table_name.” ON ” . $table_prefix . “users.user_login = “.$table_name.”.username WHERE “.$table_name.”.username IS NULL”;
The issue was caused by hard-coding of the table prefix for the user table and using the prefix that you yourself have set is the way out of this. What is less easy to resolve is a conflict between Login Logger and the Themed Login plugin. That will take further investigation before I come up with a fix.