Having problems with memengo.com timing out and not saving changes.
id is "moc.liamg|sehcrakt#moc.liamg|sehcrakt"
—tom
A web browser only allows so much computation to happen before it decides that something is wrong, and then it pops dialog telling you that script takes too long to run. We have to do lots of computations in order to do encryption and the more data you have the more computations we do. This never becomes a problem for people who only store passwords and other small string of text, but some people decide to store large texts and then this problem appears.
You should be able to finish the decryption process by clicking "Yes" on that prompt and letting it continue.
To prevent this dialog from popping up there are few options:
- Split your wallet into two different wallets to reduce the load. One way to do it via web site, using copy&paste. The other way to do it is use iPhone application to move cards or folders from one wallet to another.
- If using Internet Explorer, change the Internet Explorer timeout setting. Be very careful to follow instructions exactly. Instructions: http://support.microsoft.com/kb/175500
- It may help to stop using Internet Explorer and change the browser to Firefox or Safari.
I have reduced the size of the cards in my wallet to allow for faster saving of individual cards.
It appears that the problem is related to editing/saving cards on non-Windows platforms. Editing/saving on anything but a Windows PC works sometimes, but not others. When saving, the process hangs. If I watch the CPU activity during the attempted save, it does not increase, which would lead me to believe that this problem is not a function of the cards being too big.
Non-Windows platforms I have tried this on are Mac OS X 10.4 and Open Suse 10.3.
My workaround is to edit my cards on my Windows box, but it would be nice if I could do it anywhere.
Can you clarify which browsers do you use in each case?
Also, we had problems with our host on Thursday (which I realized only after answering your original post) so it could have been the reason, too. Could you confirm there is still a problem?
FWIW we test our site with these browsers:
- Safari 3.2 / Mac OS
- Firefox 3 / Mac OS
- Firefox 3 / Windows XP
- Internet Explorer 6 / Windows XP
- Internet Explorer 7 / Windows 2008