Hello and thank you for contacting the Toolset support.
I can't really explain the details before knowing which editor you will be using, the block editor, or the classic editor?
But, I'll give it a try and give some ideas on how to implement it from what I understand so far and how I would implement it:
- Create 5 custom post types: Profile, Job, Sport, Hobby, Child. The user will be the author of his own posts.
- Create a "Profile View", will display Profiles filtered by author, the current user to display the profile for his owner, or from parent post where this view is shown if we want to display on a Profile single page (/profile/jamal-toolset).
- Create "Jobs View", "Sports View", "Hobbies View", and "Child View", which will display, each, Jobs, Sports, Hobbies, Child, filtered by the author of the post where this view is shown.
- Use these views inside "Profile View".
Now we can display all the posts without tabs. For tabs, this will depend on what editor we are using. I do not know a solution for tabs right now on blocks, maybe using a 3rd party plugin. I still do not know. We'll figure it out if you are using the block editor. Otherwise, the workaround is to create a view with the classic editor and use it inside the block editor.
If you are using the classic editor and generating Bootstrap tabs, you will need to have a way to count the posts for tab panels and display the tab title if there are any posts. You can adapt the following function to your needs, it currently counts a custom post type for the current user: hidden link
Then register the function to be used in Toolset conditions in Toolset->Settings->Front-end Content->Functions inside conditional evaluations. Check this article https://toolset.com/documentation/user-guides/views/conditional-html-output-in-views/using-custom-functions-in-conditions/
I hope this helps. Let me know more details about your use case and what editor you are using, or allow me temporary access to check it closely. Your next reply will be private to let you share credentials safely. ** Make a database backup before sharing credentials. **
