Hello,
a user of mine had the problem that emptying the trash simply purged the whole INBOX (w/o subfolders). It occured about three months ago and again now and each time I had to restore the INBOX from a backup.
I can not reproduce the problem in any case, nor can I get an exact description of what he does. He usually uses the latest Firefox, but may be using other browsers at other places so I cannot determine his exact setup in such a case.
Does anybody have an idea?
The setup:
RC 0.1-rc1 on debian etch, Apache2.2.3-4+etch1, PHP 5.2.0-8+etch7
Cheers,
DD
Any errors in the error log?
Quote from: SKaero Any errors in the error log?
Sorry, no.
One idea of mine is that a client doesn't disable the "Empty" Link in the INBOX view for some reason and a click empties the inbox then. Is that possible?
DD
I have had 2 users come to me with this problem. The claim they have done a basic empty trash with the empty link but it also emptied their inbox. I cannot recreate the problem. Using version 0.1-rc1.
Same problem here. A least five users have reported the problem, and I was able to reproduce it once. Perhaps the "Empty" link is enabled before the variable containing the current folder gets changed. If all these actions are done through Javascript, I guess it can happen when the client CPU load is important.
I had the same problem today,
is this issue solved?
maybe the backend can check if the folder to be emptied is named 'INBOX' and abort?
I think this is a show stopper behaviour :(
thank you
Marco
I have the same problem, many users complains to this problem.
I was able to reproduce it only once :( (still trying...)
I'm working on 0.1-rc2 version.
Does anybody have any idea what can be wrong?
mabi: your solution could works :) , but will not fix the real reason :(
maybe add 'empty' function only to trash folder?
I've also had this problem about 5 times using Safari / Firefox. Thank god for backups.
I must say that the IMAP-server I'm using is a bit old and slow, which can explain why the problem is hard to reproduce.
UPDATE: This issue seems to have been fixed http://trac.roundcube.net/ticket/1484449