Skip Navigation

[Resolved] relational website additional questions

This support ticket is created 3 years, 10 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Author
Posts
#1140984

Thank you Lou, it was very helpful. I can see the foundation of my project starting to come to light.

Few additional questions

In creating the "Member" post type, how should I make the form for the person to input their personal data and bio fields? this member will become a user so he/she can see their account. Not all personal data will be available for display in their personal account like the academic achievement, reference letters, grades... the only info available for updating in the user end will be address, email, phone, password.

The users in the project will be three besides the administrator
a) member (who will be the minister or a candidate for ministry same permission leve )
b) Interviewer (board who approves the minister or candidate)
c) overseer ( those in leadership over specific department within the organization)

In this project,
is the "Member" a user ?
Are all users "members" ?

to create the user application form for the different roles I need a form with different set of data for input. Should that be a different form for each user level? This data will have field pertinent to their expertise and academic levels. the application for those fields could become a little complex depending of their level.

Should the user application form have all fields for the lengthy data I need from each user? (data will include external information like background checks)

Can the data collected be available for internal view but not the user owner of that data? like office records only?

how can I link the data availability from the initial user application to the members office records only?

Thanks for helping me. toolset is very powerful set of plugins with vast array of applications.

#1141007

Luo Yang
Supporter

Languages: English (English ) Chinese (Simplified) (简体中文 )

Timezone: Asia/Hong_Kong (GMT+08:00)

Hi,

Q1) In creating the "Member" post type, how should I make the form for the person to input their personal data and bio fields?

It depends on your self, you can use custom user fields or post fields for their personal data:
- For those generic personal data fields(address, email, phone, password), I suggest you use user fields
https://toolset.com/documentation/user-guides/user-fields/
And setup them with Toolset user form
https://toolset.com/documentation/getting-started-with-toolset/publish-content-from-the-front-end/forms-for-registering-users/
Edit each "member" post, setup the post author as the correspond wordpress user

See our document:
https://toolset.com/documentation/user-guides/how-to-create-custom-searches-and-relationships-for-users/

- For those not generic personal data fields(academic achievement, reference letters, grades), you may setup them as custom post fields of post type "Member".

Q2) is the "Member" a user ? Are all users "members" ?
In the suggestion I mentioned in your previous thread, each user is correspond to a individual "Member" post, the "Member" post's author is a individual wordpress user, see the document I mentioned above:
https://toolset.com/documentation/user-guides/how-to-create-custom-searches-and-relationships-for-users/

For the approves permission problem, please check our Access document:
https://toolset.com/documentation/user-guides/setting-access-control/

You can setup custom user roles:
https://toolset.com/documentation/user-guides/managing-wordpress-admin-capabilities-access/

And setup the limitation to the content depends on user's role:
https://toolset.com/documentation/user-guides/access-control-texts-inside-page-content/

And your description is indistinct:

a) member (who will be the minister or a candidate for ministry same permission leve )
b) Interviewer (board who approves the minister or candidate)
c) overseer ( those in leadership over specific department within the organization)

I suggest you create new ticket for those settings, describe detail steps to duplicate the same problem.

Q3) Should that be a different form for each user level?
Within Toolset user form, you can create/edit only one user with one specific user role, see our document:
https://toolset.com/documentation/getting-started-with-toolset/publish-content-from-the-front-end/forms-for-registering-users/
So you will need to setup different user form for each user role.

Q4) Should the user application form have all fields for the lengthy data I need from each user?
It depends on you, if you are going to collect all data with the application form, then you will setup all fields in the application form

Q5) Can the data collected be available for internal view but not the user owner of that data? like office records only?
You can display the data collected as what you want, for example:
- display "member" posts of current logged-in user, you can setup a post view, query "Member" posts, filter by post author is current logged-in user
https://toolset.com/documentation/user-guides/filtering-views-query-by-author/
- display it publicly to everyone, in the single member post, you can display the post author fields with shortcode
[wpv-post-author]
https://toolset.com/documentation/user-guides/views-shortcodes/#wpv-post-author
- display current logged-in user's fields:
https://toolset.com/documentation/user-guides/views-shortcodes/#wpv-user

Q6) how can I link the data availability from the initial user application to the members office records only?
How do you setup the "user application" and "members office records", are they custom post types?
If they are, in my opinion, you can setup post type relationships with the post type "member", for example
- one-to-many relationship between post types "member" and "user application"
- one-to-many relationship between post types "member" and "members office records"

So in each single "user application" post, you can get the related "member" post information:
https://toolset.com/documentation/post-relationships/how-to-display-related-posts-with-toolset/#displaying-one-related-item-parent

Then display related "members office records" posts with the specific "member" post:
https://toolset.com/documentation/post-relationships/how-to-display-related-posts-with-toolset/#displaying-many-related-items

For your reference.