Skip to content
Resrv
Esc
↑↓navigate↵open⌘Jpreview
On this page

Resrv Changelog

v6.5.4

Release date: 17th November 2026

This release fixes four search bugs. It has no migrations.

Bug fixes

  • Quantity carried over from another page: a quantity picked in an availability-search with enableQuantity stayed in the shared resrv-search session, and a search without a quantity control on a later page still priced and booked it. A room page showed and booked two rooms, a restaurant two tables, and a collection listed an entry with one unit left as unavailable. A search without enableQuantity now resets the quantity to 1 when the page loads. See The quantity on other pages.
  • Clearing a search with live off: clearing the dates reloaded the page when the search had no redirectTo. On a page with tabbed searches, the visitor landed back on the first tab. Clearing now updates the results on the page, as it does on a live search.
  • Guest counts after clearing the dates: clearing the dates also wiped the guest counts of the Guests component, while the component kept showing them. The booking then had no guest counts, and extras priced per guest charged for one. Clearing now keeps the guest counts and resets only the dates, quantity and rate.
  • Dated links and a saved rate: a link with ?date= or ?date_start=&date_end= but no rate searched only the rate left in the session from the visitor’s earlier search. After booking a 90-minute massage, a link to the spa page showed only the 90-minute option. The link now replaces the saved rate too, so it searches every rate unless it names one. See Setting the search via URL parameters.

Upgrading

Run composer update reachweb/statamic-resrv. There are no migrations. If a search’s view sets the quantity itself, such as the Guests component bound to the quantity, read Upgrading to v6.5.4.

v6.5.3

Release date: 16th November 2026

This release fixes four checkout and payment bugs. It has no migrations and no interface changes.

Bug fixes

  • Retrying a failed payment: the checkout-complete page ended the checkout on every return, including a failed payment, where it asks the customer to try again. Going back to the checkout then showed “Reservation not found in the session”, and the customer’s own hold kept the dates unavailable until minutes_to_hold passed. A failed return now leaves the checkout open, so the customer can go back and pay, and a new search releases the hold. Successful and pending returns end the checkout as before. See Checkout complete.
  • A payment gateway that fails to load: with multiple gateways, one that couldn’t be loaded, for example with missing credentials, returned a 500 error at the payment step for every customer, including those paying with another gateway. It’s now left out of checkout and reported to your exception handler. If no gateway is left, checkout shows the new noGatewayAvailable message.
  • Payment amount decimals: the Stripe and offline payment views showed “€ 316.8” for a €316.80 payment and “€ 50” for €50.00. They now show the currency’s decimals, such as “€ 316.80”, and none for currencies like the yen.
  • PayPal refund ids are now written to the “Gateway refund processed for reservation.” log entry. They were logged as null.

For custom payment gateways

  • What handleRedirectBack() should return: a false status now leaves the checkout open for another try. Return false when the customer has to act again, such as a declined or abandoned attempt, even if the provider keeps the payment open. Return 'pending' only when the payment completes without them. See Handling the redirect back. The Mollie add-on does this from v2.0.2.

Upgrading

Run composer update reachweb/statamic-resrv. There are no migrations. Upgrading to v6.5.3 covers the new translation key, the two payment views and custom gateways.

v6.5.2

Release date: 15th November 2026

This release fixes a data exposure on the checkout-complete page and adds one migration, so read Upgrading to v6.5.2 before you deploy.

Security

  • Other bookings’ data on the checkout-complete page: the page loaded whichever reservation ?payment_pending=<id> named. Reservation ids are sequential, so on a site whose template renders the reservation data, a visitor could read another booking’s reference, dates, amounts, payment id and entry. Customer names and emails weren’t included. The data now goes only to the session that made the booking, for 60 minutes after it completes, and anyone else sees the pending message without it. Pages that render {{ resrv_checkout_redirect }} are no longer written to Statamic’s static cache.
  • Custom payment gateways: most custom gateways copied the same lookup into handlePaymentPending(). The tag now filters what any gateway returns, but replace the method body with return PendingPayment::fromRequest(); anyway. See Handling the redirect back.

