Quote:
Originally Posted by mtha
It works great.
however, I need more information than that, so I create an other version of this hack, with multipleloginlog table in database (with option to use it), to store (userid,idstack,dateline,ipaddress,proxyip,userage nt,url)
No interface to see the log yet, only store to database, and you can check in the database to see the log.
|
Its good, but analysing this table will not be easy as all the ids are not stored in the userid column. Some of them are in the serialised array only, and that is not indexable.
Also, if a person has more than 2 ids, it is creating multiple records for that person.
I think it would be more fruitful to store one record for each id/cookie combination. Lets say userid 1453 logs in with cookie 78, then the plugin should store 1453 and 78 if such a record does not already exist. Later when the user logs in with id 1782 and the same cookie value, this should be recorded as well.
Now when we have to check if userid 1453 has any alter ego, we just run a query where cookievalue=78.
The advantage of this scheme would be that even shared ids would be tracked.