While the new version successfully hides duplicates from the calendar view, it does not fix the availability.
(I see there's a new function fix_bookings_filter_time_slots_when_product_not_translated() applied to woocommerce_bookings_filter_time_slots, but availability is still incorrect.)
To reproduce:
- create a bookable product with max bookings per slot set to "2"
- book one slot
- that slot is now fully booked and cannot be booked by another customer (while there should be one available slot left)
We are aiming to improve it in a hotfix (5.5.1). I can't promise we will manage, though.
Take into account that the "occupancy" results are cached, it's possible that they're from before the "update". Besides this, there is a problem, the fix will improve grouping "for a specific slot".
I tested with "brand new" products and time slots. Cache is not the issue.
(Occupancy does use transients, but these aren't the issue either. You can replicate it using the three steps above)
To reproduce:
- create a bookable product with a resource
- set the resource max bookings per slots to "2"
- book one slot
- that slot is now fully booked and cannot be booked by another customer (while there should be one available slot left) in any of the products using this resource
Ps: I'm not using "persons", but you may give it a look at the same time, as they may be affected as well
I see a beta version was released with the following info:
[WC Bookings] Reverted the change introduced in WCML5.5.0: Improved booking mechanism when the product has no translation – shows correct availability status.
Are we back to the beginning? Can you do a follow-up?
This is the current status of the compatibility with WooCommerce Bookings:
The plugin offers a wide variety of "booking variants." The fix improved one variant, the most popular in our reports, but affected others, even if they didn't work in the initial version.
For now:
- We've added to our documentation that the products we want to set up for booking must be translated into each language before they are made available to customers on the frontend (this eliminates the majority of basic issues).
- The plugin authors may prepare a hook for us that will allow us to "filter the data" (bookings from multiple languages) that enter the occupancy calculation algorithm. This should significantly/completely improve compatibility with the currently broken feature.