Improvements

  • Payment page with bank-hosted providers: some providers, such as Cardlink and other bank payment pages, can’t cancel an order the bank hasn’t answered yet. On the payment page, every Pay press then failed with a generic error until the bank’s page timed out. A gateway can now report when the open order expires, and the page tells the customer they can try again after that time. See Retrieving a payment intent.
  • Updated booking calendar to @reachweb/alpine-calendar v1.4.1. The date picker now fits narrow phone screens, closes with Escape, keeps the page behind it from scrolling and no longer submits a surrounding form from its buttons.

Bug fixes

  • Free cancellation after its deadline: availability results and the checkout offered “Free cancellation until <date>” even when that date had already passed, for example on a check-in 3 days away with a 7-day window. They now show “No free cancellation for these dates”. A booking keeps the label as it stood when it was confirmed, so emails and the status page show the terms the guest booked. See Rates.

Upgrading

Run composer update reachweb/statamic-resrv and php artisan migrate before the site serves traffic. If you use static caching, clear it once with php please static:clear. Upgrading to v6.5.2 covers the new translation keys and the payment page view.

v6.5.1

Release date: 14th November 2026

Bug fixes

  • Stale “Search error” next to valid results: with Livewire 4.4.8 or later, the availability results, availability collection and multi-rate cart components could show “Search error: The dates field is required.” next to valid results after a visitor picked dates. An earlier error such as “Please select a rate before proceeding.” could also stay visible after a new search. Every new search now starts without earlier errors. Customised views get the fix without republishing.

Upgrading

Run composer update reachweb/statamic-resrv. There are no migrations and no other upgrade steps.

v6.5.0

Release date: 14th November 2026

This release adds manual reservations, a per-rate Booked units per add-on setting and a fix for payment webhooks on Laravel 13. Custom payment gateways must be updated in the same deploy, so read Upgrading to v6.5.0 first.

New features

  • Manual reservations: create bookings with the new Create reservation button on the Reservations listing. You can request the Checkout amount, the Full amount or a Custom amount, override the total, credit an affiliate, or Overbook anyway when stock runs short.
  • New Awaiting payment status: a manual reservation that collects a payment starts as Awaiting payment (awaiting_payment) and holds availability until paid or cancelled. Use Mark as paid, Send payment request, Extend hold or Cancel reservation from the listing or the reservation page.
  • Payment page: the new reservation-payment Livewire component is where customers pay from the payment request email, without logging in. It resumes an interrupted payment and shows your Offline Payment Instructions for offline methods.
  • Payment deadlines: hold a manual reservation for 1 to 365 days and it’s cancelled automatically if still unpaid. The new resrv:cancel-lapsed-holds command does the cancelling and must be scheduled.
  • Payment request emails: a new Customer payment request email event, on by default, with the amount, any deadline and a Pay now button. It’s sent when you create a reservation, from Send payment request and optionally from Extend hold.
  • Calendar, reports, activity log and export: awaiting-payment bookings show on the reservations calendar with a dashed style, and Reports gain an Outstanding payments card. The activity log records Control Panel bookings, and the export can include Awaiting payment.
  • Booked units per add-on: a new per-rate field that sets how many booked units count as one when pricing extras and option values. Set it to 2 on a rate that books a 2-berth cabin as quantity 2, and a fixed 350 port tax is charged 350 instead of 700.
  • Add-on prices in availability results: Extras and Options in the availability results now price against the rate the results resolved. Customised availability-results.blade.php views should pass the new effectiveRateId to both (see Rates).

Improvements

  • Reservations listing: the status filter now defaults to Confirmed, Partner and Awaiting payment.
  • Permissions: the existing Use Statamic Resrv permission now also covers creating reservations, marking them as paid, sending payment requests, extending holds and cancelling unpaid reservations.
  • Availability edits: awaiting-payment holds don’t block count changes, but they block deleting their availability or their entry. The error for a blocked count change now names the checkouts in progress.
  • Clearer refunds of offline payments: offline checkout bookings show Payment instead of Paid, and refunding a booking that wasn’t paid online now reminds you to return the money yourself.
  • Payment reconciliation alerts: the orphaned-payment email to admins now also fires when a payment lands on a Cancelled reservation, such as a hold that lapsed while the customer was paying.
  • Email wording: confirmation emails say “Amount already paid” instead of “Already paid by credit card” when nothing was charged online, and show the payment rows whenever less than the total was paid. The customer cancellation email labels its date row “Cancelled on”.
  • Control Panel: reservation dates show their time zone, and status names in filters, badges and the export dialog are now translated.
  • Updated booking calendar to @reachweb/alpine-calendar v1.3.0.
  • For developers: ReservationConfirmed gained VIA_CP and a $notifyCustomer flag. ReservationCancelled gained a $context (hold_lapsed, unpaid_hold or payment_in_flight) and a $notifyCustomer flag, which listeners that email customers should honour.
  • New columns: payment_unresolved marks a payment_id kept only for reconciliation, so don’t treat payment_id !== '' alone as revenue. Read an extra’s line total from the new total pivot column with Extra::priceFromPivot(), which falls back to price times quantity.

Bug fixes

  • Payment webhooks on Laravel 13: providers’ webhook calls were rejected with a 419 error, so payments never confirmed. The routes are exempt from CSRF again, and you can remove any preventRequestForgery(except: [...]) workaround.
  • Extras required by a category condition (Extra in category is selected or No extra in category is selected) are now enforced when the checkout is submitted. Before, they only showed as required.
  • Relative rates: frontend calendar prices on relative rates no longer show NaN.
  • Multi-cart checkout: a stale add-on price in the session no longer causes a dead-end “reservation changed” error when checkout loads. If you worked around this or the relative-rate issue, you can remove the workaround.
  • Option value descriptions are no longer dropped when you save an option in the Control Panel.

Breaking changes

  • Custom payment gateways: paymentIntent() gained a 4th parameter, ?string $returnUrl = null, and retrievePaymentIntent() is a new required method. Without them a gateway fails to load and breaks checkout, webhooks and the Control Panel reservation pages. verifyPayment() must also confirm awaiting_payment reservations. See Upgrading and the Custom payment gateway guide.
  • New enum cases: ReservationStatus::AWAITING_PAYMENT and ReservationEmailEvent::CustomerPaymentRequest. An exhaustive match over either enum throws UnhandledMatchError until it handles the new case.

Upgrading

Run composer update reachweb/statamic-resrv and php artisan migrate, and update custom payment gateways (and the Mollie or PayPal add-on) in the same deploy. Then schedule resrv:cancel-lapsed-holds. Upgrading to v6.5.0 covers the rest: the payment page, cache locks and customised views and translations.

Booked units per add-on is empty by default, so nothing changes until a rate sets it.

v6.4.0

Release date: 10th August 2026

New features

  • statuses parameter on the reservation_from_uri tag: choose which statuses the tag looks up with a pipe-separated list such as statuses="confirmed|partner|refunded". The default is Confirmed and Partner.

Bug fixes

  • Partner bookings on customer pages: the tag now finds partner (skip-payment) bookings, so affiliate reservations no longer return a 404 on pages built on it.
  • Themed error pages: a missing, invalid or unknown reservation link on a page that uses the tag now shows your site’s 404 template instead of a bare error page.

Upgrading

Run composer update reachweb/statamic-resrv. There are no migrations. If a page relied on the tag returning only Confirmed bookings, add statuses="confirmed" to it.

v6.3.0

Release date: 15th July 2026

This release tightens the affiliate system and adds quantities to the Reports page.

Improvements

  • Quantity sold in Reports: the Best sellers panel on the Reports page gains a Quantity sold column next to the reservation count.
  • Turning affiliates off turns the whole system off: with Enable affiliates off, Resrv no longer sets affiliate cookies, credits affiliates, lets them skip payment or sends affiliate emails. Existing attributions are kept for reporting and refunds.

Bug fixes

  • Skipping payment is limited to affiliate links: a coupon tied to an affiliate still credits the affiliate, but no longer lets the customer skip payment, since coupon codes can be shared publicly.
  • Unpublished affiliates: a coupon tied to an unpublished affiliate still applies its discount, but no longer credits the affiliate with a commission.
  • Partner reservations in the Control Panel now say “No payment collected (partner reservation)” instead of showing a payment amount that was never charged.

Upgrading

Run composer update reachweb/statamic-resrv and php artisan migrate. The migration adds a source column (link or coupon) to resrv_reservation_affiliate and marks existing rows as link attributions.

v6.2.1

Release date: 12th July 2026

Bug fixes

  • Custom Control Panel route: Resrv’s Control Panel screens now respect a custom CP_ROUTE instead of always calling /cp, so they load and save data on sites with a different path.

v6.2.0

Release date: 12th July 2026

This release adds a customer-facing reservation status page with self-service cancellations, and a new terminal cancelled reservation status.

New features

  • Reservation status page: a new reservation-status Livewire component where customers look up their booking by email and reference, or open it from the “Manage your booking” link in confirmation emails. Enable it under Resrv → Settings → Checkout.
  • Customer cancellations: customers can cancel from the status page, with an automatic refund inside the free cancellation window. After that, or under a non-refundable policy, they cancel without a refund. Offline gateway and partner bookings are view only.
  • New cancelled reservation status: refunded now only means the gateway returned the charge. No-refund cancellations and voids of bookings that were never charged get the new terminal cancelled status.

Improvements

  • Reports: cancelled bookings that kept their payment now count toward reservation totals, revenue, best sellers and affiliate commissions. Refunds and no-charge voids stay excluded.
  • Affiliate commissions follow the money: refunding a reservation voids its commission, and a no-refund cancellation keeps it payable. Commissions of reservations refunded before this release are backfilled on migrate.
  • Safer refunds: if a reservation’s payment gateway is no longer configured, refunding it fails with a “handle manually” error instead of going through the current default gateway. Stripe refunds also handle charges already refunded from the Stripe dashboard.
  • Lookup hardening: reservation lookups are rate limited per reference and per IP, and failed deep links fall back to the form with a neutral notice.

Breaking changes

  • Custom payment gateways: PaymentInterface gained supportsAutomaticRefunds(): bool, and a configured gateway without it fails to load. Return true only if your refund() returns the money through the provider’s API, and false for gateways like bank transfer. See Refunds.

Upgrading

Add supportsAutomaticRefunds() to any custom payment gateway, then run composer update reachweb/statamic-resrv and php artisan migrate. Both new toggles are off by default. If your code matches on the refunded status string, handle cancelled too.

v6.1.0

Release date: 3rd July 2026

This release adds new reports, an activity log and a database housekeeping command, plus many fixes. See Upgrading from v6.0.0 to v6.1.0.

New features

  • Database housekeeping command: the new resrv:housekeeping command clears long-expired reservations, orphaned customer details and past availability. It takes --days (default 30) and --dry-run, and you need to schedule it.
  • Affiliate & dynamic-pricing reports: the Reports page gains an Affiliates section (reservations, sales and commission per affiliate) and a Dynamic pricing section (how often each rule was applied).
  • Resend confirmation email: a new action on the reservations listing resends the customer’s confirmation email, even if confirmation emails are disabled or routed to admins.
  • Activity log: an optional log of every availability, price and reservation status change, with the reason. Enable it under Reservation settings → Enable activity log and prune it with --log-days (default 365) on resrv:housekeeping.
  • Deep-linkable search: pre-fill the availability search from URL query parameters such as ?date=YYYY-MM-DD, ?date_start=…&date_end=… and ?rate=<id> (or ?rate=any). Invalid values are ignored, and it works with multiple search bars on a page.

