Hi Kim,
Thank you for sharing the access details and for waiting. We had some unusually busy forum queues over the weekend.
I've reviewed the relationships and the items that you mentioned, and here are my findings:
1). Template for Single Event
This template is using a view 'organizers for event', that is showing the related 'Choruses' posts through the relationship 'Chorus Events'.
2). All Events (archive)
This archive is also using the same view 'organizers for event' for showing the related 'Choruses' posts.
3). View - Upcoming Concerts Front used on the home page
When I added this same view's shortcode ( [wpv-view name="organizers-for-event"] - screenshot: hidden link ) in the view 'upcoming concerts front' that is used on the home page, it didn't work.
I updated the query filter for the view 'organizers for event' slightly so that it looks like this:
'Select posts in a Chorus Events relationship that are a related to the current post in the loop.'
( screenshot: hidden link )
As a result, this same view is now working in all 3 sections.
- homepage
- single event pages
- event post-type archive
4). Form - Add an Event
The relationship 'Chorus Events' is of type 'many-to-many' which means that a single event can be linked/connected to multiple 'Chorus' posts.
In such a case, the relationship selection field can't be used in the form to add a new post, which in this case is the form 'Add an Event'.
You can split the process into two steps using two separate forms:
a). User will first use the form to create a new event post ( i.e. form 'Add an Event' ).
b). Once an event post has been created you can redirect the user to that event's single post page, where a relationship form can be used to connect chorus posts as needed. Here is a guide on using the relationship forms:
https://toolset.com/lesson-placement/lesson-placements-1729031-1727277/
I hope this helps and please let me know if you need further assistance.
regards,
Waqar
