URL navigation bug; some groups persisting or viewable on page load

Questions
1

SPA…I followed a tutorial by Cranford Tech for url navigation using option sets. It seems to work like it should, but routinely, the map view (group) of my app will be viewable on page load…url will read index/map, when the map view is set to not be viewable on page load and to collapse when hidden. The map view will be stacked under the view that’s supposed to be viewable on page load (login view). Also, even if it does load correctly and only shows the login view…you login and it goes straight to map view as it should, but when you navigate to a different view, like group contacts view, the map view will persist along with the other selected view. BUT if you switch back and forth between different views…back to map, then to contacts or whatnot…it corrects its self and the issue doesn’t pop up again.

I have three paths to make the map view visible. When button login is clicked, make map view visible. When someone creates an account and clicks the submit button, make map view visible. And then I use page url navigation for the actual menu navigation button. It seems that all three paths work as they should and shouldn’t interfere with each other. Do I need to set up send data to page url for the other two buttons? It’s the only possibility that I can think of that could be causing the issue. Anybod

Screenshot_20241207_172802-4
Screenshot_20241207_172802-4841×498 239 KB

y experience this? Thoughts?`` text

2

Figured it out. So, although the buttons that I had the workflow of, among several other workflows…Element actions, show element, element: Map view, weren’t actively running, they were still interfering with the url navigation to the map in other sections of the app. The solution was to replace the “show element” workflow, with navigate to page, send data to page for url navigation. Guess it shows the importance of being consistent in the method of navigation throughout your app.