Message1423
Logged In: YES
user_id=6405
Hrm, it looks like a corruption (due to a bug which has been
fixed a while ago) in a user journal.
It'll have to be manually fixed before the export will work. The
simplest way is to delete the journal table entry (or entries)
which contain the invalid password data. To do this:
1. make a copy of the sqlite "db" file beforehand - it's "<tracker
home>/db/db"
2. run sqlite ("sqlite <tracker home>/db/db")
3. delete from user__journal where params like
'%roundup.password.Password%';
|
|
Date |
User |
Action |
Args |
2009-02-03 14:20:54 | admin | link | issue1009701 messages |
2009-02-03 14:20:54 | admin | create | |
|