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

24 hours filter does not take into account the user's timezone #3283

Open
AkashRajpurohit opened this issue Mar 2, 2025 · 3 comments
Open

Comments

@AkashRajpurohit
Copy link
Contributor

AkashRajpurohit commented Mar 2, 2025

Describe the Bug

Image Image

Current time is 10AM, so last 24 hours should return data according to that, but instead it returns data as per the UTC time I believe and not the user's set timezone.

Database

PostgreSQL

Relevant log output

Which Umami version are you using? (if relevant)

2.16.1

Which browser are you using? (if relevant)

LibreWolf

How are you deploying your application? (if relevant)

Docker

@mikecao
Copy link
Collaborator

mikecao commented Mar 2, 2025

What timezone are you using?

@AkashRajpurohit
Copy link
Contributor Author

Asia/Kolkata

@AkashRajpurohit
Copy link
Contributor Author

This issue is only for LibreWolf browser and works fine on other browsers.
But I have a QQ on this now, we allow user to set a timezone but only store it in the local storage, does it not pick this value before making the get request for fetching data, I feel the issue here is because Librewolf masks some of the user specific information like device and possibly timezone and hence this behaviour, we can maybe store these user config (theme, default date range and timezone in the db itself), thoughts @mikecao ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants