I have been wondering ever since I started to build my latest app on bubble, what is the official way of locking down the pages of your app so pages can truly be private for non users. I cant see why there isn’t a better way than having to initially load the page before a check can be done in the workflow.
I am aware of the work around that can be used for this use case, however these are indeed work arounds that accomplish it, however it would make sense that a specific workflow be run to check if a page should be in much the same way that privacy allows database level security.
Bump…
I’m looking for the same. When I’m using an on page load action to redirect on certain conditions but the original url page is fully loaded before the redirection. This means I need to hide all elements by default to prevent a bad user experience.
It would be great if there was on on-request event that could be used.
No, there isn’t a built-in way. Bubble does the same thing, just on page load, does a check: For example, checking if the user is logged in and if they are not, being redirected to another page with a workflow action.
Okay…I resorted to putting everything in a group and making the group hidden unless the user was logged in. That combined with the data security sounds like the right way to do this then Yes?
Thanks. I like what I’m seeing so far…just these concepts that are bubble specific that need to be under my belt. I’ve developed systems for 35 years…I’m liking this so far. I just need to quit over-thinking it.
Yes?