I spent so much time researching whether I could achieve this kind of functionality without coding it myself, and your video was the exact answer I needed! 🙏
Kevin, i know you want the best for everyone BUT , the value that you give to others completely overcomes the echo problem, and believe me, I have a super expensive hardcore gaming headset and I hear no echo :p keep it coming
I used an echo remover plugin. There's definitely still some echo but it's way better than the original source audio for sure. It'll be even better soon :)
Yay, finally! I wasn’t expecting the arrival of UI conditions so quick 😅 The by-weekly update schedule of Bricks is really great! We are getting hotfixes and new stuff so fast 🚀
So simple! Love the use case with a radio button - I had been wondering if there was a simple and explainable way to link conditional display options to components that even a client could use. A simple situation would be a local business with a specials section where a cpt needs to be toggled off or on at clients will.
This looks amazing! The screen looks a bit weird on my end, a bit oversaturated and not very defined. It looks much better on other videos on your channel. Just a quick note, hope it's helpful!
Thanks for the video, have been waiting for conditions in Bricks, such an important feature. On a slight tangent, what useful Oxygen features do you believe are still missing in Bricks, that might prevent a 100% transition from Oxy?
@@Gearyco Thanks for the reply. Of course I have ACSS, doesn't everybody :) I have to admit I do feel a bit saddened about thinking of moving away from Oxygen, but now that Bricks has conditions as well, have no more excuses. Have principles to uphold.
Great Video! Thanx! Very useful! I already made it :) Question: I set these hide/show fields (price table) in a specific page, then I added another field (CTA). Can I hide the price table field (in the backend editor) only in a page and show only the hide/show radio button or shall I have to create other group field to show?
SUPER important to me. Using conditions are essential to how I approach client editing of items (posts) from the front end controlled by role and capability. The next really important items on the Bricks Development map for me are CSS Grids (although I already use ACSS), the Mobile and Regular Menu Builders and I would like the Popup Builder IF I could also stick a menu inside a popup as well - but not a deal breaker feature, just a nice one if I wanted to. What are the most important roadmap items for you? Have you voted on them? Thanks Kevin. Just curious, are you actually diagnosed as being Dyslexic? If so, very interesting.
Hi, Kevin. You are super useful and amazing as always. Do you personally prefer ACF or Metabox and why? Please make a video one day comparing latest metabox with latest ACF. Thanks for your time in advance.
I prefer Metabox because it handles custom fields and CPTs and bi-directional relationships all-in-one. And I prefer the general UX of Metabox as well as the fact that it creates a more efficient database structure.
Wow, such a great way to utilize conditions. Is there a way to hide, for example, a button in the header when it is switched to mobile? I had chosen the the hidden option but it still looks like the button is utilizing the real estate. Whereas in Elementor, the the real estate disappears. Just curious.
Is it possible to hide a specific field based upon a users role in Bricks, or is another plugin necessary. Coming from Drupal the Field Permissions module allows for limiting exposure to individual fields on a custom content type. ie custom post type in WP
Will this work in a repeater / dynamic data also? E.g. when you have a dynamic element showing last news and a field has no data, can you hide it for that specific post in the list?
@kevin I would assume this use case can be achieved without act/meta box. Can’t you just set the condition to hide the CTS section when page Id is not the contact page? Just wondering the need for first setting up a custom field when it can be accomplished right in the condition?
Do you enjoy looking up the IDs of specific pages? And then when you need to make changes to the condition, do you enjoy looking at page IDs that lack context as to which page you need to remove? How about when you're working with teams? Will they be able to easily decipher the list of page-id conditions you've created? These questions explain why doing it with metabox is far better.
@@Gearyco agreed. I believe the bricks team are planning to add additional condition parameters like page name, etc. that would address that specific concern.
@@goshenweb It still would be worse to do it that way because then you'd have to edit the footer template every time you wanted to exclude a page. With metabox, you can exclude the page at the same time you're creatin, editing, or viewing it.
in this case can we don't make a custom fields and just use the condition for that container to just show on any page except the contract page? I haven't used the condition yet that's why I'm not sure.
It is so powerfull, But It seems that it has not "Device type" conditions, Am I right ? It is better than Display tag, because it completely remove the code from front end.
@@Gearyco Display condition based on device type. For instance we want to hide a section in mobile phones. If we use display=none, then the code is still there.
I am extemely excited today too!
One, new video
Two, Bricks Conditions
Three, new video explaining the new Bricks conditions.
Bang on.
I spent so much time researching whether I could achieve this kind of functionality without coding it myself, and your video was the exact answer I needed! 🙏
Bricks has basically matured! Having this feature implemented in this way is a great idea. Thanks for sharing!!!
Kevin, i know you want the best for everyone BUT , the value that you give to others completely overcomes the echo problem, and believe me, I have a super expensive hardcore gaming headset and I hear no echo :p keep it coming
I used an echo remover plugin. There's definitely still some echo but it's way better than the original source audio for sure. It'll be even better soon :)
Never thought of using CF's to use as a 'switch' type mechanism for conditions. Always learning new things from you Kevin.
Yay, finally! I wasn’t expecting the arrival of UI conditions so quick 😅 The by-weekly update schedule of Bricks is really great! We are getting hotfixes and new stuff so fast 🚀
It's fantastic :)
Really excited to start using conditions on Bricks!! 😊 These quick and focused on a specific topic tutorials are great! Thanks, Kevin!
Awesome video Kevin 💪 so great. Looking forward to the new content.
Thx for sharing ^__^
Next time don't forget to set your office conditions Echo to "Hide" ;)
😂😂
Thanks so much for sharing, Kevin!! Greetings from Colombia 🙌
Great short tutorial. Really excited about the conditions in Bricks. Thanks for this.
10 min geary video. The dream!
GREAT tutorial. Thank you Kevin!
This video is exactly what I want! Thank you!
So simple! Love the use case with a radio button - I had been wondering if there was a simple and explainable way to link conditional display options to components that even a client could use. A simple situation would be a local business with a specials section where a cpt needs to be toggled off or on at clients will.
You saved me again!
Finally! Can’t wait to start using.
Love it 😊 Excellent 👍 Thanx 🙏
Definitely an echo, but looking forward to watching.
Practical as always, thanks. 👍
Very usefull indeed
This looks amazing! The screen looks a bit weird on my end, a bit oversaturated and not very defined. It looks much better on other videos on your channel. Just a quick note, hope it's helpful!
make sure you have 1080p selected?
Thanks for the good and useful example. Any approximate timeframe on the next Frames launch?
Not yet. Getting closer!
Thanks for the video, have been waiting for conditions in Bricks, such an important feature. On a slight tangent, what useful Oxygen features do you believe are still missing in Bricks, that might prevent a 100% transition from Oxy?
Nothing If you have ACSS. If you don’t have ACSS then bricks is missing a grid builder.
@@Gearyco Thanks for the reply. Of course I have ACSS, doesn't everybody :) I have to admit I do feel a bit saddened about thinking of moving away from Oxygen, but now that Bricks has conditions as well, have no more excuses. Have principles to uphold.
Great Video! Thanx! Very useful! I already made it :) Question: I set these hide/show fields (price table) in a specific page, then I added another field (CTA). Can I hide the price table field (in the backend editor) only in a page and show only the hide/show radio button or shall I have to create other group field to show?
I’d need to see a link
SUPER important to me. Using conditions are essential to how I approach client editing of items (posts) from the front end controlled by role and capability.
The next really important items on the Bricks Development map for me are CSS Grids (although I already use ACSS), the Mobile and Regular Menu Builders and I would like the Popup Builder IF I could also stick a menu inside a popup as well - but not a deal breaker feature, just a nice one if I wanted to.
What are the most important roadmap items for you? Have you voted on them?
Thanks Kevin. Just curious, are you actually diagnosed as being Dyslexic? If so, very interesting.
Not diagnosed but I’m fairly certain I’m “on the spectrum” of dyslexia.
Hi, Kevin. You are super useful and amazing as always. Do you personally prefer ACF or Metabox and why?
Please make a video one day comparing latest metabox with latest ACF. Thanks for your time in advance.
I prefer Metabox because it handles custom fields and CPTs and bi-directional relationships all-in-one. And I prefer the general UX of Metabox as well as the fact that it creates a more efficient database structure.
@@Gearyco I second this.
Wow, such a great way to utilize conditions. Is there a way to hide, for example, a button in the header when it is switched to mobile? I had chosen the the hidden option but it still looks like the button is utilizing the real estate. Whereas in Elementor, the the real estate disappears. Just curious.
Search navigation on my channel there's probably a better way to do it. You may not want to be using a button outside of your navigation.
Is it possible to hide a specific field based upon a users role in Bricks, or is another plugin necessary. Coming from Drupal the Field Permissions module allows for limiting exposure to individual fields on a custom content type. ie custom post type in WP
Yes, Bricks has built in conditions for user role.
Will this work in a repeater / dynamic data also?
E.g. when you have a dynamic element showing last news and a field has no data, can you hide it for that specific post in the list?
Maybe not yet because i think bricks is missing field is empty logic.
@kevin I would assume this use case can be achieved without act/meta box. Can’t you just set the condition to hide the CTS section when page Id is not the contact page? Just wondering the need for first setting up a custom field when it can be accomplished right in the condition?
Do you enjoy looking up the IDs of specific pages? And then when you need to make changes to the condition, do you enjoy looking at page IDs that lack context as to which page you need to remove? How about when you're working with teams? Will they be able to easily decipher the list of page-id conditions you've created? These questions explain why doing it with metabox is far better.
@@Gearyco agreed. I believe the bricks team are planning to add additional condition parameters like page name, etc. that would address that specific concern.
@@goshenweb It still would be worse to do it that way because then you'd have to edit the footer template every time you wanted to exclude a page. With metabox, you can exclude the page at the same time you're creatin, editing, or viewing it.
I’ve tried using conditions using the page ID. It’s a nightmare even you’re managing a sight yourself but even more so with a team or client.
How would you deal with the true / false component of ACF since setting a value to true returns 1 while setting a value to false returns nothing?
I've done this with ACF in the past, but haven't used in a long time. It's definitely doable, though.
IS there a way to hide an element based on page views. For example I have an into but would like to hide it after the first page view.
Yeah you can use local storage and a condition check in bricks
@@Gearyco what do you mean by local storage
in this case can we don't make a custom fields and just use the condition for that container to just show on any page except the contract page?
I haven't used the condition yet that's why I'm not sure.
I wouldn't recommend it. Makes the site much harder to manage.
It is so powerfull, But It seems that it has not "Device type" conditions, Am I right ? It is better than Display tag, because it completely remove the code from front end.
Not sure which part you’re referring to
@@Gearyco Display condition based on device type. For instance we want to hide a section in mobile phones. If we use display=none, then the code is still there.
I spend so much time to realize it doesn't work with switch at all, only with radio.
Ah yes ... I couldn't get it to work with the switch either.
@@Gearyco it make me feel less stupido :p