Webform Booking/Scheduling (Date Range Selection)

Created on 11 July 2025, 10 days ago
Updated 12 July 2025, 9 days ago

Problem/Motivation

I’d like to request considering this feature. The ability for users to select a start and end date—such as arrival and departure—and have that range checked for availability would be highly useful for booking-related use cases.

Ideally, if a selected date range has already been booked, the system should prevent further bookings for those dates. It would also be helpful if unavailable dates could be disabled in the UI to avoid user confusion.

While there are contributed modules that address some of this functionality, having native support in Webform core would make it much easier to build scheduling and booking workflows without relying on external dependencies.

This enhancement would have broad applicability across many real-world scenarios.

Steps to reproduce

The date element doesn't have a start and end data range.

Proposed resolution

Allow users to select date ranges and prevent already booked or selected dates from being available.

Feature request
Status

Active

Version

6.3

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇮🇹Italy apaderno Brescia, 🇮🇹
  • This seems better left to other modules. Does the Webform Booking module implement these features?

  • I actually mentioned that Webform Booking module in my original issue description. However, I ended up removing the reference, thinking it might have initially caused the system to flag my post as spam.

    Before creating this issue, I reviewed the module’s description and screenshots, and it looks promising—even though I haven’t installed or tested it locally yet. That’s something I plan to do soon, and I’ll report back with my findings and overall impressions.

    While I truly value Drupal contributed modules, I’ve encountered several that initially seemed like reliable, long-term solutions but were later abandoned or not kept up to date with newer versions of Drupal core. That’s always a concern when deciding whether to rely on a contributed module versus a core Drupal module.

    In this case, it’s worth noting that the contributed module doesn’t create its own form submission system or field types—it extends the already existing Webform module. Ideally, it would be great to see this kind of add-on included directly within Webform.

    Webform already supports a wide range of add-on elements, such as the autocomplete element, which I’ve recently added and am actively using. So it would also be great to have a date range element available.

    I believe a date range element—or an enhancement to the existing date element—has strong potential for widespread use, especially in scheduling, booking, and similar scenarios. Currently, when users are asked to select a specific date range using two separate date fields, there’s no built-in way to prevent multiple users from selecting the same range. This can lead to conflicts in cases where exclusive scheduling or reservations are required.

Production build 0.71.5 2024