Metadata using wrong Timestamp / Timezone
Open
Nobody has claimed this yet.
0. Needs triage
bug
- Dominant language
- JavaScript
- Stars
- 214
- Forks
- 52
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 82
Description
Steps to reproduce
- Relativly fresh Install of Nextcloud (occouring in all of our instances)
- Install Tables App
- Create new Table
- Add new View with all Metadata
- See that the last edited timestamp ist made 2 hours in the past (wrong Timezone, my Timzone: UTC +2)
Expected behavior
The Table schould create Timestamps based on the Nextcloud Server-Time, found in the Nextcloud-Admin-Settings --> System --> Systemtime
Actual behavior
The Timestamp created does not match the Servertime
Tables app version
0.9.5
Browser
Edge 139
Client operating system
No response
Operating system
Kubernetes
Web server
Nginx
PHP engine version
PHP 8.3
Database
PostgreSQL
Additional info
Nextcloud-Version: 30.0.8
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the timestamp mismatch in a fresh Nextcloud installation with the Tables app, using the metadata view and comparing it with the server time shown in Nextcloud Admin Settings. Trace where the last-edited timestamp is created and verify that the result matches the configured server timezone, including the PostgreSQL setup described here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, postgresql
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100