Booking entry like the front end, only faster.
A "New booking" button sits right in the DPCalendar booking overview. You get the complete booking form: ticket types with prices, booking options, status, booking date and every custom field of your DPCalendar installation, including field groups and required fields. Prices, ticket limits and remaining capacity are calculated by DPCalendar itself; occupancy is carried forward correctly and any reduction is reported clearly. For paid events you assign the payment method (bank transfer, for instance) directly, with no detour through a payment service. Recurring events are handled properly — the whole series or one single date, depending on the event's setting.

Find events instead of searching for them.
A clear list of every bookable event with date, calendar and occupancy, filtered by search term, calendar, location and period. Fully booked events with a waiting list stay bookable, clearly marked, with the booking status "waiting" preselected so nothing is overbooked by accident.

Several users in one run.
Pick users by name, username or e-mail — each one gets their own complete booking. In the "personal details per user" step you fill in every booking field for each person individually, prefilled from their account and Joomla profile. Saving is all-or-nothing: the bookings are created only once every required field is complete for every person, so half-entered groups cannot happen.

Guest bookings, with an account if you want one.
Bookings without a user account, using freely entered contact details. On request the plugin creates a Joomla account along the way and links it to the booking — even with mail sending switched off, in which case access comes later through "forgot password". Mail sending is switchable per plugin: send the regular DPCalendar booking mails, or suppress them entirely for backend bookings.

Controlled and guarded.
Only events from calendars you have explicitly released are bookable. Access follows the DPCalendar permissions ("create bookings for other people", the calendar's "book" permission) — without them there is neither a button nor any booking page. Every step is checked server-side: calendar release, ticket amounts, required fields. A bundled template override shows the booked date next to every booking in the overview; it installs automatically, refreshes on update and is removed without trace on uninstall, leaving your own overrides untouched.

A single, lean plugin — no database tables of its own, all bookings live in the regular DPCalendar tables. Requires DPCalendar Pro 10.11.x with the booking system; the installer checks that DPCalendar is present before installing.