This really freaks me out. Trying to look into the db and compare this timeslot with another the same day without understanding how the padding time got lost. (However its not trivial to understand where the padding time is added to the other time before displaying free time slots…)
This is the json payload for the “faulty booking”:
a:19:{s:11:"final_price";s:6:"895.00";s:4:"apps";a:1:{i:0;a:11:{s:2:"id";i:1;s:9:"cancelled";s:0:"";s:12:"serviceindex";s:1:"1";s:7:"service";s:10:"Behandling";s:8:"duration";s:2:"50";s:5:"price";s:3:"895";s:4:"date";s:10:"2019-09-26";s:4:"slot";s:11:"11:00/11:50";s:8:"military";i:1;s:5:"field";s:10:"fieldname1";s:5:"quant";s:1:"1";}}s:13:"app_service_1";s:10:"Behandling";s:12:"app_status_1";s:0:"";s:14:"app_duration_1";s:2:"50";s:11:"app_price_1";s:3:"895";s:10:"app_date_1";s:10:"2019-09-26";s:10:"app_slot_1";s:11:"11:00/11:50";s:15:"app_starttime_1";s:5:"11:00";s:13:"app_endtime_1";s:5:"11:50";s:14:"app_quantity_1";s:1:"1";s:6:"formid";i:1;s:8:"referrer";s:38:"https://rostfabriken.se/onlinebokning/";s:10:"fieldname1";s:39:" - 2019-09-26 11:00-11:50 (Behandling)
";s:10:"fieldname2";s:11:"XXX XXXXX";s:5:"email";s:20:"[email protected]";s:10:"fieldname4";s:20:"Second visit";s:10:"fieldname3";s:24:"Jag accepterar villkoren";s:10:"itemnumber";s:3:"385";}
s:10: feels like it could be the padding time here…
/Erik
Ok, this seems like a regression bug introduced in one of your recent versions (not sure which one). It seems like padding time (at least after a time slot) is not functional at all anymore. Tried adding a new booking first one day (8.00 — 8.50) which is 50 minutes with a 10 minutes padding afterwards and all the subsequent times started 8.50, 9.50, 10.50 etc
Regards!
/Erik
Hi,
Please note that if on a date you have already bookings stored that were received under a different “padding” configuration and later you changed the “padding” then that may cause a conflict while calculating the available spaces.
Please check if that is the case.
Thank you.
