Problem/Motivation

Calendars with many future openings are difficult to browse in one long list. Visitors also need to understand appointment times in their own timezone.

Proposed resolution

Add bounded availability pages, date navigation, a next-available option, and a visitor-selectable timezone. Keep availability filtering consistent with booking windows, capacity, and external busy periods.

Remaining tasks

Implement for the next minor release, add automated coverage, and verify the workflow on a local Drupal site.

Test coverage

Cover pagination boundaries, date and timezone input, daylight-saving transitions, full openings, group capacity, external busy openings, booking windows, and query-specific cache isolation.

Comments

josh.fabean created an issue. See original summary.

josh.fabean’s picture

josh.fabean
Location Florida
commented
Version: 3.1.x-dev » 3.2.x-dev
Status: Active » Fixed

Implemented and pushed to 3.2.x; available in 3.2.x-dev.

  • 030bab92: Date- and timezone-aware availability pagination and next-available filtering.
  • a1d956ac: Themeable date/timezone inputs and action buttons using Drupal render elements.
  • 69e8fb20: Shared workflow infrastructure and upgrade defaults.
  • b5fec2a6: Automated regression coverage and documentation.

Verification: full module suite passes with 91 tests and 1,984 assertions. Coverage includes paging, timezone and date filters, invalid input, full openings, clean GET query parameters, and Olivero form markup. Drupal coding standards and static analysis pass. Run database updates and rebuild caches after updating.

Adding explicit links to the implementation commits and marking fixed.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.