Parent Child Events Stage 1
This work is being done to help the Joomla community support their larger events like the upcoming Melbourne Joomla Day.
Create a new relationship between events so we can support larger events with seperate sessions inside the event.
1.) Display a summary of the child event/s and selection on the Parent Event page.
2.) On rollover of the child event summary, display the event details.
3.) Upon ading each child event to the parent event, the admin is to be asked to choose if the child event is to be a general of forced cross sale. General Cross sales are just offers to the customer. Forced Cross sale must be selected.
4.) Once the child events are added the admin is to be requested to choose how many Forced Cross sale child events must be selected. Stage 2 will include more detailed Child event rules.
5.) Allow the admin to define if booking a seat in the child event is optional or forced.
Please note:
6.) Do not allow the user to book into child events starting at the same time.
7.) If the customer is forced to select a child event, do not allow them to move to purchase until at least one child event is selected.
8.) Do not allow events with multiple sessions to be child or parent events in this stage. Stage 2 will add various higher level features.
Blueprint information
- Status:
- Not started
- Approver:
- Damian Hickey
- Priority:
- Undefined
- Drafter:
- Damian Hickey
- Direction:
- Needs approval
- Assignee:
- Damian Hickey
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Some changes related to how the Adition of Parent and Child Events should occur in the Admin Tool:
I think it would be a mistake to change the standard admin template for this by adding a “P” for Parent next to the edit button for the events. This would make maintaining the template a lot harder and lead to other strange changes. We should use the tabs in the event creation/
It would be much better to change the "Subscriptions" tab in the event creation process to "Linked Events". Remove the "Child Events" tab and add its features to the new Linked Events tab below the Linked Subscriptions feature.
Change to a series of questions: Checkbox displayed as " Do you want to link this event?". If ticked, it would open out another question: "What type of link would you like?" and show the choices: "Linked Subscription, Parent Event or Child Event".
If Lined Subscription is chosen, it would show the current Linked Subscription feature.
If Parent Event is chosen, it would ask if it was to be General or Forced. It would then ask what the Child Events were.
If Child Event where chosen, it would ask, what the Parent Event was to be.
Adding an extra Child Event tab is confusing because it only manages the child. What we are doing is creating relationship between events. This is the logical linkage which should determine the menu structure.
