How To: ACF Flexible Content Fields & WordPress Bricks Builder

No video

How To: ACF Flexible Content Fields & WordPress Bricks Builder

Рет қаралды 12,633

WPTuts

Күн бұрын

Пікірлер: 56

@Hausa-Cinema 7 ай бұрын

I Don't Know Why Every Search I Made I Found Your Channel With Perfect Video. You Deserve Millions Of Subs. ❤❤❤

@RiyazShihabdeen 6 ай бұрын

Awesome tutorial Paul. Precise to the point. Keep it up. 😍👍

@BGdev305 11 ай бұрын

@wptuts Paul you have been one of my top KZfaq Creators for a long while now! I'm sooooo looking forward to you doing more with Bricks instead of that other builder 🤮 Your tutorials just have that easy to learn flow!

@brianrougeau 11 ай бұрын

Thank you, Paul. This is super helpful. Have a great day!

@FannyBrown-e2d 13 күн бұрын

Hi Paul, I love your videos they are clear and informative. In fact, they have encouraged me to purchase ACF Pro, but unfortunately they don't accept Paypal, and keep declining my card (which I use on Paypal all the time with no issues.) I know Paypal can be a pain, but so can international transactions when you have never made them outside of Paypal before. Very keen to try, but unable to buy. Never had so much trouble purchasing a product in my life!

@stevebaker2896 10 ай бұрын

Great tutorial - although I'm not clear as to why you would use Flexible Content for this at all? Why not just make 2 Group fields for example - one for the project details and one for the client feedback? What's the reasoning behind, or benefit of, using flexible content here? Is it just that the fields are 'hidden' in the add/edit post page until a flexible content row is added?

@jybedesign 8 ай бұрын

Flexible content allows the website editor to create not only 1x Project Overview and 1x Client Feedback (as "Group Field" would do), but as much as he wants (for example 5x Project Overview and then 3x Client Feedback, ALL in the same page). He can even reorder them (2x Project then 3x Feedback then 1x Project then 2x Feedback, etc.). When you think Flexible content, think "Super Repeater". Repeater can only create "one kind of component" (here, Project Overview OR Client Feedback). With Flexible content, you can create both types of elements in the same page, in AS MUCH OCCURENCE as you like (and you can reorder them).

@captainfire74 4 ай бұрын

@@jybedesign Thank you, I was wondering the same think and your answer is crystal clear :p

@Jim.Hummel 9 ай бұрын

Fantastic info as always...my mind is running in top gear thinking of scenarios where I could apply this.

@WPTuts 9 ай бұрын

So many ways to use this and Bricks makes it so easy.

@Jim.Hummel 9 ай бұрын

@@WPTuts - Indeed…I’m making the switch from Elementor this week.

@fiqihalfarizy4843 11 ай бұрын

GRREEEEATTTTT!!!

@KariposTheOne 11 ай бұрын

Great!

@vj-design 4 ай бұрын

Flexible content is the way to go! What is the mouse/tablet you’re using in this video?

@WPTuts 4 ай бұрын

It’s the Apple Magic Trackpad.

@yarinbarry3926 7 ай бұрын

Thanks for great tutorial! Everything works as you explained, a part from using a repeater inside a flexible content. For some reason, it seems that bricks doesn’t recognize the repeater fields when they are nested inside flexible content. Did you ran into this issue as well? Any solution?

@sophiemulders 6 ай бұрын

I think you need a double loop.a loop in a loop. One loop to get the flexible content, and in there a loop for the repeater. But not 100% sure. Sometimes bricks just does not want to play nice

@Arvoisa 11 ай бұрын

ACF flexible content is currently best way to make sites in bricks. Now we need to make our voices hears and hopefully they add native support for ACF blocks in bricks!

@BGdev305 11 ай бұрын

Kinda doubt it.. atleast until wordpress irons out all of the bad semantic issues with Gutenberg.