Improvements

  • Self-healing rate selections: availability components now drop a stale rate from the search session and auto-select the only valid rate. This replaces the resetOnBoot attribute, which has been removed (see Upgrading).
  • Clearer rates in the availability calendar: relative and shared rates are labelled, read-only cells show a lock icon, and dates missing a price are flagged “Price required”. Editing a shared rate pulls in the base rate automatically.
  • Smarter bulk availability editing: the bulk-edit modal disables fields that don’t apply to the selected rates, applies each value only to the rates that accept it, and saves multi-rate edits atomically.
  • Reports survive deletions: deleting an affiliate now soft-deletes it, and report rows for deleted affiliates and dynamic pricing rules stay, marked as deleted.
  • Faster dynamic pricing screen: the listing now stays fast as the number of rules grows.
  • Updated booking calendar to @reachweb/alpine-calendar v1.2.0, with more reliable timezone handling.

Bug fixes

  • Duplicating a Statamic entry no longer copies the original’s availability.
  • Translated entries now always use the root entry’s availability and pricing, even across chained translations.
  • Date picker timezone: visitors whose browser timezone is ahead of the server no longer see their selected check-in / check-out dates shift a day earlier.
  • Frontend calendar conflicts: the frontend bundle no longer leaks into the global scope, which caused an “L is not a function” error on pages that also load Leaflet or similar libraries.
  • Pending reservations: abandoned, past-window holds no longer block availability edits, and saving or deleting availability in the Control Panel no longer expires valid in-progress checkouts or confirmed bookings.
  • Confirmed bookings no longer block availability edits: you can now change the price and count on dates with confirmed or partner bookings. Only in-progress checkouts block a count change, and active bookings still block deleting availability.
  • Dynamic pricing rules show their assigned entries again instead of “Unknown entry”, including entries that don’t have availability set up yet.
  • Refund emails now show the actual amount charged to the card (including any payment surcharge) and no longer claim a refund for bookings that were never charged.
  • Reservation emails (confirmation, made and abandoned) no longer error when the booked entry or a selected option has since been deleted. They still send, with the originally booked details.
  • Email theme: a partially published or empty email theme folder no longer drops the logo header, because the packaged theme is used as a fallback.
  • Bulk rate updates: updating several rates at once, or with invalid dates or day-of-week filters, returns a clear validation message instead of a 500 error.
  • Empty listings: a rate assigned only to a disabled entry no longer leaves a collection listing empty.
  • Deleting an extra now also removes its entry assignments instead of leaving orphaned rows behind.
  • Control Panel polish: the duplicate “Use Resrv” permission is gone, and dark-mode badges, the Refund action icon and the info alerts on Resrv fields display correctly.

Upgrading

Run composer update reachweb/statamic-resrv. If any template passes :resetOnBoot to the availability-search component, remove it, because the attribute no longer exists. See Upgrading from v6.0.0 to v6.1.0 for the checklist.

v6.0.0

Release date: 6th June 2026

This is a major release with breaking changes. Please read the Upgrade Guide and back up your database before upgrading.

Resrv v6 moves the add-on to Statamic 6, adds the new Rates system and multiple payment gateways, and rebuilds the Control Panel.

Requirements

  • PHP 8.4+
  • Laravel 12 or 13
  • Statamic 6
  • Livewire 3.6.4+ or 4

New features

  • Rates: collection-scoped rates replace the old per-entry “advanced availability” and “connected availabilities”. A rate can have independent or relative pricing, independent or shared inventory, date and stay restrictions, its own cancellation policy and selected entries.
  • Multiple payment gateways: offer several payment methods at checkout, including a built-in offline gateway for bank transfer or pay at premises, with per-gateway surcharges, amount limits and webhooks. You can also build your own gateway.
  • New frontend components: availability-collection lists available entries for a whole collection, availability-multi-results adds cart-based booking of several rates or dates, and availability-list lists upcoming available dates.
  • Settings in the Control Panel: business, reservation, checkout, email and currency settings now live under Resrv → Settings, and config/resrv-config.php keeps only developer keys. php please resrv:settings:migrate moves your old values into the Control Panel.
  • Email customization: set recipients, subject, from address and template per event and per checkout form, and send opt-in abandoned-reservation recovery emails. The Logo field now shows in emails automatically.
  • Per-rate cancellation policies: set a free cancellation window or mark a rate as non-refundable. The policy is shown to the customer and saved with the reservation.
  • CSV export: export reservations filtered by date range, status and columns, with custom checkout fields included.
  • Reports can now run against the booking-creation date as well as the reservation date.
  • Minimum and maximum dynamic pricing rules: clamp the final price to a floor or ceiling, applied after all other rules and coupons (and to extras).
  • The frontend calendar moved to @reachweb/alpine-calendar and the Control Panel was rebuilt on Statamic 6 (Vue 3 + Inertia + Tailwind v4).

