Skip Navigation

[Resolved] Series of Beta Questions

This support ticket is created 6 years, 8 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.

Sun Mon Tue Wed Thu Fri Sat
- - 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00
- - - - - - -

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

This topic contains 3 replies, has 2 voices.

Last updated by Beda 6 years, 8 months ago.

Assisted by: Beda.

Author
Posts
#626362

Hello,

I have been playing with the beta releases extensively--very exciting. I have a number of questions generally trying to figure out some best practices. I've browsed the support tickets and documentation, including the beta documentation.

1. For 1:1 and 1:m relationships, it appears there are two ways to set things up (1) the beta relationships section; (2) post relationship fields within a custom post type; and (3) in some cases, parent-child heirarchy.
-when do you recommend using a post reference field rather than a beta relationship?
--->(I notice using the post reference field only creates a field on on the CPT where the post reference field is added).
-is the parent-child heirarchy only intended for relationships between a single CPT?
-when do you recommend using repeating field groups? Eg. only if not linking to another CPT (as post references aren't permitted in repeating field groups).

2. What method can be used to display fields from intermediary post types for m:m relationships?
--I've read several support tickets saying this isn't supported in the GUI in the beta releases. Is there a way to display the information stacking views and/or content templates? Where can I find step-by-step instructions on that?
--> https://toolset.com/forums/topic/many-to-many-relationships-display-view-based-on-relationship-custom-fields/
-->https://toolset.com/forums/topic/types-beta-2-3-new-relationships-moved-out-of-post-meta/
-->https://toolset.com/forums/topic/types-views-beta/

3. Related to question 1, any recommendations for how to set up lookup values that would be used in cascading combo boxes?

4. How do you list taxonomy custom fields in a view for CPT that uses the taxonomy (eg. CPT Pickup Schedule has a Waste Stream taxonomy "WS Tax". WS Tax has a custom term field "Materials" (checkboxes). How do I display the set of checkboxes for the selected WS Tax on the layout for the Pickup Schedule CPT page?)

5. Any recommended plugins for integrating with google drive?

#626641

I see you have several questions.
I will try to reply them all here, it may though be necessary to split this up into several tickets if we cannot clarify it all at once 🙂

1. There is (strictly speaking) only one way to set up post relationships with Toolset:
- by Post Relationships

The "post-reference field" is exactly as you describe it, a field where you can pick from a list of Posts (set previously in the fields settings)
It had been requested several times in past, to allow to connect one post to another one (of either same or another type), without the need to set up a whole relationship, and allowing to cross-reference.
It is not a "Post Relationship" as the one in Post Relationships section, it is a post reference feature.

The parent-child hierarchy is a pure WordPress feature, which is natively added to pages post type already.
With Toolset, you can just as well have this on Post Types, but it is a hierarchical and WordPress based relationship.

Repeating field groups are once more something else, those are Fields, that you need to be repeated on a single post, but it's a set of fields.
It's an entire repeating group of Fields.
This is not a post-relationship, but how you add Repeating Groups of Custom Fields to Posts.

2. None. Intermediary Post Fields cannot yet be displayed, as Christian already informed you here:
https://toolset.com/forums/topic/types-views-beta/

3. I do not understand this question, and it seems rather a large topic, I suggest to ask us this in a new, dedicated ticket so we can help adequately.

4. You cannot do this.
Only taxonomy views and archives can display the taxonomy term meta fields.
This is elaborated here:
https://toolset.com/documentation/user-guides/displaying-wordpress-term-fields/

5. Not that I know of, but I am also not sure what you try to achieve with it.

There is no plugin that will integrate Google Drive and Toolset somehow.
But maybe there are plugins that integrate WordPress and Google Drive:
hidden link

Although the possible applications here are countless, hence I cannot recommend a particular one yet.

#627030

Thanks for the helpful reply! 🙂

Just a couple follow up questions.

Re: #2 - To be clear, are you saying there's no way to access the data even adding code somewhere? I understand there's no way yet built into toolset, and I have limited coding knowledge, but I was wondering if there is a way to add a function or something that pulls in that data (until toolset adds access through the GUI or shortcodes).

Re: #3 - That's fair.

Re: #5 - Yes, I've found a number of plugins that integrate WP and GDrive. My intention is to use the File custom field type to attach documents to certain CPTs, but I'd like these files to be pulled from a google team drive. I am trying to determine if I should use a plugin to make the google drive docs accessible in the Add Media section and then add toolset custom fields to the Media WP Post Type, eg. the Google Drive link. I noticed that Toolset had recommended CSV importers, so thought it best to ask if htere were any recommended plugins before exploring any setups.

#627285

Hello

Let me clarify the last 2 doubts.

1. Theoretically yes, with PHP everything is possible in this sense.
But, I could not yet even provide you with a stable code snippet, given that this is still under development.
This will be implemented soon though.

2. OK, if you wish, link me to that ticket. Then I can help 🙂

3. I understand. For this, you need 100% 3rd party Software. Toolset does not feature any such preview or even reading of Google Docs.
You can add the link, as you mention, but that will not pull the DOC itself.
This requires a 3rd party plugin, but we are not recommending any in special.