You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 24, 2020. It is now read-only.
This is a big one, but eventually creates a pretty nice data model for reuse of the components.
Basically, each check-out is an individual entry with item, link, (description). Each check - out has a many to one relationship with episode and also with guest.
So a check out has the episode it is related to, as well as the guest. Then, we can easily do a query to show the check-outs for that episode for a specific guest.
Implementation is the challenge with WordPress data stuff. Having it be a metafield on episode introduces challenges as how do we assign it to the guest? Possible option is to make it a custom post type, which makes for some crazy admin overhead (having to create a post for every single check-out?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is a big one, but eventually creates a pretty nice data model for reuse of the components.
Basically, each check-out is an individual entry with item, link, (description). Each check - out has a many to one relationship with episode and also with guest.
So a check out has the episode it is related to, as well as the guest. Then, we can easily do a query to show the check-outs for that episode for a specific guest.
Implementation is the challenge with WordPress data stuff. Having it be a metafield on episode introduces challenges as how do we assign it to the guest? Possible option is to make it a custom post type, which makes for some crazy admin overhead (having to create a post for every single check-out?
The text was updated successfully, but these errors were encountered: