-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
[Bug]: Use system timezone in calculation of share times #42453
Labels
Comments
Likely culprits server/lib/private/Share20/Manager.php Lines 432 to 438 in 7d8741c
and server/lib/private/Share20/Manager.php Lines 508 to 514 in 7d8741c
|
Recommended fix :
|
Defaults to UTC. Europe/Berlin is an example. |
szaimen
added
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
26-feedback
labels
Jan 2, 2024
4 tasks
github-project-automation
bot
moved this from 🏗️ In progress
to ☑️ Done
in 📁 Files team
Jan 15, 2024
nfebe
removed
the
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
label
Jan 31, 2024
Closed
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
A user encountered an issue when attempting to create share links in Nextcloud before 9:00 AM JST (UTC+09:00). After investigation, it appears there is an error in how we calculate share link expiration times, because looking at the code, we always use UTC irrespective of the users timezone.
Steps to reproduce
Expected behavior
Share links should be created without encountering any issues irrespective of the time of day.
Installation method
None
Nextcloud Server version
26
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: