Hello. Updated to latest version this morning. Client just contacted me. In the Appointments list changing the status (via drop-down) from Pending to Approved is not working - it is necessary to edit the order, click on the green circle and click save.

By 'not working' I mean that the change via drop-down is not sticking, change to Approved, refresh browser, status is still Pending.

Is this a bug in latest version?

Could you please take another look?

If edit the appointment and change state to Approved and save it that works. I can then, using the drop-down, change the status back to Pending, and that works. But I cannot then use the drop-down to change again to approved, everything just hangs and I see this in console:

<code>amelia-booking-appointments-1e6ea23562f73ec85ee6.js:1 Uncaught (in promise) TypeError: Cannot use 'in' operator to search for 'timeSlotUnavailable' in undefined
    at amelia-booking-appointments-1e6ea23562f73ec85ee6.js:1:241298</code>

I have tried in 2 browser, in anonymous tabs, all cache cleared - same. There is no server-side cache.

Thanks.

Hello, I'm facing the same issue , I can not accept bookings. It works fine in the Edit screen. 

Error message is the same:

Uncaught (in promise) TypeError: Cannot use 'in' operator to search for 'timeSlotUnavailable' in undefined
    at amelia-booking-appointments-4dabac2f1dc4cce2c84d.js:1:241298

All caching is turned off and using incognito browser session, Chome, Firefox. 

I have this too and clearly others do.  I posted this on Saturday (https://tmsplugins.ticksy.com/ticket/3151526/) and have had no reply from TMS.  I appreciate that that was a weekend but this report here started on Friday and seems only to have been put to "level 3 agents" today.  Wim has given a really clear report that clarifies that it's a bug in the plugin presumably introduced by the latest update.  I am guessing that this is some corner case otherwise I would guess that his board would be swamped with people reporting it but that makes it particularly important that you liaise back with those who are reporting it and don't try to bounce it with a comment about cacheing (honestly, this plugin should be utterly robust against browser cache issues).  It's not acceptable for a plugin that is going to be vital to many companies not to be (a) communicating better about reported issues and (b) fixing it.  Matthew Gerrish replying to my report (which has had no reply from TMS yet that I can see, says what I was tempted to say which is that TMS appear to be committing to adding things but have serious issues with rock solid reliability.  NOT impressed.

Thanks Marko - it wasn't me that was berating you about speed of fix, incidentally!

Have responded in the other thread but will confirm here - today's release looks to have fixed this bug.

Thanks Marko. Just installed the update and it seems to work fine now.

Fixed for me too.  I was (one of) the ones "berating" TMS for the speed of response on this, essentially a complete break in what the plugin is supposed to do and I remain deeply concerned both that such a failure could happen, but accept that these things can if there is something sufficiently different about our deployment environments from TMS's pre-release testing environments.  More seriously, I don't think the communication or the speed of fix is good enough.  Perhaps TMS need only to release "upgrades" that are not security critical on Mondays if they are not going to fix reports of fundamental failures over weekends.  Episodes like this shouldn't be just about the fix, they should be about the entire system and about learning from such things.  If this were open source I'd accept that resources to fix things and to have a full systems overview can't be expected but I think TMS plugins are not cheap and the financial resources should be there to handle these things better.  

I think as customers paying for these things we have a right, actually a responsibility, to flag these things and publicly.  (I do give TMS 5/5 for the fact that we can flag them publicly: too many software vendors don't allow that, so thanks for that!)