DIGITALYSATOR BOOKING SLOTS · DOCUMENTATION
Stable booking blocks, reliable availability and separate rental and buffer periods for WooCommerce and PH Bookings.
This user manual covers version 0.1.14 (pre-release) for PH Bookings Premium 6.1.0. It is based on the plugin README. Updated: 19 November 2026.
Features and booking workflow
Digitalysator Booking Slots is an independent must-use extension for PH Bookings. It preserves a fixed grid of hourly or minute-based booking blocks. Reserved blocks and blocks closed by rules remain visible. Rental time and the buffer time required before or after it are evaluated separately.
- Open a booking product and select an available day. Days without a bookable start are greyed out.
- Select the first and last rental blocks. The rental ends at the end of the last selected block.
- Check the duration, price and resource, if applicable, then add the booking to your cart.
- Availability is checked again on the server in the cart and at checkout. A time shown as available is not yet a completed reservation.
The extension works alongside WooCommerce and PH Bookings. Pricing rules, opening hours and basic product settings are managed by PH or WooCommerce.
Requirements and installation
- PHP 8.1 or later, WordPress, WooCommerce and PH Bookings Premium 6.1.0.
- PH’s availability table must already exist. The database account must have permission to add the archive column.
- PH WooCommerce Product Addons is optional. Third-party plugins are not included in the installation package. Compatibility with other PH versions has not been confirmed.
- Back up your database and existing MU-plugin files. Test the installation on staging first.
- Use the release installation package
digitalysator-booking-slots-0.1.14.zip. GitHub’s automatically generated source archive is not an equivalent installation package. - Extract the ZIP directly into
wp-content/mu-plugins/. This directory must containdigitalysator-booking-slots.phpnext to thedigitalysator-booking-slots/folder containing the PHP files, JavaScript and translations. - Check for “Digitalysator Booking Slots” under Plugins → Must-Use. WordPress loads MU plugins automatically. There is no Activate button; the package is not installed with the normal plugin ZIP uploader.
- Confirm that the archive column was created successfully and review the settings of the affected booking products.
Product configuration
Go to Products → Edit product and open the product’s PH booking settings. The additional buffer controls appear beside Buffer Time. The question-mark tooltip next to the calculation selector explains the two modes.
| Setting | Purpose and use |
|---|---|
| Interval and time unit (PH) | Choose hours or minutes and the length of a block, for example four hours. The grid retains PH’s configured start positions. |
| Opening hours and availability rules (PH) | Define allowed start times, weekdays, date rules and closed periods. A visible boundary block can still be disabled because of its end time or an availability rule. |
| Minimum duration, lead time and booking window (PH) | Set how long and how far in advance customers can book. These settings work together with the availability checks. |
| Product capacity and resources (PH) | Set the available units and any assets shared between products. The extension includes these in its occupancy checks. |
| Buffer Time | Enable this when time must be protected before or after a rental. When disabled, no additional buffer is required. |
| Buffer calculation | Choose “Duration (absolute)” or “Number of blocks”. Absolute duration is the default if no mode has been saved. |
| Duration before/after rental (PH) | In absolute mode, use PH’s existing before/after values and time unit. Configure each side separately. |
| Blocks before/after rental | In block mode, use the two additional whole-number fields. Zero means no buffer on that side. Negative or fractional values and values outside the supported integer range are rejected. |
| Allow overlapping buffers | Available in both modes and enabled by default. Determines whether pure buffer periods between rentals may be shared. |
Save the product after making changes. Settings are product-specific. Existing bookings retain their stored boundaries; new settings do not retroactively recalculate them.
To get started, configure the interval, rules and capacity first. Then enable buffers, choose a mode and values, and decide whether buffers may overlap. Check a free day, an occupied day and a booking near closing time.
Buffer calculation
Duration (absolute)
The buffer runs as elapsed time, including nights, closed days and weekends. One buffer day is exactly 24 hours, even across daylight-saving changes. Values come from PH’s existing before/after buffer fields.
Number of blocks
This mode counts actual positions in the product schedule. Periods closed by availability rules are skipped. Already reserved blocks still count; they are not skipped. The subsequent conflict check determines whether the occupancy is allowed.
The search covers up to 366 calendar days in either direction. This is a search horizon, not a maximum block count. If the requested number cannot be found within this horizon, the affected booking start is unavailable.
Example: eight hours or two blocks?
Assume that only the blocks 08:00–12:00, 12:00–16:00 and 16:00–20:00 are eligible. The rental is 16:00–20:00, with no before buffer.
| After buffer | Occupancy ends | The following day |
|---|---|---|
| 8 elapsed hours | 04:00 | 08:00–12:00 is potentially available again. |
| 2 eligible blocks | 16:00 the next day | 08:00–12:00 and 12:00–16:00 are buffer time; 16:00–20:00 is potentially available. |
The following rental’s own before buffer is also checked. Other bookings, capacity and rules may impose additional restrictions. This example does not redefine PH’s opening or boundary settings.
How buffers work
Eight hours are not always two blocks.
This simplified example has three bookable four-hour blocks per day: 08:00–12:00, 12:00–16:00 and 16:00–20:00. A rental ends at 20:00. No buffer before the rental is configured here.
Buffer as an absolute duration
An eight-hour buffer after the rental ends at 04:00 the following day. Nights, closing hours and weekends count towards it. The next rental can start at 08:00, provided no other rules or bookings prevent it.
16:00–20:00
Rental
20:00–04:00
8-hour buffer
04:00–08:00
Closed
Day 2 · 08:00–12:00
Available again
Buffer as a number of blocks
Two buffer blocks count actual positions in the schedule. Times closed by availability rules are skipped; already reserved blocks still count. In this example, the first two blocks of the following day are therefore buffer time.
Day 1 · 16:00–20:00
Rental
Day 2 · 08:00–12:00
Buffer block 1
Day 2 · 12:00–16:00
Buffer block 2
Day 2 · 16:00–20:00
Available again
Can buffers overlap?
The “Allow overlapping buffers” option is available for both calculation modes. Here, each rental needs one block before and one block after the rental period. For an exclusive resource with a capacity of 1:
08:00–12:00
Rental A
12:00–16:00
Buffer after A + buffer before B
16:00–20:00
Rental B
08:00–12:00
Rental A
12:00–16:00
Buffer after A
16:00–20:00
Buffer before B
20:00–24:00
Rental B
These schematic examples are independent of the demo’s opening hours. All rental blocks shown must be permitted by the relevant schedule. Shared buffers do not allow rental periods to overlap protected occupancy. For resources shared between products, both products must allow buffer sharing.
Overlapping buffers
Enabled: Pure buffer periods between consecutive rentals may be shared. With one four-hour block before and after each rental, a single free four-hour gap can meet both buffer requirements.
Disabled: The complete occupancy windows, including buffers, count against capacity. With one block before and after each rental, two separate free blocks are needed between rentals.
For a resource shared between products, both products must allow sharing. Otherwise the stricter setting applies. Availability checks read the current settings of all involved products.
This option does not increase capacity. For an exclusive resource with capacity one, rental time must not overlap another rental or its protected buffer. Example: a 12:00–16:00 rental has buffers at 08:00–12:00 and 16:00–20:00. With sharing enabled, rentals at 04:00–08:00 and 20:00–24:00 may share those pure buffer periods if the schedule and other rules allow.
Calendar, capacity and cart
- Calendar: Partly available days remain selectable. Days without a possible start are disabled. Tooltips distinguish rental occupancy from buffer conflicts; status words are not printed inside the block.
- Capacity: Active cart holds count against availability. Expired, released and archived holds do not. Explicit resource selection checks that specific resource; automatic assignment can choose another eligible available resource.
- Server validation: Month availability, add-to-cart and checkout use the same booking validator. It considers rules, the current time, minimum duration, capacity, buffers and shared resources.
- Cart: Changed configurations, expired holds or invalid resource assignments cause the affected cart item to be removed. Its hold is archived and the customer must choose a time again. Undo cannot revive an incompatible reservation.
- Checkout: Classic checkout and the Store API perform independent checks before saving an order. A booking’s own exact hold is excluded only for its own validation; other cart items are checked together. PH participant checks and other WooCommerce/Addons validators remain involved.
Navigation coalesces identical requests, discards outdated responses and runs at most one background prefetch at a time. Day and month responses are cached in the browser for at most three seconds. Cart changes and returning to the tab clear that cache. A displayed day response invalidates its cached month. The browser cache never authorises a booking.
A maximum loading time of 1.5 seconds is not guaranteed. The month calculation time and the complete HTTP response time are different measurements.
Data, updates and archiving
On first load, the plugin adds dbs_archived_at DATETIME NULL DEFAULT NULL to PH’s existing {prefix}ph_bookings_availability_calculation_data table. The WordPress prefix remains unchanged. NULL means “not archived”; a UTC timestamp records archiving and excludes the row from active availability checks.
Initialisation is repeatable and preserves existing values. If column creation fails, the request stops. The plugin does not create PH’s table, rebuild historical inventory or delete rows during initialisation.
Recognised PH deletion requests are converted to archive or status updates. Associated reservation posts and metadata are retained; destructive whole-table resets are blocked. Direct database maintenance outside WordPress is not covered. Restoring an eligible cart item creates a fresh hold.
Existing rental and buffer boundaries remain stored. If historical rental boundaries cannot be recovered, the entire stored occupancy is treated conservatively. No manual bulk migration is required.
Version changes
- From 0.1.10 to 0.1.11, the new buffer-sharing option stays enabled by default. This version step requires no additional schema change. Older open admin forms without the new field do not overwrite the option.
- From 0.1.9 or earlier, review the new default. Disable overlapping buffers on the relevant products to retain the previous separate-buffer policy.
- Changes to buffer sharing participate in configuration checks for existing cart items. Customers may need to select their times again.
A named database lock serialises reservation writes and relevant configuration changes. Test updates with your own products and checkout workflows first.
About this demo
The Classic Bike Store uses fictional bicycle products. Its pricing and pickup rules are a separate, site-specific integration and are not automatically installed with the general MU plugin.
- Four-hour blocks, up to 84 blocks or 14 elapsed days. Nights count towards rental duration.
- A €2 base fee and product-specific block rates of €2, €3, €4 or €6.
- A native PH pricing rule multiplies both the base and block price by 0.8 for 7–84 blocks. Exactly 24 hours has no discount; the rule applies from 28 hours.
- Pickup: Monday–Saturday 08:00–18:00 and Sunday 08:00–16:00. Return boxes allow returns outside opening hours.
- Configured booking window: 90 days in advance, with eight hours of lead time.
- Buffers are product-specific. Classic Noir was last documented with one block before and two blocks after, with buffer sharing enabled. Other products retain their own settings.
These details describe the documented demo configuration on 19 November 2026. Refer to the product page and cart for a specific selection. The demo includes custom adaptations; enforcement of lead time and the booking window across every write path still needs a dedicated regression test. This is not a real rental service. Please use fictional details only.
See the Classic Bike example for details of how it is separated from the general plugin.
Language, technical options and rollback
The new buffer controls and messages use English source strings and the digitalysator-booking-slots text domain. German PO/MO files and a POT template are included. The WordPress site or user locale selects the translation. Older calendar and cart messages are not all internationalised in the general release.
Developers can use the digitalysator_booking_slots_enabled filter to disable the block adapter per product. Data-retention protection remains active. The experimental REST transport is disabled by default; it is not a regular setting covered by this manual. The product options described here do not require a separate global settings page.
For a complete rollback, move the top-level MU loader out of mu-plugins/. Keep the archive column and retained records. There is no automatic uninstaller that deletes history. Without the loader, PH resumes native behaviour, including its own cleanup logic. Make a backup before rolling back.
Custom runtime code, JavaScript and translations reside in the MU plugin; settings and availability data are stored in the WordPress database. The general extension does not modify vendor files from PH, WooCommerce or Product Addons.
Troubleshooting and limitations
- The additional controls are missing.
- Check the MU loader and folder structure, open a PH booking product and enable Buffer Time. Absolute mode shows PH’s duration fields; block mode shows the additional block counts.
- A day or start block is unavailable.
- Check opening hours, boundary/end times, minimum duration, lead time, booking window, capacity, resources, active holds and both buffer sides. In block mode, also consider the 366-day search horizon.
- Buffers do not seem to be shared.
- For shared resources, check the option on both products. Only pure buffers can be shared, not rental time. Capacity and other rules still apply.
- A cart item disappears.
- The hold may have expired, the resource may be invalid or the product configuration may have changed. Select the time again.
- Requests fail after installation.
- Check that PH’s availability table exists and that the database account can add the archive column. Back up before working on the database.
This release targets hourly and minute-based intervals. Day/month intervals, recurring or disjoint multi-date bookings, all admin editing dialogs, external calendar synchronisation and real payments have not been fully accepted. Compatibility checks are required after changes to PH’s PHP behaviour or database schema.
The README reports 226 passing PHP checks for the booking baseline from 0.1.12, eleven archive-initialisation checks from 0.1.13 and 24 translation checks from 0.1.11. These do not represent a full browser checkout acceptance test for 0.1.14 or arbitrary product combinations.
Digitalysator Booking Slots is an independent GPL-2.0-or-later extension and is not an official PluginHive or WooCommerce product. Further reading: README and changelog.