Skip to content
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

Remove timezone configuration for brisbane #24

Closed
atruskie opened this issue Dec 4, 2013 · 4 comments
Closed

Remove timezone configuration for brisbane #24

atruskie opened this issue Dec 4, 2013 · 4 comments

Comments

@atruskie
Copy link
Member

atruskie commented Dec 4, 2013

Assigning the default timezone to the site as Brisbane (10+) as in (e2435cb)[https://github.com/QutBioacoustics/baw-server/blob/e2435cbe76e0088601fa202cab5ab9abb6c7b75d/config/application.rb#L38] is terrible practice.

It was done to meet time constraints and so that old legacy problems were not a problem.

Removing this assumption will affect #22 and #23

@cofiem
Copy link
Contributor

cofiem commented Dec 6, 2013

A user should also be able to set the locale (for dates / times and translations) for their personal profiles.

@cofiem
Copy link
Contributor

cofiem commented May 6, 2015

Based on tests done while adding site and user time zone settings ( #121 ), removing this setting will not affect accessing audio files.

@atruskie
Copy link
Member Author

atruskie commented May 6, 2015

Good it won't affect.

Still think this setting should removed/set to UTC anyway as it should now be redundant?

@cofiem
Copy link
Contributor

cofiem commented May 6, 2015

set to UTC, yes. So, that will be 'server time', users will see things in the time zone they set.

atruskie added a commit that referenced this issue Jul 27, 2020
atruskie added a commit that referenced this issue Jul 27, 2020
atruskie added a commit that referenced this issue Jul 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants