If a user goes to a page in toaster from their bookmarks or a link from memory, or in a new browser/different pc and if they haven't selected a project or got a current session toaster will just 500 out on them, we can fix this by sending them to the /projects page for instance.
(In reply to comment #0) > If a user goes to a page in toaster from their bookmarks or a link from > memory, or in a new browser/different pc and if they haven't selected a > project or got a current session toaster will just 500 out on them, we can > fix this by sending them to the /projects page for instance. Though just testing that it seems a bit jarring as you have no idea why you've been dumped into the all projects page. So this need some design thoughts, over to you Belen!
heh, I was about to submit this :) I think we should probably tell users what's going on. If we land them directly on the projects list without anything else, they will not understand why they are brought to a page that is not the one they wanted to go to in the first place. We could either: * Bring them to the all projects page with a notification on top * or we could use something like the landing_not_managed.html template, but with a different message (see attached image). But ideally, in both options, we would remember the page that was originally requested, and bring users directly there when they select a project.
Created attachment 2427 [details] select-project.png
This is probably needed as part of the table refactoring effort that's currently ongoing. Assigning to Michael.
We now use a url schema that contains the current project identifier rather than having this value in the session.
verified on master: 71b0568fa43285f0946fae93fb43cea5f3bbecec