Tell us what you are trying to do?
Hello,
I have set up a group of custom fields which are "Allowed as multiple-instances"
I would like to add this entire group with one button when editing the post.
Meaning instead of adding one filed at a time.
The whole group set of custom fields meta boxes would appear under the previous one, where then the users can select the values. Then this would render in the front end as well. Like an update log.
Is there any documentation that you are following?
No
Is there a similar example that we can see?
Yes, please see the screenshots attached
#1, #2 & #3
What is the link to your site?
hidden link
You're welcome to join and I would make you an administrator since all the content is hidden to the public.
Hi, what you're describing is a very close description of the Many-to-Many relationship changes that are coming up very soon. You can follow along with our blog for some more information about this, and there's even a beta version you can use as a (very limited) preview:
https://toolset.com/2017/09/first-beta-of-types-2-3-with-post-relationship/
In the meantime, the closest approximation of this system we offer is parent / child relationships. In your case, Ad Update would represent a new Post Type rather than a custom field group. The Ad Update post type will be a child of the post type you pictured above. Then you can use the Post Relationship fields in the parent post editor to manage child posts, similar to what you're describing for custom fields.
https://toolset.com/documentation/user-guides/creating-post-type-relationships/
https://toolset.com/documentation/beyond-the-basics/post-relationship-concepts/implementing-one-to-many-relationships/
Thanks a lot for your reply Christian.
I think I get your temporary work around for this feature.
If I "add a new post type" as a child of the post, would that child be in a different URL?
If so, here's the challenge:
Currently my posts are private and assigned only to certain users.
If a child post with a different url gets created, the problem would be that, an administrator would have to go in each time there is an update and set the users restriction settings over and over which would not be so good.
Also, approximately how soon would you estimate the Relationship Update to be ready?
If I "add a new post type" as a child of the post, would that child be in a different URL?
Yes, that's correct. WordPress will create a unique URL for each child post by default.
an administrator would have to go in each time there is an update and set the users restriction settings over and over which would not be so good.
I see what you mean, that's not ideal. Is it really necessary to have a single post URL for each child? If not, you could tell WordPress not to create one using the Post Type editor configurations. You can turn off "rewrite", so a unique URL will not be created. You can turn off "feeds", "pages", "has_archive", and "query_var" and turn on "exclude from search", etc. to tweak the privacy of these posts.
Yes, I really need one URL per post and have all the updates inside that same URL.
Other things I should mention is that eventually:
The posting system would not be handled by the regular WP Backend Post Editor
It'll be handled with the "Frontier Plugin": https://wordpress.org/plugins/frontier-post/
It will be used by people who will not be that tech savy nor would want to put in much settings each time they create a post and ad an update. My goal is to make it as easy as possible for them. Some will be just viewers some will be Authors.
I don't mind waiting some time for the update you mentioned.
Do you have an idea of how log would it take to be out?
Yes, I really need one URL per post and have all the updates inside that same URL.
Okay great, then you can turn off the rewrites for child posts using the Post Type options, like I was describing. Then show all the child post information on the parent post URL by using a View of child posts. This way, on the front-end everything will appear at the same URL. On the back-end, you will have separate editors for parent and child post types, but on the front-end they will be displayed together. I think this is what you're describing. Please correct me if I'm wrong.
The posting system would not be handled by the regular WP Backend Post Editor
It'll be handled with the "Frontier Plugin": https://wordpress.org/plugins/frontier-post/
Okay, I'm not really familiar with this plugin. If it's able to create posts in a custom post type, and apply custom field values to those posts, then it should be possible to create the posts with the custom fields and associations you need. But learning how to use Frontier would be your responsibility. I can tell you what you need to do technically to create a post and store the necessary values, but not how to execute that within Frontier. Or, I can help you set this up in CRED, which is our front-end post creation system, in a way that is simple for your users.
I don't mind waiting some time for the update you mentioned.
Do you have an idea of how log would it take to be out?
I don't have an idea at the moment, sorry. The beta that's available now is very limited, and is only capable of saving data. It's not capable of displaying that data, and it's not ready for production by any means. It's intended to allow users to try it out and get their feedback. So my best guess is more like multiple months than multiple weeks, because full implementation will require updates to Views as well, and there are no betas available for that yet.
