Rishi S
Rishi S
TTwenty
Created by Rishi S on 9/13/2024 in #❓︱help
Webapp gets blank after an hour of idle session
Steps to Reproduce: - Log in to the application with a valid user account. - Leave the session idle for a while until the authentication token expires. - Attempt to navigate or interact with the application after the token expiration. - Observe the screen after the token has expired. Description: - After a period of inactivity, when the session token expires, the user is not redirected to the login page. Instead, a blank white screen appears, leaving the user stuck without any indication of the issue or the next steps. This disrupts the user experience and forces users to manually refresh or re-enter the URL, instead of being redirected to the login page to re-authenticate.
10 replies
TTwenty
Created by Rishi S on 9/13/2024 in #❓︱help
Webapp gets blank after an hour of idle session
Hey @charles, thanks for looking into this, I'll share the steps to reproduce locally anytime soon 🙂 .
10 replies
TTwenty
Created by Rishi S on 9/13/2024 in #❓︱help
Webapp gets blank after an hour of idle session
In order to get it running again, we've to clear the browser cookies. After that, it functioning well.
10 replies
TTwenty
Created by Rishi S on 9/13/2024 in #❓︱help
Webapp gets blank after an hour of idle session
The server is host in EC2 on Docker.
10 replies
TTwenty
Created by Bhavin on 9/10/2024 in #❓︱help
How to backup existing DB data to latest twenty version ?
I've DMed you @charles, if you can help that would be really helpful.
9 replies
TTwenty
Created by Bhavin on 9/10/2024 in #❓︱help
How to backup existing DB data to latest twenty version ?
Hey @charles the guide you've shared is about migrating from 0.21* to the next version: v0.21.0 to v0.22.0 v0.22.0 to v0.23.0 v0.23.0 to v0.24.0 https://twenty.com/developers/section/self-hosting/upgrade-guide But here we've a special case, we were on 0.3.3 (with user's data in DB) and we've merged the latest changes of 0.23 (so we're on 0.23). As there are lots of schema changes, we need to just sync the latest schema from merged 0.23 codebase. In that case, we need to go with the same steps mentioned in the upgrade-guide? yarn database:migrate:prod yarn command:prod upgrade-0.24 We tried both and getting errors. Just wanted to confirm that can we retain data if we migrate from 0.3.3. to 0.23 at one go?? Seeking your help and we appreciate your prompt reply.
9 replies