Great video. Is there a way to get a 302 redirect on a page when you also want to be able to redirect the user to a specific path in your URL after they log in? For example, when a user clicks on a link in an email you sent them but they're not logged in. I want them to be redirected to that specific URL path afterwards. I'm able to do that using "This URL", but it causes the redirect to be a 200 redirect instead of a 302. Is there a better way to do this?
@@mattschuberg Thanks for answering! I also couldn't find a way to use "This URL", but there is a way almost equivalent that still gives 302: Check the "Send current page parameters" and also "Send more parameters to the page" to add something like afterlogin="my-page", where you have to type the "my-page" instead of extracting anything from "This URL". Then just use these parameters to redirect the user back after the login.
The answer from @antoruby is the way! The only way to preserve values through 302 redirects is to use url parameters and to then use those parameters in your routing logic. One good approach is to have a dedicated /redirect page in your app that you use for your 302 redirections. On that page then you handle the specific routing depending on what parameters there are in the URL. Hope that helps!
out of context, but how do you allow users to upload a csv that has comma-separated text values in the cells of one of the columns that are of a data type attached to the main data type (the data type being uploaded as csv)? i read for the native action arrays have to be uploaded as JSON array but the user doesn't know that and simply uploads the file where the values are comma-separated.
Hey Matt this is a very important video, thank you. Just to be 100% explicit and sure - for an app to be secure, you must have when page is loaded -> first action: Direct user to 404 ONLY WHEN Current User is not logged in?
Such a great and elaborate explanation.
I've seen so many questions around this and you've explained it perfectly.
Thanks!
Thanks Raymond!
Very informative and useful, keep the good things coming up. Thanks.
Really well explained, thank you.
Realy great, thank you !
Very important lesson. Thank you.
Great video. Is there a way to get a 302 redirect on a page when you also want to be able to redirect the user to a specific path in your URL after they log in? For example, when a user clicks on a link in an email you sent them but they're not logged in. I want them to be redirected to that specific URL path afterwards. I'm able to do that using "This URL", but it causes the redirect to be a 200 redirect instead of a 302. Is there a better way to do this?
Great question 😅 Have you found an answer?
@@antoruby Not yet, unfortunately.
@@mattschuberg Thanks for answering! I also couldn't find a way to use "This URL", but there is a way almost equivalent that still gives 302:
Check the "Send current page parameters" and also "Send more parameters to the page" to add something like afterlogin="my-page", where you have to type the "my-page" instead of extracting anything from "This URL". Then just use these parameters to redirect the user back after the login.
The answer from @antoruby is the way!
The only way to preserve values through 302 redirects is to use url parameters and to then use those parameters in your routing logic.
One good approach is to have a dedicated /redirect page in your app that you use for your 302 redirections. On that page then you handle the specific routing depending on what parameters there are in the URL.
Hope that helps!
"And I'm using something called the internet" Hahaha, my fav moment
out of context, but how do you allow users to upload a csv that has comma-separated text values in the cells of one of the columns that are of a data type attached to the main data type (the data type being uploaded as csv)? i read for the native action arrays have to be uploaded as JSON array but the user doesn't know that and simply uploads the file where the values are comma-separated.
Always difficult to make sense of how bubble treat the data, so that's a great video explaining it 👌
What about pages with a type of data ?
Hey Matt this is a very important video, thank you.
Just to be 100% explicit and sure - for an app to be secure, you must have when page is loaded -> first action: Direct user to 404 ONLY WHEN Current User is not logged in?