After my last signing-in, which was yesterday, I closed the backend and frontend servers. I think the database server has been running on my laptop forever.
The frontend end, at this state of this commit (dc925521ee24ecb177d0f75a136753bcae552f26), has been programmed to check if the authenticated variable is true or false for the current user. When the user logs in, he will be authenticated, and if he logs out, he will become unauthenticated.
In the backend, it has been programmed that the user after the correct login, will be given an hour, then he will be logged out automatically. But this is not happening as expected, actually, the user after one hour will be unable to add more tasks, so is just stuck on the tasks page.
i think the problem is not in backend, because when the backend is not adding any tasks, or no actions will be executed, means that the backend knows that the one hour has left, so the problem is in frontend, he is not redirecing to the home page after the time expire.
After my last signing-in, which was yesterday, I closed the backend and frontend servers. I think the database server has been running on my laptop forever.
The frontend end, at this state of this commit (dc925521ee24ecb177d0f75a136753bcae552f26), has been programmed to check if the authenticated variable is true or false for the current user. When the user logs in, he will be authenticated, and if he logs out, he will become unauthenticated. In the backend, it has been programmed that the user after the correct login, will be given an hour, then he will be logged out automatically. But this is not happening as expected, actually, the user after one hour will be unable to add more tasks, so is just stuck on the tasks page.
i think the problem is not in backend, because when the backend is not adding any tasks, or no actions will be executed, means that the backend knows that the one hour has left, so the problem is in frontend, he is not redirecing to the home page after the time expire.