Thanks Mikong, I think the problem is that when a task is saved to the database, completed_on gets set to Time.now
Going into console and typing Time.now gives: Tue Dec 23 10:05:00 -0800 2008 I think this is where the problem lies (the auto updated_at and created_at timestamps must get round this somehow) ... any ideas? cheers, DAZ On Dec 23, 4:36 pm, mikong <[email protected]> wrote: > Handling time zones ever since Rails 2.1 should be invisible to the > developer. You might want to check out > > http://railscasts.com/episodes/106-time-zones-in-rails-2-1 > > I tested your case in a recently generated app in Heroku (default > config.time_zone in environment.rb is 'UTC'). I've generated a User > scaffold (the migration had timestamps by default). I created a user. > Even if I use distance_of_time_in_words(@user.created_at), the > displayed time is correct (1 minute ago, 7 minutes ago, and so on). > Even after changing the time zone in environment.rb to 'Fiji', it's > still displayed correctly. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
