-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Field does not show correct activation date #306
Comments
So the activation date display the last modified date ? |
Seems like it !! |
The timestamp is updated when the activation field is saved. It looks like a feature, not a bug. What about changing the label by "Last activated" ? |
Hmm. Does not make sense to me. Why should the activation be renewed every time the entry is saved? That would simply mimic the function of the system saved date. It makes a lot more sense to me to only store/save the date of the initial activation, especially since there is no way to deactivate a user again if I get it right. |
Yeah but looking at the code, it is clear to me that it is how it was designed. Now, do we still need this ? We would need to git blame the thing before taking a conscious decision. |
The blame game! I’ll have a look on monday. Not feeling conscious enough anymore today. Thanks for your insights! Good night |
nite nite ! |
Looks like the timestamp came along after I worked on this field, so I can't speak to the original intent. If I had to guess, though, it sounds like a bug. |
Thanks for chiming in Craig, I do feel the same. |
When a user is activated the activation date/time is shown in the field. This does not seem to reflect the actual activation date but is set to whenever the entry its is was last saved.
The text was updated successfully, but these errors were encountered: