Max Chirkov

Thanks Nono. I will include that into the next update.

Thank you very much! Your translation will be included in v.1.0.1

Hi Dan,

I realized that my logic for displaying results in the back-end was flawed – it was, in fact, querying all records multiple times. BUT – that was not happening on the login page – just on the Users/Login Log admin page.

There is only 1 instance of a request that gets ALL results – it’s the export ALL function.

v.1.0.1 will have the SQL queries fixed.

That sounds weird… such data is automatically logged in within apache access logs on pretty much every single web site. I guess it may have to do with actually identifying a live person and linking log data to him/her.

I’m considering adding a settings page where admin would be able to choose which data to log, but this will probably be a commercial version (speaking of donations ;)).

That is a very unique use case. I don’t think this deserves to be a feature of its own, unless more people request it.

Hi Alan,

what’s the minimum amount of information they would want to see in the front-end?

Hi Alan,

what’s the minimum amount of information they would want to see in the front-end?

Will be added in version 1.0.1. Thanks!

Hi Jack,

currently no – there is no way to do that. You can run a direct SQL query on your DB for each user that is in users table but doesn’t exist in the simple login log table.

Hi Andre,

contact me via this form https://simplerealtytheme.com/support/ and I’ll reply to you with my email address where you can send the MO file.

Thank you for your contribution!

Will get that fixed. Thanks!

Thanks for the suggestion. I need to think about it. The issue with logged in duration is that it can’t be recorded for users that don’t manually log out. I personally never log out from my WP sites on my own machines – I just let the cookie to expire. So, this option would be totally irrelevant to me.

By the way, when user logs in – there is an option on the login form called “Remember Me” – if user checks it, WP will remember the user for 14 days, otherwise the user will be remembered for 2 days. In any case, if user doesn’t log out, then he/she will be logged in for at least 2 days, which doesn’t represent the real duration of their stay.

There is a setting under the main General Settings section that allows you to truncate data after specified number of days.

Last login ONLY would not be as useful for many users, I would not be interested in implementing it. But again – the truncation option should fix the issue with rapidly growing database.

Hi Dan,

I looked into the issue you described and can not see it happening on my end.

The only place where it’s grabbing all data is on table schema update. Yea, I agree – it shouldn’t be doing that and I will make a change, but if you successfully updated, it shouldn’t do it on every wp-login.php load. It doesn’t do it on m machine. Could you please update to the most current version and double-check for me?

Thanks

Hi Dan,

sorry – no I never seen your post. I’ll look into the issue ASAP. Thanks for your persistence, I really appreciate pointing this out.