You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If user creates a map and then wants to save it, but they have not logged in or created a MyGLOS account, they then are taken back to the default catalog page. In other words, they have now lost the map they just were working on creating. Suggest expected behavior to be that they get put back exactly where they were. [I know this because for some reason myGLOS lost my account or I can't remember what I used originally so I created a new one. Put me back to start and I recreated my map. Then it didn't show me as logged in anymore so I had to log in and it put me back to start.]
The text was updated successfully, but these errors were encountered:
This still works as I originally reported. Added to map, decided to save collection, Login to MyGLOS, after logging in it takes me to catalog view. Go to map, and it is just the default map - my map view (potential future collection) I was building is no longer there.
FYI Another example of this behavior is when user adds a buoy to map then clicks on 'manage alerts'. If they aren't logged in, they get the error message that they must be logged in order to manage alerts. They login, but then are put to the catalog page and now have to re-do their search and buoy placement before they can set their alert.
If user creates a map and then wants to save it, but they have not logged in or created a MyGLOS account, they then are taken back to the default catalog page. In other words, they have now lost the map they just were working on creating. Suggest expected behavior to be that they get put back exactly where they were. [I know this because for some reason myGLOS lost my account or I can't remember what I used originally so I created a new one. Put me back to start and I recreated my map. Then it didn't show me as logged in anymore so I had to log in and it put me back to start.]
The text was updated successfully, but these errors were encountered: