A bit over a week ago I received an email telling me that my AppDb account would soon get deleted due to inactivity. I don't really remember creating an AppDb account but it is possible I did. So I went there to check it out but of course I could not remember my password.
So I typed my email address and clicked on 'Email me a New Password' but got the following error message:
Sorry, that user (fgouget%40free.fr) does not exist.
So I tried my other email address and got the same message. So at this point I see two possibilities:
* I don't have an account on the AppDb. Why did I receive an email saying my AppDb account was inactive then?
* Or there is a bug in the 'Email a New Password' functionality. Maybe it's the '%40' causing the problem?
Either it's a bug in the AppDb code so I thought it would be good to report the problem here.
Right. There was a bug with the cleanup script that performed:
if user is inactive for >=6 months, warn them about inactivity if user is inactive for >=7 months, delete them
You can see the issue with this logic right away. Your account was unfortunately warned and then deleted.
We've fixed this bug and the issue with the login page echoing back the encoded version of your email address is also scheduled to be fixed in the near future.
Chris
On 10/4/05, Francois Gouget fgouget@free.fr wrote:
A bit over a week ago I received an email telling me that my AppDb account would soon get deleted due to inactivity. I don't really remember creating an AppDb account but it is possible I did. So I went there to check it out but of course I could not remember my password.
So I typed my email address and clicked on 'Email me a New Password' but got the following error message:
Sorry, that user (fgouget%40free.fr) does not exist.
So I tried my other email address and got the same message. So at this point I see two possibilities:
- I don't have an account on the AppDb. Why did I receive an email
saying my AppDb account was inactive then?
- Or there is a bug in the 'Email a New Password' functionality. Maybe
it's the '%40' causing the problem?
Either it's a bug in the AppDb code so I thought it would be good to report the problem here.
-- Francois Gouget fgouget@free.fr http://fgouget.free.fr/ tcA thgirypoC muinelliM latigiD eht detaloiv tsuj evah uoY