Tour stays on same step if using multipage and subsequent step doesn't exist about hopscotch HOT 2 CLOSED

Hey Jan, thanks for bringing this up. This is a tricky case where a few different cases can have the same saved state, and Hopscotch just does the best that it can.

Consider a tour where step 1 is on page A, and step 2 and step 3 are on page B. If the user is on step 1 on page A and refreshes the page, step 1 should display again once the page has reloaded. To Hopscotch, refreshing the page is the same as loading another page, since it is going to check state (sessionStorage/cookies) to figure out what it should do. Since it's ambiguous what state the tour is in, Hopscotch will try to find elements in this order: step 2, step 1, step 3, step 4, ... and so on until the end of the tour. Checking step 1 is meant to handle the refresh case.

Of course, that means that in situations like yours where the DOM element for step 1 exists on both page A and B, and the element for step 2 does not exist on page B, it's going to get it wrong. At this time, it's just an edge case that the framework currently doesn't handle. Sorry! If you can change your tour to include the step 2 element on page B for sure, or to exclude the step 1 element on page B, that would be the best way to handle it.

from hopscotch.

I have a similar problem when using hopscotch over multiple pages under Wordpress. Cant get passed the first step

from hopscotch.