I think I know what is going on. I am still having trouble. I am logged in as a test user in the Wappler Platform, so when I go and check the Live URL to see the updated changes I am still logged in as that test user. This is why I am able to change to another page without any security obstacles as I am still logged in on the Wappler side even after I click Logout (I tested this theory with the 'Identity' tag).
So I guess my next logical question would be... How do I stay logged out when I hit logout? Because if I simply hit 'Reload Design View' - I am still logged in and can see the member only area again. How do I make this workable so these type of small delays are no more for logging in, logging out, and executing functions as a user / non user.
Only test in the browser and not within Wappler? Or maybe use Incognito Mode or an alternative browser? Personally have never logged in from within Wappler itself... But may explain the weirdness you are experiencing?
This is such an obstacle I am just going to move on, this is delaying my whole project. Hopefully when I launch it will just work since it will no longer be connected Wappler editor once Live I guess.. This is my non-solution for now.
Go for it, not worth spinning around in circles for a possible 'local' only issue! Crack on and come back to it if you need to, we'll all still be here.
I tried to read and understand all the posts in this topic but i am afraid i donât understand whatâs the issue here and whatâs actually going on.
Just wanted to mention that all the testing with login/logout/user details should be done in a browser, not in in Wappler design view⌠and also Wappler design view has nothing to do with the sessions and cookies in your browser, as well as login stuff done in the browser.
