-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
time issue #37
Comments
Post creation time is an UNIX timestamp. The database driver declares it as such: databases/gorm/posts.go#L53 This formatted time is controlled by main.go#L72-L74 What this means is that the time is most likely taken from the Heroku's server time, which seem to be the time of Ireland. If you can confirm that the time difference between you and Ireland is 4 hours, I could take a further look into the bug. |
@9uuso yeah, theres a 5 hour difference |
As far as I know, there is no way to feed the server your current time without using JS. I have to figure if I need to implement a select option to choose your timezone. |
@9uuso well if the select option is the simplest way to do this then I guess that it doesn't sound bad, 👍 |
a timezone select option is probably the best option. just dont forget to On Wed, Jun 24, 2015 at 1:02 PM, My-khael Pierce notifications@github.com
|
branches merged |
I pulled the latest code and deployed it to heroku, I submitted a new post but the time was a little wrong. I posted my post at 6:45 AM but it displays 10:45AM. I don't know if this is set for your time but can you confirm? @9uuso
The text was updated successfully, but these errors were encountered: