DayTidy 1.0.1 makes the everyday booking path clearer: offering pages do less repeated availability work, service calendars show the right end time, and selected reservations retain their individual time ranges as customers move through the form. It also corrects calendar headings, special-character display, and several administration details that can make a small task harder to understand.
This is a DayTidy Free maintenance release. Free moves to 1.0.1; DayTidy Pro remains at 1.0.0. The changes improve the existing booking foundation rather than introduce a new paid package or alter which modules belong to Pro. The version-by-version changelog is the concise reference for the release. If you are new to the product, the DayTidy 1.0.0 overview explains how offerings, resources, customer access, and optional Pro workflows fit together.
Less repeated work in recurring and multi-service bookings
An offering with a long recurring schedule can contain many possible sessions. When a customer selects several services, DayTidy also needs to check which options and resources can support those choices. Repeating the same availability work across each stage adds overhead before the customer can continue.
Version 1.0.1 reduces that repeated work on offering pages, service calendars, and transitions between booking steps. The changes include reusing availability results within the request, batching resource data, and stopping a session search when it has found the requested number of available sessions. Where a smaller initial availability check is inconclusive, the broader search remains available.
The practical benefit is a lighter path through complex offerings, not a promise that every site will load in a particular number of milliseconds. Your actual result still depends on the offering, saved bookings, hosting, theme, and other active plugins. The update does not turn an unavailable provider into an available one: resource eligibility, hours, exceptions, capacity, buffers, and reserving bookings still matter.
When checking the update, compare the same offering and service selection before and after it. Include a time that should be available and a time that should be rejected. A faster response is useful only when the booking still respects the operation’s limits.
Each service shows its own time range
A short consultation and a longer appointment can begin at the same time without ending together. Previously, a service-specific picker could display the offering session’s end time for both services, even when each had its own configured duration. That made different services appear to take the same amount of time.
In 1.0.1, a service-specific calendar uses the service’s positive configured duration to calculate its visible end. The selected-session summaries and the information, checkout, and confirmation steps use those service-specific ranges too. A selected visit retains its correct range when the customer browses a different calendar month. If the service has no positive duration override, the offering session’s end remains the fallback.
For example, suppose the offering session starts at 09:00, and the customer can choose a 30-minute consultation or a 60-minute extended consultation. The first shows 09:00–09:30; the second shows 09:00–10:00. A 15-minute cleanup buffer on the shorter service keeps its resource occupied until 09:45, but the customer-facing service still ends at 09:30. Buffers describe the time the operation needs around the visit, not extra time the customer has booked.
Review the service under DayTidy → Offerings, open the appointment’s Booking → Services controls, and compare its saved duration with the public picker. Check each service separately when a booking contains several choices. The service-duration and booking-options guide explains the relationship between the option, session, and resource rules.
Calendar headings line up with the dates
The schedule picker now uses a consistent calendar-start calculation for its weekday headings and date grid. Both honor WordPress’s Settings → General → Week Starts On setting, and weekday labels use the offering calendar’s timezone. This corrects cases where a timezone difference could shift the heading away from the dates beneath it.
Time-slot headings also use a consistent bold style when the calendar first loads, when a date is selected, and after AJAX month navigation. The purpose is simple: changing the selected date or month should not change the visual hierarchy of the same control.
After updating, compare a few known dates against their weekday headings and navigate to the next month. Check the offering’s timezone before changing a schedule to compensate for a display problem. A label correction should not require moving valid saved sessions.
Names and form values display cleanly
Ampersands and other special characters now display correctly in affected form values and offering details. This includes fields and labels across booking, resource, notification, view-builder, settings, and frontend forms, plus the relevant host, location, presenter, and sponsor output.
For a name such as Smith & Co, the reader should see the name rather than an encoded entity. The correction keeps the appropriate WordPress escaping while avoiding a second escape that exposed entity codes. You should not need to rename a legitimate business, service, or location to work around the display.
Check both the saved editor value and its public output if your offering includes these characters. Avoid replacing an ampersand with an entity manually; that can preserve the wrong underlying value rather than confirm the fix.
Clearer administration and the right help links
The first-time dashboard has a simpler presentation, and administration notices have consistent spacing from the main page content. Delete actions retain WordPress’s red styling, while deactivation-dialog close icons remain visible in their normal and hover states. These are presentation corrections; they do not change what deleting or deactivating a plugin does.
The plugin’s documentation and support destinations now point to the DayTidy documentation and DayTidy support page. Use DayTidy → Help & Support when you need to review diagnostics or find help. Redact customer details, credentials, and private calendar-feed URLs before sharing diagnostic information.
Update the Free foundation and verify one real workflow
Back up your database and files, retain a working recovery package, and try the update on staging first. Free is distributed through WordPress.org. If you use Pro, keep it active alongside Free and check its authorization and compatibility separately; 1.0.1 does not announce a new Pro release.
Free’s Webilia Connect hub manages the shared connection and licensing state. Its Download DayTidy Pro link opens My Webilia; download an eligible Pro ZIP there and install it through the WordPress Plugins screen. Free does not install Pro, and separately installed, active Pro handles its own update checks. The installation guide covers the required Free/Pro setup.
On staging, open one representative offering, select services with different durations, browse another month, and review the selected times through the booking steps. Check quantity limits as well as resource capacity: a service explicitly limited to one remains limited to one even if its resource has spare capacity. Use controlled recipients and provider test settings for any completed booking test.
The update and recovery checklist provides the backup, validation, and recovery sequence. Do not uninstall simply to replace plugin files, and leave optional permanent data cleanup disabled during routine update troubleshooting.
FAQ
Is DayTidy 1.0.1 a Free or Pro release?
This maintenance release updates DayTidy Free to 1.0.1. DayTidy Pro remains at 1.0.0; the release does not announce a new Pro version.
Does cleanup time extend the service duration shown to customers?
No. The visible range uses the positive configured service duration, or the offering session end when no override is set. Preparation and cleanup buffers extend resource occupancy separately.
Does faster availability checking make previously unavailable slots bookable?
The optimization reduces repeated availability work. Saved schedules, resource eligibility, capacity, quantity limits, exceptions, buffers, and existing reserving bookings still determine whether a selection is available.
