Conditionally Show & Hide Page Elements with Conditions in Bricks Builder

แชร์
ฝัง
  • เผยแพร่เมื่อ 3 ธ.ค. 2024

ความคิดเห็น • 62

  • @RedcubeX24
    @RedcubeX24 2 ปีที่แล้ว +1

    I am extemely excited today too!
    One, new video
    Two, Bricks Conditions
    Three, new video explaining the new Bricks conditions.
    Bang on.

  • @LaurelRonning
    @LaurelRonning 3 หลายเดือนก่อน +1

    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! 🙏

  • @webcare_live
    @webcare_live 2 ปีที่แล้ว +4

    Bricks has basically matured! Having this feature implemented in this way is a great idea. Thanks for sharing!!!

  • @hakira-shymuy
    @hakira-shymuy 2 ปีที่แล้ว +1

    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

    • @Gearyco
      @Gearyco  2 ปีที่แล้ว

      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 :)

  • @ocbroadband
    @ocbroadband 2 ปีที่แล้ว +5

    Never thought of using CF's to use as a 'switch' type mechanism for conditions. Always learning new things from you Kevin.

  • @stripedgoat
    @stripedgoat 2 ปีที่แล้ว +9

    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 🚀

    • @Gearyco
      @Gearyco  2 ปีที่แล้ว +3

      It's fantastic :)

  • @isaurasotoca
    @isaurasotoca 2 ปีที่แล้ว

    Really excited to start using conditions on Bricks!! 😊 These quick and focused on a specific topic tutorials are great! Thanks, Kevin!

  • @AmandaLucaseu
    @AmandaLucaseu 2 ปีที่แล้ว +1

    Awesome video Kevin 💪 so great. Looking forward to the new content.

  • @kareem2928
    @kareem2928 2 ปีที่แล้ว +5

    Thx for sharing ^__^
    Next time don't forget to set your office conditions Echo to "Hide" ;)

  • @HectorVector85
    @HectorVector85 10 หลายเดือนก่อน

    Thanks so much for sharing, Kevin!! Greetings from Colombia 🙌

  • @dahunsi
    @dahunsi 2 ปีที่แล้ว

    Great short tutorial. Really excited about the conditions in Bricks. Thanks for this.

  • @OneBrokeBloke
    @OneBrokeBloke 10 หลายเดือนก่อน

    10 min geary video. The dream!

  • @chelofonte
    @chelofonte ปีที่แล้ว

    GREAT tutorial. Thank you Kevin!

  • @LooWoo-d6q
    @LooWoo-d6q ปีที่แล้ว

    This video is exactly what I want! Thank you!

  • @joshknight8744
    @joshknight8744 2 ปีที่แล้ว +3

    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.

  • @GavinDavidson
    @GavinDavidson ปีที่แล้ว

    You saved me again!

  • @ReubenHochstetler
    @ReubenHochstetler 2 ปีที่แล้ว

    Finally! Can’t wait to start using.

  • @joachimauster
    @joachimauster 2 ปีที่แล้ว

    Love it 😊 Excellent 👍 Thanx 🙏

  • @pandaosa9
    @pandaosa9 2 ปีที่แล้ว +1

    Definitely an echo, but looking forward to watching.

  • @kevindezwart
    @kevindezwart 2 ปีที่แล้ว

    Practical as always, thanks. 👍

  • @rebelinc
    @rebelinc 2 ปีที่แล้ว +1

    Very usefull indeed

  • @Pensandoci9
    @Pensandoci9 2 ปีที่แล้ว +1

    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!

    • @Gearyco
      @Gearyco  2 ปีที่แล้ว

      make sure you have 1080p selected?

  • @pandaosa9
    @pandaosa9 2 ปีที่แล้ว +1

    Thanks for the good and useful example. Any approximate timeframe on the next Frames launch?

    • @Gearyco
      @Gearyco  2 ปีที่แล้ว +1

      Not yet. Getting closer!

  • @mayanikolova8353
    @mayanikolova8353 2 ปีที่แล้ว

    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
      @Gearyco  2 ปีที่แล้ว +1

      Nothing If you have ACSS. If you don’t have ACSS then bricks is missing a grid builder.

    • @mayanikolova8353
      @mayanikolova8353 2 ปีที่แล้ว

      @@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.

  • @simonepagnini6735
    @simonepagnini6735 10 หลายเดือนก่อน

    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?

    • @Gearyco
      @Gearyco  9 หลายเดือนก่อน

      I’d need to see a link

  • @jmcbade2960
    @jmcbade2960 2 ปีที่แล้ว

    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.

    • @Gearyco
      @Gearyco  2 ปีที่แล้ว

      Not diagnosed but I’m fairly certain I’m “on the spectrum” of dyslexia.

  • @itevensystems8860
    @itevensystems8860 2 ปีที่แล้ว

    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.

    • @Gearyco
      @Gearyco  2 ปีที่แล้ว +9

      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.

    • @stripedgoat
      @stripedgoat 2 ปีที่แล้ว +2

      @@Gearyco I second this.

  • @markbratton111
    @markbratton111 4 หลายเดือนก่อน

    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.

    • @Gearyco
      @Gearyco  4 หลายเดือนก่อน

      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.

  • @a1webguy
    @a1webguy 11 หลายเดือนก่อน

    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

    • @Gearyco
      @Gearyco  11 หลายเดือนก่อน

      Yes, Bricks has built in conditions for user role.

  • @Xboxers
    @Xboxers 2 ปีที่แล้ว

    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?

    • @Gearyco
      @Gearyco  2 ปีที่แล้ว +1

      Maybe not yet because i think bricks is missing field is empty logic.

  • @goshenweb
    @goshenweb 2 ปีที่แล้ว

    @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?

    • @Gearyco
      @Gearyco  2 ปีที่แล้ว +3

      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.

    • @goshenweb
      @goshenweb 2 ปีที่แล้ว +1

      @@Gearyco agreed. I believe the bricks team are planning to add additional condition parameters like page name, etc. that would address that specific concern.

    • @Gearyco
      @Gearyco  2 ปีที่แล้ว +7

      @@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.

    • @ReubenHochstetler
      @ReubenHochstetler 2 ปีที่แล้ว +2

      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.

  • @paolobattiloro947
    @paolobattiloro947 2 ปีที่แล้ว

    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?

    • @Gearyco
      @Gearyco  2 ปีที่แล้ว +1

      I've done this with ACF in the past, but haven't used in a long time. It's definitely doable, though.

  • @AlwaysSlimShadyBro
    @AlwaysSlimShadyBro 6 หลายเดือนก่อน

    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.

    • @Gearyco
      @Gearyco  6 หลายเดือนก่อน

      Yeah you can use local storage and a condition check in bricks

    • @AlwaysSlimShadyBro
      @AlwaysSlimShadyBro 6 หลายเดือนก่อน

      @@Gearyco what do you mean by local storage

  • @Nima-Norouzi
    @Nima-Norouzi 2 ปีที่แล้ว

    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.

    • @Gearyco
      @Gearyco  2 ปีที่แล้ว

      I wouldn't recommend it. Makes the site much harder to manage.

  • @hosseinkhanmohammadi4770
    @hosseinkhanmohammadi4770 ปีที่แล้ว

    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
      @Gearyco  ปีที่แล้ว

      Not sure which part you’re referring to

    • @hosseinkhanmohammadi4770
      @hosseinkhanmohammadi4770 ปีที่แล้ว

      @@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.

  • @TheTrentmoller
    @TheTrentmoller 2 ปีที่แล้ว

    I spend so much time to realize it doesn't work with switch at all, only with radio.

    • @Gearyco
      @Gearyco  2 ปีที่แล้ว +1

      Ah yes ... I couldn't get it to work with the switch either.

    • @TheTrentmoller
      @TheTrentmoller 2 ปีที่แล้ว

      @@Gearyco it make me feel less stupido :p