Hello Olivier,

Thank you for reaching out to us.

Can you please send us a short one-two-minute video of the issue so that we can take a closer look?

Looking forward to your reply. 

Hello Olivier,

Of course, we understand and we will gladly take a look and resolve this issue.

Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site), and of course, we do not provide login data to third parties. 

You can write credentials here just check PRIVATE Reply so nobody can see them except us.

Looking forward to your reply. 

Hello Olivier,

We have forwarded your ticket to our level 2 agents and as soon as we get some feedback from them we will contact you immediately.

Hello Olivier,

We just got the feedback from our colleagues and they have told us that we have solved the original error:

amelia-booking.js?ver=6.2.1:1 TypeError: Cannot read properties of undefined (reading 'ev_spots_number')

Now it seems to be working. We are redirected to a successful booking page and have received the email. Please try now.

The redirect URL in the settings is used when the client clicks finish, the second button in the picture. They are first always redirected to the same page they booked from.

5406449616.png
If you want the client to be redirected right away you can use the following js hook:

<script>
window.ameliaActions = { 
   Purchased: function (success = null, error = null, data) {  
      //triggered once an online booking is completed   
      console.log('Purchased HOOK')    
      console.log(data)
      console.log('------------')  },
}
</script>

Hope this helps. 

Hello Olivier,

We will check this out with our colleagues and as soon as they send feedback we will contact you on this ticket.

We wish you all the best.

Have a nice day. 

Hello Olivier,

We just got the feedback from our colleagues and they have told us that the solution was to click save on customize (since a new label was not saved), not to change any of the code, so it is not necessary to update the plugin. However, we have fixed the issue in the newest update and there is no problem with updating to that one anyway.

If you have any more questions please open a new separate ticket for each question and we will gladly help you there.

We wish you all the best.

Have a nice day.