Plugin Author
anmari
(@anmari)
Hi – it’s more like a historical anomaly. Rather use the field ‘Registered days ago’ – that is actually the real ‘user registered date’, but formatted as days since registration (also shows the actual date when one hovers over the field). This was the original need. CSV should also show the actual date I think.
The field ‘registered date’ is kinda a copy of the real field that some folks asked for because they wanted to show the date directly. This is possibly why it is misbehaving.
The plan in the long run is to offer a choice of date/time format rather and collapse the two fields back into 1.
Thanks! The sorting is now working. Now my only issue appears to be the actual displayed date. I have my timezone set to Vancouver in WordPress, but the registered date doesn’t appear to be obeying that. Do you know what this issue is as well?
As an example, one of my users says the registration date was at 2017-01-10 04:21:08. I can also confirm this in the DB. In actuality, they were registered at about 2017-01-09 20:21:08 PST. The time is now 2017-01-10 16:38:12 PST, but the registration days ago value still says 16 minutes ago. It looks like the days ago code is ignoring the timezone and also the hour and is reading it date off of the minutes in the time only.
Plugin Author
anmari
(@anmari)
Aahh, now you really have found something.
Wordpress is saving registered date in UTC time (as it does with post dates etc for good reasons). So when we display these dates we should be converting to the websites current timezone, not just grabbing from the DB.
Note made and hopefully I’ll be able to roll a fix into an update soon.
Thanks for flagging.
Thanks! I look forward to a fix being released.