@michaelvandinther 10 ай бұрын

Streamlining the workflow would be a giant leap forward. Imagine ACF fields being automatically generated and mapped to a WP page based on the elements used in Bricks layout. 😮 Sections are rows, query loops are repeaters etc.

@thomasbauer4801 9 ай бұрын

Great Tutorial. thank you so much 🙏🏻. Does it works also with ACPT flexible Content field?

@WPTuts 9 ай бұрын

I believe so, yes. I’m still testing ACPT with Bricks. So far, everything seems to be working the same as ACF.

@thomasbauer4801 9 ай бұрын

@@WPTuts Update: I have just tried it out. Unfortunately it doesn't work - when I select Use query loop in the block, I can't select the flexible element itself, only the blocks it contains.So instead of "[Page] - Inhalt flexibelContent" it shows "[Page] - Inhalt flexibelContent heading" (heading is one of the contenttype). I can loop the content, but only on this single content type. Also, adding image galleries doesn't seem to work for a single content type either. But maybe I am doing something wrong?

@WPTuts 9 ай бұрын

@@thomasbauer4801 hmm, that’s a shame. I’ll have to have a play around with it and see what’s going on. It’s probably worth reaching out to the developer to see if it’s supported or will be in the near future. I know v2 is due for release soon. Maybe that’s updated the flexible content functions.

@micheltsa 11 ай бұрын

A great feature of ACF Flexible Content is that it allows the end user to insert blocks in any order. Does Bricks support this functionality as well?

@56k-web 11 ай бұрын

Yes. The Order is respected in the loop

@jenniferward6821 11 ай бұрын

thank you for this - how does ACF handle map listings?

@shepdesign 11 ай бұрын

Wonderfully

@sophiemulders Ай бұрын

just a bit confused... can you only use the flexible content sections once on a page? what happens if you use them twice? or is that where the conditional logic with acf_get_row_layout is for?

@WPTuts Ай бұрын

No, you can stack them as needed on a page.

@sophiemulders Ай бұрын

@@WPTuts so if i understand correctly; i put multiples on the page on forehand? And hide if empty? My brain has having a 404😂 I will just test. Lol.

@clairebarnett4587 11 ай бұрын

Can you have more than one of the repeater block types on the same page?

@WPTuts 11 ай бұрын

I haven’t tested it, but I believe it should work.

@shepdesign 11 ай бұрын

Yes, you can. You can have as many as you want.

@clairebarnett4587 10 ай бұрын

This tutorial was a huge prompt for me moving to Bricks from Elementor. I have so many use cases for flexible content and to be able to create it directly in the builder without any additional templates is a much better workflow. Thank you for this in depth tut!! @@WPTuts

@wingtracer 8 ай бұрын

Have you noticed that Bricks wraps the "loop" child elements in an html tag and class of whatever tag and class the looping parent element has?? I don' think this is great for SEO, have no idea why they do this, and it bloats the DOM for no apparent reason. I haver tried for hours to work around this. I would love your thoughts @WPTuts

@NiPSpawN 9 ай бұрын

What are alternative for elementor to check the existence of flexible content field and then display? 8:42 How i can do that?

@vigilantezack 7 ай бұрын

