Nice video! Thanks for sharing. My only critique would be that you need some form of error control for the JavaScript that fires after the form submission. You should use the same check used at the beginning after the JavaScript that fires after the form submission and the add a Branch after the JavaScript to be sure everything fired correctly before moving on to the Close Popup.
What I came up without adding any new nodes was to check if the item was stored in local storage by trying to get it immediatly after setting it. If retrieval fails, then refresh the page. I'm not sure if the close popup node will run if of the previous JS step triggers the failure refresh. In my testing, the previous set of actions that true/false test for age_gate storage item will fail before the JS sets the age_gate item. So, What I added was probably more than what is needed for most use cases.
@@aperturedigitalmarketing All you needed to do was add the isAgeGateVerified function after the setAgeGate function. Then in the new Branch node, you check if it is false. If it is then move to Close Popup. If the setAgeGate fails and the isAgeGateVerified is not false then set it to "show" a hidden error message in your Popup. You could put this failed setAgeGate in a console, but that would not be good for the UX.
Great Video! But why are you using a Pro Form only for the submit button? Why did you not using a simple button and a click event instead the submit button and the on submit event?
Thanks for this, will watch later but looked at the website link and laid out really nice, didn't know you had a Bricksforge link or I would have used it, is your course up and running now? No money after the holidays but sometime this year......
Recording is in progress! I hope to be finished up end of Q1 2025. I pivoted to a full blown community rather than a course. So, building out all of that as we speak!
I doubt the code BF produces is going to have any impact. But, I have not looked at the waterfall to see. I bet it's going to be less than say a 75kb above the fold hero image.
Why not just a simple button + onclick event? What dictates "which" on pageload is gonna fire first? There MUST be a place to control this, not shown in your video or theirs. As a side note, you dont necessarily have to use those const in the js.. there are also bricksforge global variables now.
@@BGdev305 I chose a form instead of a button so I could log form submissions action if I wanted. But a button would work too! If you watch the node explainer video, it says you can't route multiple events that you have to separate them. So that's what I did. It works too 👍
Thanks for sharing this 🎉
Love your style of doing videos! Hope to see more Bricksforge 3.0 tutorials :) well done
Love this! awesome for showing
Nice video! Thanks for sharing. My only critique would be that you need some form of error control for the JavaScript that fires after the form submission.
You should use the same check used at the beginning after the JavaScript that fires after the form submission and the add a Branch after the JavaScript to be sure everything fired correctly before moving on to the Close Popup.
I think that's a great idea, I'll incorporate the code in the blog post!
What I came up without adding any new nodes was to check if the item was stored in local storage by trying to get it immediatly after setting it. If retrieval fails, then refresh the page.
I'm not sure if the close popup node will run if of the previous JS step triggers the failure refresh.
In my testing, the previous set of actions that true/false test for age_gate storage item will fail before the JS sets the age_gate item. So, What I added was probably more than what is needed for most use cases.
@@aperturedigitalmarketing All you needed to do was add the isAgeGateVerified function after the setAgeGate function. Then in the new Branch node, you check if it is false. If it is then move to Close Popup. If the setAgeGate fails and the isAgeGateVerified is not false then set it to "show" a hidden error message in your Popup. You could put this failed setAgeGate in a console, but that would not be good for the UX.
Great Video!
But why are you using a Pro Form only for the submit button? Why did you not using a simple button and a click event instead the submit button and the on submit event?
I think the Pro Form log form submission action would be useful to gather additional data. But, yep, you could use a simple button.
Thanks for this, will watch later but looked at the website link and laid out really nice, didn't know you had a Bricksforge link or I would have used it, is your course up and running now? No money after the holidays but sometime this year......
Recording is in progress! I hope to be finished up end of Q1 2025. I pivoted to a full blown community rather than a course. So, building out all of that as we speak!
Is there much overhead vs coding in the Code Block?
I doubt the code BF produces is going to have any impact. But, I have not looked at the waterfall to see. I bet it's going to be less than say a 75kb above the fold hero image.
Get the JS code here: dominate.aperturedigitalmarketing.com/node-demo
Why not just a simple button + onclick event?
What dictates "which" on pageload is gonna fire first? There MUST be a place to control this, not shown in your video or theirs.
As a side note, you dont necessarily have to use those const in the js.. there are also bricksforge global variables now.
@@BGdev305 I chose a form instead of a button so I could log form submissions action if I wanted. But a button would work too! If you watch the node explainer video, it says you can't route multiple events that you have to separate them. So that's what I did. It works too 👍