Breaking changes

  • Requires PHP 8.4, Laravel 12 or 13, Statamic 6 and Livewire 3.6.4+.
  • The property column, advanced_availability and connected_availabilities are removed and replaced by Rates. Run php artisan resrv:upgrade-to-rates after migrating.
  • Custom payment gateways must implement five new PaymentInterface methods.
  • CP-managed settings move out of config/resrv-config.php into the Control Panel.
  • Published frontend views (e.g. availability-advanced → availability-rates), language overrides and the calendar’s CSS variables changed.

Upgrading

Follow the full Upgrade Guide. In short: back up your database, bump your requirements and run composer update, run php artisan migrate, run php please resrv:settings:migrate and php artisan resrv:upgrade-to-rates, then update any published views, language files and custom payment gateways.

v5.0.0

Release date: 5th Dec 2025

This release contains breaking changes please read follow the release notes to upgrade existing Resrv installations.

New features

  • Totally rewritten Extras and Options functionality. Instead of using Blade components this functionality has now been moved into their own Livewire components. This minimizes use of JavaScript in the frontend and results in faster and more secure functionality.
  • Added a new “days of the week” setting in the Mass Availability modal that allows you to only apply the changes in specific days of the selected range.
  • Added a new availability-results-advanced Blade component that you can use to display all the possible advanced properties and their availability / pricing.
  • Added a new Cutoff field that allows you to set a specific start time and schedule for each entry and set a cutoff time in hours after which reservations are no longer possible.
  • Added more robust connected availabilities rules.
  • Changed the $resetAdvancedOnBoot property of AvailabilitySearch to $resetOnBoot and it now also resets the quantity and triggers a search.
  • Moved the customer data into a separate Customer model and database table. This will help us create account functionality in the future.
  • Moved the availability calendar into a popup in order to provide much better mobile support.
  • Removed the need for the Resrv Availability field to have the “resrv_availability” handle in the Statamic blueprints.
  • Added a “when extra is NOT selected” condition rule to show / hide / require an extra if another extra is NOT selected.
  • Added extra category conditions to show / hide / require extras based on categories.
  • Added support for wildcard coupons using * to apply coupons to all entries.
  • Added affiliate - coupon relationship to connect affiliates with coupons.
  • Added the ability to close the calendar popup with the Esc key.
  • Added support for multiple webhook secrets in the payment gateway configuration.
  • The payment gateway now passes the public key through for easier frontend configuration.
  • Email templates now use the configured logo.
  • Made the calendar input readonly to prevent manual text input.
  • Use override label in emails and frontend if set.

Bug fixes

  • Fixed some countries not appearing in the phone codes field of the checkout form.
  • Fixed some issues with reservations made on the current day for the same day.
  • Fixed an issue where coupons wouldn’t update the total if applied after step 1.
  • Fixed affiliate removal when coupon is removed.
  • Fixed wildcard coupons on update event.
  • Fixed Resrv tag getting schedule for wrong entry.
  • Fixed reverse condition for extras.
  • Fixed wrong email getter.
  • Fixed refund emails being sent multiple times.
  • Various other fixes you can find in GitHub.

