I’m currently running a beta test on my platform to check for bugs, and things that needs to be fixed.
I’m having an issue that I would like to get help with.
I have our “frontend” which is viewable to non-logged in users only
I have our “backend” which is viewable to logged in users only
The main issue I need to resolve is this, when “logged in users” decide to close their tab, and maybe re enter our website using our main domain, this does not work because it’s only viewable to non-logged in users.
This is causing a little headach, as users are reporting that they are not able to access our homepage. Any thoughts on solution here?
NOTE: I dont want “logged in” users to be able to access our frontend, as it looks quite weird, having a vertical nav bar and scrolling around on our homepage.
The main issue I need to resolve is this, when “logged in users” decide to close their tab, and maybe re enter our website using our main domain, this does not work because frontend is only viewable to non-logged in users.
Here is the recording showing this:
I could alternatively allow all our frontend sites to be viewable to all users, but I dont like the touch and feel of this, as its not very user friendly to view the sites like this:
Typically you could put some CTA on the home page for logged in users to navigate into dashboard area sort of…
Or you could also have website on mydomain[.]com and the app/dashboard on app[.]mydomain[.]com
Or as Davit suggested we could give small script that redirects from home to specific page if the user is logged in - however they will not see the page in any case as logged in user
I tried the script and it worked partially. As I have two dashboard slugs /dashboard-user, as well as /dashboard-manager. They get to any of these dependent on their user access such as “manager” or not. I tried to amend it below; but did not get it to work either:
OK that makes sense. I know the group information is available to custom code, but I don’t have any code for that right now so will have to poke around in the debugger. If anyone else knows how to write that code off the top of their head, please jump in!
Right, but we would not want to copy that logic into the custom code as that would violate “don’t repeat yourself” and set up a future bug where someone changes the logic in the group definition and breaks the custom code in a way that would be hard to diagnose.