I am trying to emulate some of ACF's flexible content paradigm with toolset, and it seems the design direction for Toolset is to have discrete fields associated with post types as opposed to the flexible content loop idea ACF uses. Based on the documentation, I'm fairly sure this is the case, but I wanted to check in briefly to make sure there wasn't something I was missing.
Our end goal is to have multiple custom field groups, each assigned to a taxonomy term and representing a page component, which we will then handle rendering in a template. This approach works, as far as I can tell, but only assuming each page component only appears once on a given page. With this quick overview of the thought process, is there a native way toolset would allow us to include a specific page component twice on the same page without needing an entire second custom field group?
Thanks in advance, and please let me know if I can clarify anything regarding this request.
Is there any documentation that you are following?
Toolset is to have discrete fields associated with post types as opposed to the flexible content loop idea ACF uses.
Can you provide a bit more clarity here for me ?
is there a native way toolset would allow us to include a specific page component twice on the same page without needing an entire second custom field group?
Can you provide an example so that I can know exactly what you're referring to ?
Sure - in our system we have associated a custom field group with each of our front-end design components/sections (hero, text with image, image grid, newsletter sign up with text, etc), and have assigned a subset of these sections to a page via taxonomy terms (the home page has the hero, text with image, and newsletter sign up sections, for example).
At the moment, it seems like we could only have one text with image section (for example) per page; as we have already associated the text with image field group with the home page, we can't associate it again, meaning that with this structural approach we can currently only have one instance of a design component/section on a given page. Is there a way for us to reuse the same field group on a given page (in our case, so that we could use the same design component/section again)? Or some way we can emulate using the same field group again?
Thanks in advance for your help, and please let me know if I can clarify anything else or if you have any other questions.
Thank you for the explanation, however im not sure of what are the post types. How i'm interpreting this is that you want to assign a field group to multiple post types ?
At the moment, it seems like we could only have one text with image section (for example) per page;
Are you referring here that you can only have 1 custom field for image assigned to the page ?
Here is a though I had.
You've created several post types "hero, text with image, image grid, newsletter sign up with text, etc". On the homepage you want to pull the Hero text that is stored in the Hero post type and the other sections that are stored in their respective post types.
However on another page you want to pull these same sections without having to create a new hero, text with image etc post.
Is there a way for us to reuse the same field group on a given page (in our case, so that we could use the same design component/section again)?
Assuming that my interpretation is correct then what you should be looking into is the Post Relationships. Post relationships will allow you to associate a Post with another post and you can pull the various sections through the post relationships.
Lets say Homepage 1 and Page 2 are both in a relationship with Hero 1 then you can pull Hero 1 on both page.
This gave us half of the answer to our initial question, and from there we figured out a workaround - we created a new post type and related it with the parent (as suggested), and were then able to associate the specific field groups with a dropdown value for the new post type. This let us achieve our end goal of associating the same field group type with the same page multiple times (though the relationship between the new post type and the parent), and should also let us reference an existing post of the new post type on multiple pages if needed.
