Error at booking an appointment

Hi,

to fix this click “Reset settings” you need to enter gain your previous settings.

Okay, but will I loose all the settings I set?

I have the same problem, I just did it… You will not loose the setting of your “services” and you will not loose the schedule of your “assitants”… but you will have to set the other things

@kaz007 & @wordpresschef thank you for your quick support. The settings of the assistents and services luckily didn’t delete. I did have to create the whole colorscheme again and all the vacations of employees. (so something to consider, might someone read this and is about to reset the settings). Tip for someone that reads: screenshot all settings and copy+paste all added info, so you can have the app working again in no time!

Bless

But it doesn’t work for me, I have the error problem.In another post the autor say to disable the AJAX step option and enable the “gust checkout” option.

https://www.mogbarbershop.com/

@kaz007 @wordpresschef Yes, have the same problem again too. With resetting the app did it for a second, but now I still get an error when testing it!

How is it gonna get resolved @wordpresschef ?

So, i fixed the booking thing: stopped AJAx and enabled guest option.

BUT NOW: I don’t receive booking emails, and the customers are stuck in the page where they just confirmed booking……

(Guys, I just had a major newsletter for Mothersday, so a lot of people want to book, can someone please help us out?)

https://www.beautyvibes.nl/online-afspraak

Hi,

we are going to make a test on your website.

but I don’t see it online..

@wordpresschef That’s because I enabled it, since I was getting an overload on phonecalls and emails because people weren’t able to book ??

I’ve created a private page customers won’t see, so you can test it:

https://www.beautyvibes.nl/testpage

Hi,

we’ve just released a new version with a definitive fix.

Wait for the update alerts and then proceed with the update, no other actions are required.

Thank you for your patience.

I think we have the same problem although it is not fixed (we use free version 3.30.2). Clients get this error: https://ibb.co/F4YF4ym

When testing we ourselves never saw this error, but many clients report it. What could this be?