Is there any way to associate an instance of a Pod with a particular WordPress Page or Post? Looking through the User Guide and the Q&A, I don’t see any mention of this, so I’m guessing no, but is this something that 2.0 might do?
I understand I could add a Custom Field that simply collects a Pod slug, but I really need for the user to be able to see the list of available Pod instances, like in a dropdown list or similar.
Part 1 is to create a column in the pod that contains the data of what wordpress page/post the pod is linked to:
Right now, on the Pods side of things, you can create a pick field in the pod to associate the pod record with a WordPress Page, OR a WordPress Post, but not both.
If you want to use the same pod and be able to associate it with a WP Page, OR a WP Post, you can use a textfield, where you enter the ID of the post or page.
Part 2 is to add Pods code to your wordpress page/post templates. For Pods, you’ll have to do a findRecords, and look for a Pod record where the ID that you entered in the Pod record is a match to the current page’s or post’s ID.
Thanks, but what I want to do is have the ability to select a Pod instance from a WP Page. For example, I have a Doctor Pod defined, and I’ve created a half-dozen or so Doctor instances. I’d like the user to be able to choose a Doctor to associate with each WP Page they create, so when they create a Page, they can specify which Doctor that page is associated with. Is this possible?
I guess this would be similar to being able to specify a Pod instance as a Custom Field.
I suppose you could use custom fields to do this — perhaps a custom field that contains a comma-delimited list of the slugs of the pods that you desire to associate? Alternatively, you could use custom post- or page-types that have a field that is tagged for this purpose. There are a few plugins that let you tweak the addition of different custom fields to a post.
Every time I have needed to do this, I have worked from the other direction, and maintained the list of associated pages in the pod. It just seemed like too much brain damage on my side to do a custom UI that is part of the page or post admin, when the client can be trained to make the choices on the "Doctor" side of the interface, rather than the page side of the interface.
Unless you’re talking about a site user (not a site admin) associating Doctors with pages, and then you’re just talking about integrating the publicForm into the page templates where you want to provide this functionality.