Forums

Discuss all things Remember The Milk.

menu

707 error caused by Remember The Milk for Gmail?

toyobay says:
I'm using Windows XP SP3, Firefox3.5.5, and Remember The Milk for Gmail 1.0.4(Firefox extension).
From a few days ago, Gmail error 707 occurs very frequently.

I've tried many ways to solve this trouble, and I found that when I invalidate Remember The Milk for Gmail 1.0.4, the error doesn't occur.
Is this right?
Posted at 10:10am on December 4, 2009
steve23606 says:
Same here.

In fact I came onto the forum to see if anyone else was having the problem.
Posted 15 years ago
jr78 says:
Same problem here, using FF 3.5.5 as well as 3.6 Beta4 on OS X 10.6.

Here they describe the same problem - but no satisfying solution. :(

http://mail.google.com/support/bin/static.py?page=known_issues.cs

Please, RTM Team, are you aware of the problem and working on it?

Thanks for you efforts in this great plugin - my favourite way of entering tasks!!!

Cheers,
Jochen
Posted 15 years ago
geoff.emerson says:
I have the same issue on 3 machines.
My home PC and laptop at work (both XP) and also on a Linux netbook.
I tried clearing cookies and cache but that didn't fix it. the only way I was able to send email from gmail was by disabling the extension. Which is a pity. Will there be a fix?
Posted 15 years ago
arvinda01 says:
Yeah, I'm having the same problem and have had to disable RTM add-in for the moment :(

Is this problem being looked into by RTM? The add-in is amazing and I'd hate to lose it! Thanks.
Posted 15 years ago
jr78 says:
Hi all ... somehow since yesterday everything is working again like a charm. :) Don't know who fixed something - Google or RTM?!

In any case - I'm happy again! :) Thanks!
Posted 15 years ago
jon.bell says:
no fix here....OS X 10.6 ....nothing by 'Oops 707' errors from gmail that go away when the RTM extension is disabled.
Posted 15 years ago
(closed account) says:
still broke - firefox 3.5.5 on win xp, need to disable RTM to make the 707 error go away. Only found out it was error 707 when I disabled offline mode; with offline mode enabled, I was just getting "oops an error has occurred...". gmail worked fine in chrome, obviously with no RTM running.
Posted 15 years ago
murdo.munro says:
I still have this problem.

However, interestingly it does not cause a problem on my business GMail for Domains account, only my personal GMail account.

Set up / versions as per Toyobay.
Posted 15 years ago
dan.quigan says:
I am also experiencing this issue. Windows XP Sp2, Firefox 3.5.5. It manifests itself in other ways too - links stop working, eg unable to click the "display images below" in an email containing images, where the link stops working.

Posted 15 years ago
paul.barrett says:
I was having this same issue, only disabling RTM for Gmail 1.0.4 got rid of the errors.

Good luck fixing it!
Posted 15 years ago
steve23606 says:
Did appear to be fixed but has started doing it again today.
Posted 15 years ago
turkeyphant says:
Any new version planned to fix this?
Posted 15 years ago
jr78 says:
Hmmm ... strange - since right now the errors occur again...

Maybe it has something to do with browser resizing due to an screen resolution change (had my macbook connected to a beamer) ... nothing else changed - even no reboot since 2 weeks.
Posted 15 years ago
dan.quigan says:
This is mentioned on Google's page now.

http://mail.google.com/support/bin/static.py?page=known_issues.cs


'Oops 707' on using Gmail in Firefox 3.5
Firefox users with the Remember the Milk extension installed may encounter 'Oops 707' errors on common inbox actions. To resolve the problem, you can disable the extension or use another browser.
Posted 15 years ago
geoff.emerson says:
Seems to be working for me now. I have been upgraded to FF 3.5.6 on Linux Mint. Have to say above response is a wee bit disappointing. Great extension otherwise. I tried the Labs version but it has less features and shows less tasks (those scheduled more than a week away are not shown).
Posted 14 years ago
andrewski (Remember The Milk) says:
Sorry I didn't post it here earlier: we addressed this on our status blog last month. Summary: we fixed it, but also keep in mind we only support the extension in US English.
Posted 14 years ago
This topic has now been closed automatically due to a lack of responses in the past 90 days.