Postpone tasks, but when I refresh they still show up on today's list
So it is nearing the end of the day and my expectations of getting all these things done is apparently unrealistic. I have four tasks that I just postponed until tomorrow. Everything looks great, no tasks left to do today. But when I refresh the browser those 4 tasks keep on showing up in today's tab. So I postponed them again and tried the whole thing over, same problem. I switched from Firefox to Safari, still the same issue, I just tried to postpone them yet again. I have seen this on occasion, but I thought it was something goofy with having my list open on two different machines or maybe the iphone and my laptop, but it appears to go deeper than that. All that being said, all I can think of is that it might be a bug? Anyone seeing this? BTW, I checked the timezones, my computer and my settings match, so it wasn't that issue.
Thanks!
Thanks!
andrewski (Remember The Milk) says:
Gears may cause problems like you're seeing if you have it enabled in both browsers. Can you try disabling it? You can do so on the Tools menu under Gears Settings; simply set "http://www.rememberthemilk.com" to "Denied". You may need to reload the RTM site after this to make the change.
Let me know what you find!
Let me know what you find!
Thank you for the reply. My intent of using Safari was to eliminate the possibility of Google Gears, but alas I see that there is a version of Google Gears for Webkit, so that wasn't the smartest idea.
I did check however and found that Google Gears is not compatible with Firefox 3.5.5 that I am using, therefore it was deactivated. I also checked on my Safari install and I do not appear to have the Google Gears plugin installed there either, as there is no entry for it under /Library/Plug-ins.
I did check however and found that Google Gears is not compatible with Firefox 3.5.5 that I am using, therefore it was deactivated. I also checked on my Safari install and I do not appear to have the Google Gears plugin installed there either, as there is no entry for it under /Library/Plug-ins.
andrewski (Remember The Milk) says:
I'd also suggest clearing your cache in both browsers to make sure RTM isn't working with outdated data. (This isn't usually necessary outside of interactions with Gears, but could be a problem.)
Also, a proxy on your network could affect RTM's performance. Is that possible on your network?
It'd be helpful to try the secure site, available at https://www.rememberthemilk.com/.
Also, do you use any other services that synchronize? Anything else on your computer, the iPhone or Android apps, MilkSync, etc.?
Also, a proxy on your network could affect RTM's performance. Is that possible on your network?
It'd be helpful to try the secure site, available at https://www.rememberthemilk.com/.
Also, do you use any other services that synchronize? Anything else on your computer, the iPhone or Android apps, MilkSync, etc.?
I still have the same problem.
I have cleared the cache, it seems to make no change.
No proxy on my network, transparent or otherwise.
I almost always use the SSL version or RTM, which of course means it would not cache the data on the machine. I only use Firefox, Safari, and Chrome and therefore SSL data is not cached (like it is on IE). I do use two different machines, a laptop and a desktop. I shutdown the browser on one of the computers, but I still have the same issue of some tasks that will not postpone.
I was using Google Calendar and syncing with RTM, but I have disabled that and am still having the problem days later. I also use the iPhone app for RTM, but I see the same thing there.
Today I have two events I keep trying to postpone and they will not. I probably postponed 15 events today since I didn't get them done today. I refreshed and I have 5 that are now overdue, so I postponed them, still have 5 overdue when I refresh. I kept on trying, I now have 2 that keep on showing overdue.
I don't know why it is doing this, it is very confusing. I generally have 20 or so "to do" items on roughly 18 different task lists. Not sure that matters, but just want to make sure I tell you everything so that you might be able to recreate the problem on your own.
Thanks for working on this with me. I love and rely on RTM, just so you know.
I have cleared the cache, it seems to make no change.
No proxy on my network, transparent or otherwise.
I almost always use the SSL version or RTM, which of course means it would not cache the data on the machine. I only use Firefox, Safari, and Chrome and therefore SSL data is not cached (like it is on IE). I do use two different machines, a laptop and a desktop. I shutdown the browser on one of the computers, but I still have the same issue of some tasks that will not postpone.
I was using Google Calendar and syncing with RTM, but I have disabled that and am still having the problem days later. I also use the iPhone app for RTM, but I see the same thing there.
Today I have two events I keep trying to postpone and they will not. I probably postponed 15 events today since I didn't get them done today. I refreshed and I have 5 that are now overdue, so I postponed them, still have 5 overdue when I refresh. I kept on trying, I now have 2 that keep on showing overdue.
I don't know why it is doing this, it is very confusing. I generally have 20 or so "to do" items on roughly 18 different task lists. Not sure that matters, but just want to make sure I tell you everything so that you might be able to recreate the problem on your own.
Thanks for working on this with me. I love and rely on RTM, just so you know.
andrewski (Remember The Milk) says:
I know you already covered this, but what are your timezones set to? I'm curious about the locations as well as the hours offset for the site, your computer, and your iPhone.
andrewski (Remember The Milk) says:
Are you traveling across timezones? If so, that could cause problems with the dates. RTM doesn't currently support shifting timezones; when a due date is set in one timezone, the task will be due at the start of that day (i.e., midnight) in that timezone. So when you cross timezones, and then postpone a task, it's offsetting it, but perhaps unexpectedly.
If that's the case, can you try to postpone a test task while on EST?
If that's the case, can you try to postpone a test task while on EST?
I generally postpone all my tasks at the end of the day, and when that is done I am in a fixed timezone.
I do think you may have touched on something though. If I:
1. created a new task that is due today while in California (GMT -8)
2. then came home to the East Coast (GMT -5) on the same day and later at 15 minutes past midnight (GMT -5) postponed the task
Would it:
A. postpone the task to today, because it would detect the due date to be yesterday relative to my current location (because today in GMT -8 is really yesterday)
B. postpone the task to tomorrow (because it is already today and postponing it would be +1 day, which is tomorrow)
C. do something else?
All that being said, is there any way for me (the user) to view any metadata about when a particular event was created and at what time and in what time zone? Because if so, I could test this theory the next time I can replicate this problem to see if the suspect events that will not postpone were created in a different time zone (which is quite possible, because I do travel across time zones)
I would think that my RTM account settings which specify GMT -5 would cause all of my events to be created in GMT -5 time zone regardless of my true geolocation (which for instance the iphone may know, but the RTM app wouldn't care about because its time settings are static). Therefore if I were to do event postponing at any time it would always be relative to the EST timezone (GMT -5).
And if I am postponing events over and over and they are still not postponing, then that to me doesn't seem to fit with the problem I am seeing. Because I would expect that postponing an event 5 times would send it into next week vice stay as overdue.
I suppose I could get rid of this problem by being more efficient or realistic with my tasks :)
I do think you may have touched on something though. If I:
1. created a new task that is due today while in California (GMT -8)
2. then came home to the East Coast (GMT -5) on the same day and later at 15 minutes past midnight (GMT -5) postponed the task
Would it:
A. postpone the task to today, because it would detect the due date to be yesterday relative to my current location (because today in GMT -8 is really yesterday)
B. postpone the task to tomorrow (because it is already today and postponing it would be +1 day, which is tomorrow)
C. do something else?
All that being said, is there any way for me (the user) to view any metadata about when a particular event was created and at what time and in what time zone? Because if so, I could test this theory the next time I can replicate this problem to see if the suspect events that will not postpone were created in a different time zone (which is quite possible, because I do travel across time zones)
I would think that my RTM account settings which specify GMT -5 would cause all of my events to be created in GMT -5 time zone regardless of my true geolocation (which for instance the iphone may know, but the RTM app wouldn't care about because its time settings are static). Therefore if I were to do event postponing at any time it would always be relative to the EST timezone (GMT -5).
And if I am postponing events over and over and they are still not postponing, then that to me doesn't seem to fit with the problem I am seeing. Because I would expect that postponing an event 5 times would send it into next week vice stay as overdue.
I suppose I could get rid of this problem by being more efficient or realistic with my tasks :)
andrewski (Remember The Milk) says:
There's no way to view the metadata; shifting timezones isn't something RTM is currently designed to support.
It's hard to say exactly what will happen (depending on where you add the task, which timezone is set on the computer if added there, etc.) but it will very likely not work correctly. :)
A simpler scenario: do you experience this problem on a test task while in a fixed time zone? If you create it and postpone it, it should work correctly immediately; if that doesn't work, then something else may be afoot.
It's hard to say exactly what will happen (depending on where you add the task, which timezone is set on the computer if added there, etc.) but it will very likely not work correctly. :)
A simpler scenario: do you experience this problem on a test task while in a fixed time zone? If you create it and postpone it, it should work correctly immediately; if that doesn't work, then something else may be afoot.
biancolo says:
Just wanted to chime in on this thread, as I have a similar problem, but without any timezone shifting (timezone is EST). I also don't have Gears installed, and I tried clearing my cache. I don't do any synchronization with other devices. I have tried the https version. Here's the behavior:
I have a task that shows up as due two days ago (Dec 17). I hit "p" twice (once to make it due "today" and again to make it due tomorrow). I then switch from my Inbox to some other page, then go back to my Inbox, and the task is listed as Dec 17 again.
Thanks!
Jim
P.S. I wish I could subscribe to threads, either via e-mail or RSS.
I have a task that shows up as due two days ago (Dec 17). I hit "p" twice (once to make it due "today" and again to make it due tomorrow). I then switch from my Inbox to some other page, then go back to my Inbox, and the task is listed as Dec 17 again.
Thanks!
Jim
P.S. I wish I could subscribe to threads, either via e-mail or RSS.
I have the same problem, and it only seems to happen AFTER 4pm PST. Aka when it is after 00:00 in GMT.
And it ONLY happens if I use POSTPONE. if i manually set the due date, thinks work just fine.
i think the postpone logic is calculating things relative to GMT instead of the localtime
And it ONLY happens if I use POSTPONE. if i manually set the due date, thinks work just fine.
i think the postpone logic is calculating things relative to GMT instead of the localtime
Update: check you timezone in you settings on your RTM account (not your computer's timezone). I only had the problem in the afternoon, when it was after 00:00 UTC.
I checked my settings and my timezone was set to 'not specified'. I changed it to PST and noe postpone works again.
BTW - i had to turn on firebug to see this,and then i saw all sorts of other scary personal data being sent back in rtm.rtm?ac=lists.load like my address, lat long and such. Where are you getting that data from ???
I checked my settings and my timezone was set to 'not specified'. I changed it to PST and noe postpone works again.
BTW - i had to turn on firebug to see this,and then i saw all sorts of other scary personal data being sent back in rtm.rtm?ac=lists.load like my address, lat long and such. Where are you getting that data from ???
yang says:
I have the same problem, all the time. I've been having this problem for (I'm guessing) at least a year now. I've all but stopped using the postpone feature, instead always specifying due tomorrow. (If it makes any difference, I always use the keyboard; I don't use a mouse.)
yang says:
Also, FWIW, I've seen this across several different browsers -- Chrome, Opera, and Firefox.