Ticket #1259 (new bug)
Logging update action on profiles and on preferences, geo setting, emails update
| Reported by: | jeanyves | Owned by: | jeanyves |
|---|---|---|---|
| Priority: | critical | Milestone: | unassigned |
| Component: | BW General | Version: | test |
| Keywords: | logs | Cc: | lupochen fake51 |
| Follow up needed: | test on alpha | Frequently reported: | 1 |
| Announce on BW: | no |
Description
When someone update his profile there is no more logs (MOD_Log) about it.
It is needed to do it (no need to log the data), because if for some reason thee is a bug, or someone stealing a password and updating a profile, or some failed update, or some member contes, or whatever you can imagine, it is very useful to be able to see when the member last updated his profile.
(May be some are already done but I didn't detect the)
The same stands for geo updates, emails update (don't put the email value in logs !)
It is also very important to do it with preferences (and here to log the value before and the value after). This has been very demonstrated to be very useful before when a member though that his preferences for public profile (which was done from the preferences page in old BW) where not working because his profile was indexed by google. We have been able with these log to provide him with exact and reliable explanations
For the typeof log, please use the same value as old BW, this allow for efficient history. If you don't know which one to use, please just ask me.
Any action one the database should in general produce a log (don't overload it however).
Be careful not to store private data in logs.
Always store volunteer actions or even from members which might lead to some contestation
I set it to critical, because I think it hard to keep it mind such detail which you never realize you miss it untill the moment when you are with a problem to try to explain some big problem
