On my user profile page, a ‘return to previous page’ action doesn’t work after arriving at that page from one of the other pages. However, it does when the profile page was navigated to from another page. Both pages use the same user card from a RP.
I also have a ‘return to previous page’ action running from a back button placed on the page. This doesn’t ever work on this page, even after arriving from the page that does work with the browser’s back button.
Interestingly, when I press this page’s back button with the action, it breaks the browser’s back button, leaving it unable to work even on the page that it did work with.
Note that the same back button with the action does work on other pages.
What could be the problem? I need this to work as I’m making a PWA.
In Bubble, you have the option to check Replace the entry in the browser’s history when you use the Go to page action.
This means that when a user clicks the ‘back’ button, they won’t see the replaced page, but instead navigate to whichever page in the history was before that. You can see it as moving on to the next page in a book and ripping out the one you just read.
Another thing that you can check are event listener on the window: in chrome type in the dev tool’s console getEventListeners(window), look for popstate, for each item check the listener and see if the function location is some bubble code (e.g. run.js) or not.
I’m getting all sorts of errors on all my pages. I’m don’t even have the Lottie plugin installed, or any Lottie files on the page, so I don’t know why it’s showing that error.
they are different problems, mainly because there are plugins not checking if they have already initialized global instances or if they have all the necessary data. Plugins can load scripts globally even if you don’t use them on the page. It’s something that need to (and can) be fixed, but not relevant to this problem.
have you tried to preview the page without plugins and html?
I just tried these (I didn’t know they existed). I don’t think it’s possible to test the forward/back functionality since when I leave the origin page, it appears the destination page is no longer in safe mode…
Fixed. It didn’t like that the page was navigating to a particular page tab when the page was loaded, for some reason. I replace those workflows with another way that does the same thing. Thanks for the help!
Do you mean that a “scroll to” action was causing the problem? It happened to me in an app that “scroll to” was throwing an error and stopping everything else in the workflow.
