Hi!
I have a floating group at the top of my page with a hamburger menu, logo, etc. It loads fine, menu works, etc, but if I refresh the page, both live and dev, or if I close the browser on my phone (PWA), the floating group does’t display.
The core functionality of the page still works, which is primarily a search function. The user must close the session and log back for the floating group to be visible and to use the menu.
Not sure if it’s an auth persistence problem, A side affect of conditionals, or something else that I’m not seeing.
It’s a private app with propriatary info that doesn’t belong to me, so I can’t share a link, but will share as many screenshots as needed. First parent is Index.
Thanks!
2 Likes
Try combining the two conditions into one.
“Group login view is visible and/or group admin create user view is visible”
You can also create a Page is loaded > Show FloatingGroup Nav event.
Thank you for the reply! So, I did as you suggested with the conditions, and it worked as far as the persistence issue, but it is now visible in the login view, even if I refresh the page.
I’m not sure what you mean by your “page is loaded” suggestion, that is; are you assuming that each “view” is a separate page?
I have this set up as a SPA, with all groups (views) conditionally visible through URL parameters utilizing an option set. All groups are a direct child of Index.
If all else fails, I can put the two views that shouldn’t have the floating nav into separate pages, as the transition performance/ load times aren’t as critical.
1 Like
ok, now add a condition to the event so that it only happens when the user is logged in.
That makes sense. Will have to work on this another time. Gotta go do life. Will reply back when I get to it. Thanks again for the help!
1 Like
Went in circles but finally fixed it. The “When user is logged in” solution ran into problems unassumingly due to browser caching the session/ login, so the navbar was visible on the login page. Serious security issue.
With many tests I had 3 conditions; no nav at all, nav on all views, or nav correctly showing, but disappearing on page refresh.
Since all views are shown through URL parameters except for the login which is visible on page load, I tried “Show floating group Nav when, get data from page URL (path segmented as list, type option set, Navigation), :first item is not empty.
DIdn’t work at all even when combined with element-level conditionals either matching with a similar expression or a direct visibility expression.
What did work; Checked if the URL parameter existed at all, and in that case the nav is visible and persistent on all views using URL navigation.
This fixed the number one friction point in the app.
Hope that this helps someone else having these issues.
Thanks again for your help!
