BookingHive – Reservation Calendar for WooCommerce

Changelog

2.1.0

• New: capacity per price period. A price-list row can now say how many seats or units it sells per day, so one product serves several customers at once — pitches, kayaks, seats on a tour. Leave the field empty and the product behaves exactly as before: one booking a day, priced per stay.
• Where a period declares a capacity, the price is multiplied by the number of seats booked. Periods without one are still priced per stay, so no existing price list changes what it charges.
• The product page shows what is left: the quantity selector cannot exceed the fewest free seats in the selected range, and a refusal says how many places remain instead of only that the dates are taken.
• Availability now counts seats rather than answering free or taken, including on changeover days: a departure day may still be someone’s arrival and an arrival day may still be someone’s departure, each up to the capacity.
• New: a “Powered by BookingHive” credit. A small grey line links back to BookingHive below the booking form on the product page, in the footer of WooCommerce customer e-mails whose order holds a booking, and in all three stay e-mails. It is rendered by default; the bookinghive_powered_by_html and bookinghive_powered_by_text filters restyle or remove it.
• Fixed: a date range longer than two days silently cleared itself after the calendar was moved to another month. The day click handler was bound a second time on every month change, and the duplicate run discarded the selection it had just made. This affected every booking product.
• Fixed: the reservations table stored prices as whole numbers, so a night priced 77.50 was recorded as 77.00. Reservations written before this release keep the truncated figure; the orders themselves were always charged correctly.
• The admin panel no longer shows the “Partners and services” tab or the partner banner above the settings tabs. Both are only hidden, not removed: the bookinghive_show_partners_tab and bookinghive_show_sitecare_banner filters bring either one back.
• Fixed: the “Book Now” tab, and with it the whole booking calendar, was added to every product in the shop, so an ordinary product offered a calendar that could never be submitted. The tab now appears only on products of type booking.
• The booking form’s fonts, stylesheet and scripts are loaded only on pages that actually show the form — a booking product or a page carrying the [ilabs_ibooking_form] shortcode — instead of on every page of the shop. A page builder that keeps its content out of the post body can force them back with the bookinghive_load_booking_form_assets filter.
• Fixed: on a server where several sites share one PHP-FPM pool and opcache with opcache.use_cwd=0, the plugin could pick up another site’s bootstrap file, and every front-end request then died with a missing-class fatal error.

2.0.1

• Housekeeping release, no functional changes. Declares compatibility with WordPress 7.1, states the licence consistently as GPLv3 or later and ships the full licence text, and moves the tested-WordPress version into readme.txt alone so it can be raised without a new release.

2.0.0

• New Reservations dashboard: stays grouped by month, totals and revenue tiles, filters by guest, order, product, status and date range, and a details modal with a per-night price breakdown and order status control.
• Stay Notifications module: reminders 14 days, 7 days and one day before arrival, plus a signed self-service cancellation link with a configurable cutoff and a confirmation e-mail.
• Spectator Views module: live viewer counts, recent-booking notices, popularity and occupancy badges with configurable thresholds, colours and product scope.
• Quantity modes: choose whether the quantity is guest information or a price multiplier, globally and per product.
• Availability and price are validated on the server when adding to the cart and before payment, so stale pages and tampered requests can no longer book occupied dates or set their own price.
• Reservation writes are serialised per product and re-checked immediately before saving, so two checkouts completing at the same instant can no longer both book the same dates.
• The booking reminder e-mail now uses the standard WooCommerce frame like the other two, greets the customer by name, lists every booked date with the product name, and counts the days until arrival with correct grammar in every language.
• The Reservations screen now shows dates, weekdays and month headings in the language of the person looking at it, while amounts follow the shop’s own currency settings — the same symbol, position and separators WooCommerce uses everywhere else, whatever language the user works in.
• Compatible with High-Performance Order Storage. The Reservations screen reads order data through WooCommerce rather than the posts tables, so customer names, the guest search and the links to orders keep working whichever storage the shop uses.
• Booking calendar redesigned around a two-month grid.
• Two customers could book the very same two days. A two-day stay consists of nothing but its arrival and departure day, and a day carrying one of those markers alone counts as available, so such a stay blocked no day at all and the shop happily sold it twice. Booking rules are now checked against the whole requested range rather than each date on its own: a changeover day may be used only in the opposite role — arriving where someone leaves, or leaving where someone arrives — and a range that swallows another guest’s stay is refused in the cart, at checkout and when the reservation is saved.
• The Week and Whole range period rules are enforced on the server, not only in the calendar. A single day of an object rented in whole weeks, or a part of a Whole range period, used to pass validation when the request bypassed the calendar; it also left the rest of that week or period unsellable as a whole, because a full period then contained an occupied day.
• Back-to-back stays are possible at last. The rule the documentation has always described — one guest may arrive on the day another leaves — was never wired up: the code marking arrival and departure days was dead, so every booked day, the departure day included, stayed blocked and the object lost a day on every changeover. It now applies to the calendar, the REST price list and the cart and checkout validation alike, and a one-day booking still blocks its day whole. Rentals needing a service day between customers can keep the whole day blocked with the new Changeover day setting, plugin-wide under BookingHive – Global settings or per product in its Price List tab.
• Paging the booking calendar to another month works again on the storefront. The month loaded by the arrows was requested without a product, so every one of its days came back unbookable; the same fault made the year select in the price list empty the list instead of loading that year’s rows.
• The week start day can now be changed on a price list row that already exists. Picking the Week rule while editing a saved row reveals the Start of period select, which until now appeared only when adding a new row — changing the weekday meant deleting the row and entering it again.
• The package now ships only the English source strings and the Polish translation. The eight abandoned translation files that had been sitting in the plugin since 2022 covered less than a fifth of the interface and left the rest of it in English mid-screen; other languages now come from translate.wordpress.org, where they can actually be kept up to date.
• Fixed the misspelled month name shown in the calendar and the price list: “Febraury” is now “February”, in the English interface and in every translation catalogue.
• Rebranded to BookingHive. The Support tab now points at the BookingHive channels: kontakt@ilabs.dev and https://bookinghive.ilabs.dev, where the user manual, the FAQ and technical support live.

1.0.1

• Details of booking in notification emails.

1.0.0

• Initial release.