Booking Plus follows the same child-theme override convention as Listeo Core: copy any template from the plugin’s `/templates/` folder into a matching path under your child theme, and Booking Plus loads your copy instead of its own.
Override path
wp-content/plugins/listeo-booking-plus/templates/<path-to-template>.php
→
wp-content/themes/your-child-theme/listeo-booking-plus/<path-to-template>.php
Most commonly overridden templates
| Template | What it controls |
|---|---|
booking/modal.php |
The popup shell and step navigation. |
booking/modal-sidebar.php |
The left sidebar inside the popup. |
booking/modal-step-datetime.php |
The first step — date / time pickers. |
booking/modal-step-resource.php |
The resource picker step. |
booking/modal-step-confirm.php |
The confirmation step — guest info, attendee fields, summary. |
booking/modal-step-success.php |
The “booking confirmed” screen. |
booking/event-ticket-selector.php |
The multi-tier ticket quantity selector on Event listings. |
booking/event-booking-summary.php |
The breakdown of selected tickets and totals. |
single-listing/resources.php |
The Resources block on single-listing pages. |
single-listing/resource-card.php |
A single resource card inside that block. |
resource-submit.php / resource-list.php |
The front-end resource manager screens. |
single/recurring-event-block.php |
The occurrence picker on a recurring event’s single page. |
Things to know before you override
- Templates can change between major versions. When you override, you’re taking responsibility for keeping your copy current. After a major update, diff your override against the new plugin version and pull in any changes — otherwise you’ll miss bug fixes and feature improvements.
- Hooks first, overrides second. Many templates have
do_action()/apply_filters()hooks. If you can achieve what you want by hooking into them from your child theme’sfunctions.php, do that — you’ll survive plugin updates without diffing anything. - Don’t override
partials/unless you know what depends on them. Several partials are included from multiple parent templates; overriding one partial changes its behaviour everywhere it’s used.