It seems like this style of page development is all-or-nothing. For example, if this were for a blog, then how would you combine the flexible content rows with the Gutenberg blocks? Can you mix and match back and forth between Gutenberg blocks and flexible content rows? So you'd have to pick one method and disable the other. But if it's not for Gutenberg content, then it's only for page content, but now you have the same question of mixing directly Bricks builder content with the flexible content. In your example, you have standard Bricks output in the upper part of the page and then only output flexible content in a certain spot. This is not very flexible if the user wants to insert their flexible row higher up on the page, or mix flexible content with other custom Bricks content on the page. So you kind of just have to pick one style or the other. Based on how Bricks itself works, if this is only for page content and not templated/blog style content, then we can accomplish users adding pre-made styled blocks in Bricks just by having saved templates they can insert. Yes there is a small learning curve if the end user wants to use the page builder and learn how to add/remove templates, but I've never had a client complain. In fact once I tell them a little about Bricks and encourage them to watch a beginner video or two, they quite enjoy using it. So unless a person has a demand that end users never enter Bricks mode, using flexible content seems like extra unnecessary steps. Especially over time maintaining it. What if you don't need a block any more, or have to change it, or the user asks for more types of blocks. It's a ton of custom fields and logic and templating to manage. But if they know how to use Bricks, they can just edit the mast template or adjust styles or simply delete blocks right out of Bricks as normal. To each their own, but flexible content seems like an old methodology to me. Why not skip all the ACF field creation, looping, logic, dynamic stuff, and stick to either Gutenberg posts or Bricks builder pages/templates? I don't see an actual need to inject using flexible content strategy unless, again, the dev demands nobody ever use Bricks. But why? Bricks (and others) are "page builders", that's their exact job, building pages. It's a learning curve but the curve isn't that hard when doing high level basic stuff.

@DaveSorge 3 ай бұрын

I'm 100% sure I'm missing something but after eleven minutes I still have no clue why I would ever use this.

@adrianarcay5559 11 ай бұрын

Elementor is way behind on this point for a long time. dynamic groups, conditional... etc...

@WPTuts 11 ай бұрын

I agree. Bricks is focusing on making a solid platform for dynamic data as opposed to relying on additional plugins.

@emailjough 11 ай бұрын

Adding the Dynamic Content for Elementor plugin lets you easily do everything shown here and much more. But yes it does mean adding a plugin to Elementor.

@WPTuts 11 ай бұрын

@@emailjough exactly. It’s another plugin to do what should be basic functionality.

@BrantK147 11 ай бұрын

Can you do absolutely everything you can do with Elementor in Bricks? Somoene please tell me! If so, I'm switching because Elementor's so full of bugs lately...

@Gearyco 11 ай бұрын

Bricks is much more powerful than Elementor.

@BrantK147 11 ай бұрын

@@Gearyco is it though?

@WPTuts 11 ай бұрын

In many important ways, yes it is. To do what’s covered in this and the previous video about Repeater Regions would require extra plugins in Elementor Pro. Global styling and class based design is way more powerful in Bricks and dynamic data is way more powerful and flexible natively in Bricks. Plus, you have more control over WooCommerce and more than offered by Elementor.

@BrantK147 11 ай бұрын

@@WPTuts Interesting. I will definitely start using it then. What about Bricks compared to Oxygen? Who has the edge? I'm just trying to find a builder that I'll be able to rely on for years to come. Is perhaps Webflow the answer? idk.

@WPTuts 11 ай бұрын

@@BrantK147 I wouldn’t opt for Oxygen tbh. It’s a good tool but the framework it’s built in is older and is coming to the end of its life. Oxygen will still be supported, but I personally wouldn’t want that fact potentially limiting what I can do. Webflow is good but can get expensive quickly for larger sites. It really comes down to the types of sites you’ll be developing and how you want to handle supporting them into the future. Bricks is a good candidate, but you should also look into some of the block based tools like Cwicly, Greenshift, etc.

@MarnoKumaya 2 ай бұрын

how to do it in elementor?

@WPTuts 2 ай бұрын

You can’t without additional plugins.

@MarnoKumaya 2 ай бұрын

@@WPTuts Thank you for replying to my comment. Yes, I have installed ACF Pro, Elementor Pro, and Jet Engine. If I don't use Bricks Builder and only use Elementor Pro and Jet Engine, can I still do the same things?

@ohadcohen136 8 ай бұрын

Why not just to learn how to do it yourself with code?

@WPTuts 8 ай бұрын

Carry on.. but not everyone has the inclination or need to learn coding when there are viable no-code tools available that make the process way easier.