Upgrading

  • Make a backup of your database.
  • Migrate your database by running php artisan migrate
  • The resrv_customers table should now have your customer data. This should be handled automatically by the migration but please check your database afterwards.
  • There are major changes in Resrv’s frontend views: if you were overriding those you need to manually upgrade the following views:
    • checkout.blade.php - needs to be upgraded to use the new Extras and Options components. Check the file in this release to check what needs to be changed.
    • availability-results.blade.php - also needs to be upgraded to use the new Extras and Options component - even if you had not enabled them here.
    • Also in availability-results.blade.php you need to add the section for displaying the cutoff feature error if you use it.
    • checkout-extras.blade.php and checkout-extra.blade.php - These have been completely replaced by extras.blade.php and extra.blade.php
    • checkout-options.blade.php and checkout-option.blade.php - These have been completely replaced by options.blade.php and option.blade.php
    • If you were using availability-extras.blade.php or availability-options.blade.php they also need to be upgraded.
    • checkout-payment-table.blade.php needs to be upgraded to use the new Extras and Options objects. Also check the changes in this release.
  • You also need to update your email templates (again if you were overriding those). We have tried to respect backwards compatibility here but changing the following in all email templates is best practice:
    • Any mention of $reservation->customer->get('email) should now be $reservation->customer->email.
    • Replace $reservation->customer->count() > 1 with $reservation->has('customer')
    • Replace @foreach ($reservation->customer as $field => $value) with @foreach ($reservation->customerData as $field => $value).

v4.1.0

Release date: 18th Mar 2025

  • Laravel 12 support
  • Added a fix for the new country code dictionary so that it can be used in regular Statamic forms and pass the value to the email template correctly.
  • Cleanup of unused database columns and tables.

v4.0.1

Release date: 1st Mar 2025

  • Fix issues with diffInDays method changing in Carbon v3.

v4.0.0

Release date: 28th Feb 2025

  • New frontend calendar based on Vanilla Calendar Pro.
    • Added the capability to display price and availability per day inside the calendar itself.
    • The calendar now respects minimum and maximum durations and doesn’t allow the user to select an unsupported range.
  • New extra categories feature: your extras can now belong to categories.
  • Extras are now using the Entry model to associate themselves with Entries.
  • Extras are no longer editable inside an Entry using the resrv_extras field.
  • Full conditional extras support (Show / hide or require extras based on conditions).
  • New phone dictionary (both frontend and backend) for the checkout form that displays country phone code select box plus a text input for the phone number.
  • Added a resrv:import-entries command that can be used to sync the site’s Entries to Resrv’s database.
  • Improved extension’s config display in the control panel and various panels.
  • Upgraded the Stripe library to the latest version.
  • Various small bug fixes.

Upgrading

  • Make a backup of your database.
  • Migrate your database by running php artisan migrate
  • The resrv_statamicentry_extra table is being replaced by the resrv_entry_extra table. This should be handled automatically by the migration but please check your database afterwards.
  • There are major changes in Resrv’s frontend views: if you were overriding those you need to manually upgrade the availability-search.blade.php, checkout-extras.blade.php, checkout-extra.blade.php files (and possibly more like the dictionary fields).

v3.2.0

Release date: 1st Oct 2024

  • Removed all the legacy API endpoints, controllers and more.
  • Added more tests to cover scenarios that were tested from the API endpoints.
  • Fix an issue that when a date range would contain the date that Daylight saving starts, the duration would be a day less.

v3.1.0

Release date: 18th Sept 2024

  • NEW Added support for Dictionaries in your checkout forms so that you can easily add selects with many options, like Countries.
  • NEW New AlpineJS component for dictionaries, with filtering.
  • FIX The select field was not working on checkout forms due to some changes from Statamic’s side.
  • FIX Calendar and Reports will now show and take into account accordingly partner reservations. (made via the affiliate system).

Upgrading

Please note that if you have already overridden the Resrv views you will need to copy the file dictionary.blade.php from views/livewire/component/fields to your views/vendor/statamic-resrv folder.

v3.0.1

Release date: 9th Sept 2024

  • Fixed an issue when at the first save of an Entry that had a Resrv Availability field as “disabled” the value would not get saved thus making the Entry available to reserve.
  • Fixed two issues with Fixed pricing.
  • Updated the documentation URL and added the logo.

v3.0.0

Release date: 3rd Sept 2024

  • Disabled legacy endpoints be default.
  • Removed support for Statamic 4.
  • Fixed some icons in dark mode.
  • Small fixes in Livewire components.
  • Improved the LfAvailabilityFilter component so that it requires less properties.
  • Added the live-availability data in the entries when using the regular Collection tag via a Hook.

Was this page helpful?