I was having a very hard time with meta box and this lesson was explained and illustrated in a very clear and understandable fashion. It gave me a great restart. It was actually the first MB project I got to work for me so far (Thank You!). I would appreciate a tutorial that would include adding pictures to an MB post, such as in a service card or menu items, etc. I cannot seem to get pictures to I place in the MB custom fields, to show up in the Bricks builder or the front end, Looking forward to more of your lessons and thanks again!
Thank you for the kind feedback. "I would appreciate a tutorial that would include adding pictures to an MB post, such as in a service card or menu items, etc. " Are you referring to MetaBox front end submission? Or something like adding a feature image/custom field image to a card or something similar?
Great tutorial, I have a question: I made 1 home FAQ and 1 general FAQ post, how can I limit the showing of just the home faq on the home page and the general faq on other pages?
Hey, great question! The way I do it is as follows: 1. enable tags on the FAQ custom post type 2. add a tag to each post E.g. pricing, general, products 3. Inside Bricks and on the CPT query loop, exclude posts by terms. You can say, exclude the general FAQs which will display everything but the general post. Let me know if that works or if you have any other questions.
I don't believe there are any controls to order the sub fields using Bricks. If you wanted the most granular control, you could make a post for each FAQ question. Then enter the answer to that question inside the post's content using the WordPress editor. Query the CPT, then return the post title and the post content wrapped up inside a block. This is a great solution, but takes a bit more time, but is a totally fine solution too.
Are familiar with using Fluent forms with Metabox that lets users update and edit post types on the front end? And also Metabox Data stores on the front end like creating a ticketing system?
@@aperturedigitalmarketing i did it =) Created 5 front end submissions where the user or anyone can create a new post by themself and edit it =) At least something =)
I was wondering how I can use the MB Relationship for that one: Like I have a CPT with Drink Recipes then I choose via MB Relation the related FAQ Post inside my FAQ CPT. And I only want to Display the Related FAQ at the front end.... my big Question... one day I will figure it out =)
When would you make these in a group vs not? When would you make them cloneable? I get why you did it this way for FAQs specifically but why would you do it for any other CPT or would you not?
The group field is used to manage many fields nested under the group name. I use group fields when I want to clone all those fields at once. You make them cloneable when you want to create more and more of those fields on a post/page. "why would you do it for any other CPT or would you not?" For this question, it all really depends on the website and your imagination. Metabox is a data management tool. It helps bridge the gap between your site, the user interface, and the database. So, plan out how you want the user to use the interface and use Metabox to help manage all that data. I don't user group fields for things like "author" or "address." Data that is truly singular do not really need the group field. Group fields are for data that can be extended or cloned as many times as you need. FAQs is a great example because you could have an unlimited number of FAQs and you don't want to have to go create another custom field called "FAQ1/FAQ2/FAQ3" Just pop them all in one group field. I hope that helps make more sense of the Group/Cloneable fields.
If you want the first item to be open by default - see this forum post forum.bricksbuilder.io/t/no-bug-bricks-accordion-brx-open-class-applied-at-wrong-location-when-wrapping-accordion-item-with-adittional-wrapper/10226/7 There is a JS snippet that patches the accordion to make that functionality work.
What is the benefit of doing it that way instead of querying the CPT FAQs directly. let's say you even add taxonomies for your FAQs CPT to categorize these FAQs. Could you not just query/output a bunch of those FAQs from a specific taxonomy without having to have the field group? Oh I see - in my case I would have to add a new FAQ post for every new FAQ Question and Answer combo.
You are correct - using the field group makes the Q and A cloneable. There are many different ways to implement a custom post type for FAQs. So, it depends on the situation. For affiliate marketing, I don't use custom post types for FAQs. I use custom fields. I want the FAQ Q and A to be present on the post because the questions and answers are unique to the post. For service based businesses, I create FAQ custom post types and categorize FAQs that way. Data management is the key point here. Set up your FAQs so you can manage and access the data as easy as possible.
@@aperturedigitalmarketing Awesome. Thanks for the great video and explanation. So it can make sense to have a combination of both. So for example: Have general service level FAQs which might be shown on multiple pages/posts as CPT. And then have post/page specific FAQs for each page/post via custom fields. The best part would be having the front front end even mix the two types and output only one FAQ section there and then output the Schema for those via the technique shown in your other video.
I think if you are using the same custom fields in your CPT and at the page/post level...the schema generation should work. I have no idea...that scenario would need some testing to see how it all works. But thats a good idea and a good question.
@@aperturedigitalmarketing I noticed that the second query - where I have to select the Field group - shows up 3 times in the select field - why is that? I am running Bricks 1.6.2 and the latest MetaBox. I added another Field Group and testet it with that and the new field group also shows up 3 times in the "type" select of the second query.
Why is the accordion not expanding downwards but instead looking like Title>Item (Question>Answer). I was expecting a result like in your video when the item is clicked.: Question Answer
@@aperturedigitalmarketing Starting at about 10 mins you are using the accordion. It opens with the "Answer" below. On my localhost the Answer extends to the right of the Question without any spacing between and the ">" in between the Question and Answer. Edit: I built the same thing with ACF and it worked as expected. Might be MB, might be Bricks, or, I just did something differently? Hope that helps. Thanks.
@@jmcbade2960 Yea that is strange behavior, like its opening in a "row" instead of a "column"? I will see if I can reproduce that behavior. If I can I will reply back.
I was having a very hard time with meta box and this lesson was explained and illustrated in a very clear and understandable fashion. It gave me a great restart. It was actually the first MB project I got to work for me so far (Thank You!).
I would appreciate a tutorial that would include adding pictures to an MB post, such as in a service card or menu items, etc.
I cannot seem to get pictures to I place in the MB custom fields, to show up in the Bricks builder or the front end,
Looking forward to more of your lessons and thanks again!
Thank you for the kind feedback.
"I would appreciate a tutorial that would include adding pictures to an MB post, such as in a service card or menu items, etc. "
Are you referring to MetaBox front end submission?
Or something like adding a feature image/custom field image to a card or something similar?
I agree!!! I was starting to get overwhelmed and then watched this video! :)
Thank you! I never understood how to query groups before. Amazing!!
Who hooo, let me know what you build! That group field could be powerful with switches or something neat like that.
This is such a good reference I actually found myself returning to it for review. Thanks again!
Glad it was helpful!
Thanks for this! I need to create something like this with ACF.
Awesome! Yep should work the same with ACF! Let me know if it doesn't.
Really like how you explain things! Subscribed :)
Thank you for the kind words. I appreciate the feedback.
This is great!
Great tutorial, I have a question: I made 1 home FAQ and 1 general FAQ post, how can I limit the showing of just the home faq on the home page and the general faq on other pages?
Hey, great question! The way I do it is as follows:
1. enable tags on the FAQ custom post type
2. add a tag to each post E.g. pricing, general, products
3. Inside Bricks and on the CPT query loop, exclude posts by terms.
You can say, exclude the general FAQs which will display everything but the general post.
Let me know if that works or if you have any other questions.
@@aperturedigitalmarketing Can you pls indicate where to add a tag to each post?
found the place to add tags to CPT, and tested your way, it worked, thanks for this great totorial!
@@diacutex6391 awesome! Keep pushing the limits. Way to go! I know it feels awesome to get it working how you want.
Can this process be done using ACPT Custom Post Type Framework instead of Meta Box?
I am not sure, I don't use that software personally. Let me know if you discover it works!
Excellent tutorial, thank you. Do you know if you can order the cloneable fields, similarly to how you can order the custom posts?
I don't believe there are any controls to order the sub fields using Bricks.
If you wanted the most granular control, you could make a post for each FAQ question. Then enter the answer to that question inside the post's content using the WordPress editor.
Query the CPT, then return the post title and the post content wrapped up inside a block.
This is a great solution, but takes a bit more time, but is a totally fine solution too.
Yes, just make the field group sorteable
Are familiar with using Fluent forms with Metabox that lets users update and edit post types on the front end? And also Metabox Data stores on the front end like creating a ticketing system?
I will put this on my 2023 road map for sure. Thanks for the suggestions.
@@aperturedigitalmarketing i did it =) Created 5 front end submissions where the user or anyone can create a new post by themself and edit it =) At least something =)
@@dynamic-homepages that's awesome! Dynamic data at its finest!
I was wondering how I can use the MB Relationship for that one:
Like I have a CPT with Drink Recipes then I choose via MB Relation the related FAQ Post inside my FAQ CPT. And I only want to Display the Related FAQ at the front end.... my big Question... one day I will figure it out =)
Figured it out by myself just now, and almost started to cry because of happiness.
Awesome! Glad you got it sorted!
When would you make these in a group vs not? When would you make them cloneable? I get why you did it this way for FAQs specifically but why would you do it for any other CPT or would you not?
The group field is used to manage many fields nested under the group name. I use group fields when I want to clone all those fields at once. You make them cloneable when you want to create more and more of those fields on a post/page. "why would you do it for any other CPT or would you not?" For this question, it all really depends on the website and your imagination. Metabox is a data management tool. It helps bridge the gap between your site, the user interface, and the database. So, plan out how you want the user to use the interface and use Metabox to help manage all that data.
I don't user group fields for things like "author" or "address." Data that is truly singular do not really need the group field. Group fields are for data that can be extended or cloned as many times as you need. FAQs is a great example because you could have an unlimited number of FAQs and you don't want to have to go create another custom field called "FAQ1/FAQ2/FAQ3" Just pop them all in one group field.
I hope that helps make more sense of the Group/Cloneable fields.
@@aperturedigitalmarketing Makes sense. Thank you for the thoughtful reply!
If you want the first item to be open by default - see this forum post forum.bricksbuilder.io/t/no-bug-bricks-accordion-brx-open-class-applied-at-wrong-location-when-wrapping-accordion-item-with-adittional-wrapper/10226/7
There is a JS snippet that patches the accordion to make that functionality work.
What is the benefit of doing it that way instead of querying the CPT FAQs directly. let's say you even add taxonomies for your FAQs CPT to categorize these FAQs. Could you not just query/output a bunch of those FAQs from a specific taxonomy without having to have the field group? Oh I see - in my case I would have to add a new FAQ post for every new FAQ Question and Answer combo.
You are correct - using the field group makes the Q and A cloneable. There are many different ways to implement a custom post type for FAQs. So, it depends on the situation.
For affiliate marketing, I don't use custom post types for FAQs. I use custom fields. I want the FAQ Q and A to be present on the post because the questions and answers are unique to the post.
For service based businesses, I create FAQ custom post types and categorize FAQs that way.
Data management is the key point here. Set up your FAQs so you can manage and access the data as easy as possible.
@@aperturedigitalmarketing Awesome. Thanks for the great video and explanation.
So it can make sense to have a combination of both.
So for example:
Have general service level FAQs which might be shown on multiple pages/posts as CPT.
And then have post/page specific FAQs for each page/post via custom fields.
The best part would be having the front front end even mix the two types and output only one FAQ section there and then output the Schema for those via the technique shown in your other video.
I think if you are using the same custom fields in your CPT and at the page/post level...the schema generation should work. I have no idea...that scenario would need some testing to see how it all works. But thats a good idea and a good question.
@@aperturedigitalmarketing I noticed that the second query - where I have to select the Field group - shows up 3 times in the select field - why is that? I am running Bricks 1.6.2 and the latest MetaBox.
I added another Field Group and testet it with that and the new field group also shows up 3 times in the "type" select of the second query.
Why is the accordion not expanding downwards but instead looking like Title>Item (Question>Answer).
I was expecting a result like in your video when the item is clicked.:
Question
Answer
Hello, could you reference a timestamp on the video for some additional context? I want to make sure I understand your question before I answer.
@@aperturedigitalmarketing Starting at about 10 mins you are using the accordion. It opens with the "Answer" below. On my localhost the Answer extends to the right of the Question without any spacing between and the ">" in between the Question and Answer.
Edit: I built the same thing with ACF and it worked as expected. Might be MB, might be Bricks, or, I just did something differently?
Hope that helps. Thanks.
@@jmcbade2960 Yea that is strange behavior, like its opening in a "row" instead of a "column"? I will see if I can reproduce that behavior. If I can I will reply back.
@@aperturedigitalmarketing I hope you are able to reproduce it and let me know what caused it. Thanks
@@jmcbade2960 This was all I could come up with snipboard.io/7Xwjx8.jpg