Skip to main content

Switching Locations Doesn't Update Interface State

To replicate this issue, take the following steps:

  1. Login as a customer with multiple locations.

  2. Navigate to Get More Reviews > Request Reviews > Edit Campaign > Opt-In Page

  3. Click on Opt-In page. Note URL.

  4. From this screen, switch to a different location.

  5. Click on the Opt-In page. Note the URL is the SAME as the previous location.

  6. Click on Request Reviews > Edit Campaign > Opt-In Page.

  7. Click to open the Opt-In page. Note the URL is now DIFFERENT & has been updated.

The expected behavior is that when a user switches locations, all state updates to reference that location, and anything referencing that location, such as campaign opt in page URLs, should also update.

Status: Completed4 comments

Log in to comment and vote

Comments4

  • Patrick

    •

    May 16, 2024

    Update to this:

    It seems that application state is not updated across multiple components. Not sure what framework or state library you're using, but it's happening inside settings for feedback forms as well. If a user switches locations, they are viewing the previously viewed location's feedback form, not the one they switched to. Weirdly, the page refreshes, but it doesn't change the location data they're viewing.

    I'm assuming this is probably happening application-wide for various other items.

    • mannie@embedmyreviews.com

      Team•

      May 16, 2024

      If you have the feedback form open and switch location you will still remain within that form regardless of switching locations. This applies across the board and is not a bug but by design. If an entity is being updated and you decide to switch it will keep you on the same page.

      • mannie@embedmyreviews.com

        Team•

        May 16, 2024

        saying that if you switch locations on a page that is not reserved for updating i.e. campaigns, forms, widgets then it will reflect the state. You can tell which URL(s) will not change if they have an ID or UUID.

        • Patrick

          •

          May 17, 2024

          I think the most obvious behavior - from a user standpoint - is that when they switch locations, everything "switches". Doesn't that make sense? Several different users have been confused by this. Otherwise, a user switches locations then has to re-navigate to the feedback form (or anywhere else they're currently viewing) for it to refresh. It's confusing & hard to tell which location's data you're viewing. Plus, it takes 2-4 clicks for a user to get to where they want to be.

          Why not do a page refresh fully when switching locations?