More granularity on user last login Date...

mrdale · 2013-06-26 23:29:48

Month and year just don’t cut it. ;)

springworks · 2013-06-27 07:02:35

Agreed, including the date at the very least would be much more useful.

Pat64 · 2013-06-27 07:27:12

+1

philwareham · 2013-06-27 08:51:45

Agreed. Hope one of the programmy core devs can do this. Maybe open an issue in SVN?

Last edited by philwareham (2013-06-27 09:07:46)

Gocom · 2013-06-27 11:48:13

The last login date only tells you when the user logged in. Not when the user accessed the site. As the session lasts for a month, the last login date isn’t very accurate presentation of when the site was accessed by the user. You can’t tell from when your account was accessed by someone else, or how actively users use the site.

Now, if the date contained the day, what valuable information would that provide to you?

Last edited by Gocom (2013-06-27 11:57:10)

maniqui · 2013-06-27 13:08:33

Nitpick: then, the column may be better renamed to something else than last_access, as it’s currently named. last_login perhaps?

mrdale · 2013-06-27 15:28:45

OK, so I suppose I should be more specific.

Often I would like to have an easy way to tell when the last time a user was accessing the back end. That field is virtually pointless as is.

fiddle · 2014-04-03 20:22:30

I noticed that the last login column really isnt accurate.. Anyone else.?
I know for certain that a specific account was used, but no date shows up..

uli · 2014-04-04 00:51:26

fiddle wrote #280049:

I know for certain that a specific account was used, but no date shows up..

That person didn’t log out then. As a result, there’s no login necessary and no new timestamp created.

Maybe hide the checkbox “Remain logged in” from the login screen? Can’t tell, though, what happens if users don’t log out and quit their browser immediately.

fiddle · 2014-04-04 01:24:10

I did log out..

I created an account for myself just to test, and I log in, do whatever, log out.. Never gets marked with a date, although, this is using smd_user_manager, cbe_members, cbe_frontauth..
Not sure If this might make a difference, but some accounts are logged, others are not..

Last edited by fiddle (2014-04-04 01:26:21)

uli · 2014-04-04 10:16:19

fiddle wrote #280055:

Never gets marked with a date

I.e. you have March in your admin right now, log out, log back in, visit the Users panel and there’s still March? That’d be weird.

You can install one of these dashboard plugins (e.g. smd_tabber) and put a query tag with a nicely formatted date there.
You might also hack the core. I did that once for these dates, it’s not too tough cause I could do it. But it didn’t survive the update and was never re-ordered.

Edit: Umm, wait, you’re not calling for more granularity like the others, you complained about TXP not working as it should, right? Did you try to deactivate the above plugins and test then? Do any of these have their own DB tables and override the system one’s? Then lay a cable from there into your dashboard.

Last edited by uli (2014-04-04 10:21:29)

Bloke · 2014-04-04 10:41:09

fiddle wrote #280055:

some accounts are logged, others are not..

smd_user_manager piggy backs on top of the core tables so shouldn’t affect the outcome here. Are you logging in from the admin side or from the fronrt-end via cbe_*? I presume that the cbe plugins use core functions to log you in and out, which should take care of the last access time. Maybe they don’t…?

Can you check if the last_access column is being updated at all in the txp_users table in the database? If not, any error messages in server logs?

fiddle · 2014-04-04 14:07:11

One account is on thebackend, which is fine, then ihave about 10 accounts in the front through cbe.. Only 2 of the 10 gets loggedat all. That’s why I find it weird, itshould either work, or not at all..
Ill look at the db table when iget a chance.. But like I said, itworks for certain accounts, so it is getting updated,sometimes….
Thanks for the help..

Gocom · 2014-04-04 17:59:07

fiddle wrote #280082:

One account is on thebackend, which is fine, then ihave about 10 accounts in the front through cbe.

That explains it. It’s a plugin provided feature, and thus unrelated to the core functionality. cbe_frontauth versions prior to 0.9.5 just don’t update the date on log in.

Bloke wrote #280066:

I presume that the cbe plugins use core functions to log you in and out, which should take care of the last access time. Maybe they don’t…?

There aren’t really any features for handling logins and session in Textpattern 4.5 and older. Textpattern has just a total of one function for all that, and that one is for validating credentials. For some odd reason that function also updates last-access time on successful validation: old-school slap-on code in other words.

Rest of the old codebase is useless outside admin-side and actually leads to security vulnerabilities if run elsewhere by plugins. The private login cookie for example itself becomes domain-wide.

I personally wouldn’t recommend using Textpattern 4.5 session functions otherwise either for anything actually mission critical (i.e. as a login backend). The public login cookie is 10 bytes long substring of md5 hash, for example (note: the private cookie and admin-side login system is unrelated and fine).

towndock · 2016-07-16 13:31:03

Was a solution ever found for this?

Textpattern CMS

Textpattern CMS support forum

#1 2013-06-26 23:29:48