Problem
Saving an event as a template and creating a new event from it silently drops every booking-email setting.
create_from_template in buzz/events/doctype/buzz_event/buzz_event.py copies fields listed in its field_map, which covers the ticket email settings (send_ticket_email, ticket_email_template, ticket_print_format) and the sponsorship ones, but not:
The Event Template DocType has no fields for them either, so this is not a one-line map addition — the template needs the fields, create_from_template needs the mapping, and the "save event as template" side (buzz_event.js, buzz_event_list.js) needs them in its option list so an organiser can tick them.
The gap predates the offline acknowledgement: the confirmation template has been missing since it was introduced. An organiser who templates a carefully configured event gets one with default booking emails and no template link, and there is nothing in the UI to say so.
Expected behaviour
An event created from a template carries the same booking-email configuration as the event it was templated from, opt-in via the same checkbox list as the other copied groups.
Notes
buzz/events/doctype/event_template/event_template.json — add the three fields.buzz/events/doctype/buzz_event/buzz_event.py — field_map in create_from_template, plus the save-as-template path.buzz/events/doctype/buzz_event/buzz_event.js and buzz_event_list.js — the field registries behind the template dialog.- Test round-trip coverage already exists (
test_round_trip_event_to_template_to_event); extend it rather than adding a new case.
Problem
Saving an event as a template and creating a new event from it silently drops every booking-email setting.
create_from_templateinbuzz/events/doctype/buzz_event/buzz_event.pycopies fields listed in itsfield_map, which covers the ticket email settings (send_ticket_email,ticket_email_template,ticket_print_format) and the sponsorship ones, but not:send_booking_confirmation_emailbooking_confirmation_email_templateoffline_acknowledgement_email_template(added in feat(booking): acknowledge offline bookings before verification #388)The
Event TemplateDocType has no fields for them either, so this is not a one-line map addition — the template needs the fields,create_from_templateneeds the mapping, and the "save event as template" side (buzz_event.js,buzz_event_list.js) needs them in its option list so an organiser can tick them.The gap predates the offline acknowledgement: the confirmation template has been missing since it was introduced. An organiser who templates a carefully configured event gets one with default booking emails and no template link, and there is nothing in the UI to say so.
Expected behaviour
An event created from a template carries the same booking-email configuration as the event it was templated from, opt-in via the same checkbox list as the other copied groups.
Notes
buzz/events/doctype/event_template/event_template.json— add the three fields.buzz/events/doctype/buzz_event/buzz_event.py—field_mapincreate_from_template, plus the save-as-template path.buzz/events/doctype/buzz_event/buzz_event.jsandbuzz_event_list.js— the field registries behind the template dialog.test_round_trip_event_to_template_to_event); extend it rather than adding a new case.