Super
Thanks to @HotDrive and @jasperkok for working with me on this and testing the BETA, we now have an update for all sent via email and RW in-app update:
- Fixed issues with email Notifications
- Updated sending SMTP settings to fix bug for sending
- Added a disable button on submit to prevent double submissions
- Added a “are you sure repost?” message to prevent double submissions
https://updates.yuzoolthemes.com/post/180773005882/booking-stack-157
Thanks
Thx Michael, just test the update. All works now fine
Thanks for the great support
Great update (1.5.7) Michael
Thanks
My wish for the next update
Enable MinMax Day (same as MinMaxTime)
Add a Start and End day (entry of fixed days) for the booking selection.
Hey Michael!
I’m testing out the Booking Stack (again). The email notifications work perfectly now! However, I noticed a bug of sorts- I’m testing out duplicate bookings on the same date and time (to verify that a user can’t book a date/time that’s already booked by someone else). The error message works perfectly and does not allow me to make a duplicate booking. BUT, when I made a duplicate booking (with different credentials- name, email, etc), the proper error message came up but it still sent a booking notification email even though the duplicate booking was never saved. Is it possible to simply not send email notifications for EVERY booking form submission? Even though it’s properly displaying the “existing booking” error for the user, it still sends a booking email for the attempted submission.
Thanks!
Interesting @manuvmusic!
The email notifications work perfectly now!
Great
The error message works perfectly and does not allow me to make a duplicate booking
Great
Is it possible to simply not send email notifications for EVERY booking form submission?
Absolutely yes. Will look into this and get it into the next round of updates for this Stack. Thanks for reporting it, appreciate that.
Just going to private message you a BETA update @manuvmusic that hopefully has an improvement for this If it works out then we can release it!
Let me know.
Awesome! Will download and test today/tomorrow.
Thank you!
Thanks to @manuvmusic for his excellent suggestions and diligent testing we now have a new version of Booking Stack out today (1.5.9):
NEW
- Allow more time step intervals. E.g. 180mins would allow bookings for 3 hour slots.
- Ships with demo project
IMPROVEMENT
- Improved email notifications - only sends if booking is made successfully.
FIXED
- Fixed preview bug with SMTP enabled
TESTED
- Redirecting works, the “Sorry” message for an existing booked day works, notifications work, email receipts work, and SMTP works
More updates on the way soon and thanks for the suggestions
Great update, thanks Michael
Awesome, this is becoming a real and usable booking system.
Thanks to all the great feedback and testing from RW community
Have a great weekend everyone!
Hi Michael, can you please add the ability to view bookings via a calendar? I will buy it then. cheers
Thanks @A.D.STUDIO - that’s been requested and on the list
Not super easy to do but always exploring this
In the meantime users who use GCal have embedded a calendar next to their form to show the “unavailable days”
Thanks for the info. I’m sure you can do it!
Hi Michael, that would be indeed a great update. Making the Booking Stack even more powerful, as always most of your stacks are excellent and your custom service (feature request) 10/10
SOLVED AFTER PUBLISHING
Hello everybody,
I finally set up the booking stack on one of my pages.
I registered my domain on the Google’s link Yuzool put on his stack sheet’s info.
I copied the Site Key into the stack, but when I preview an after publishing I get this message on the re-captcha icon
Is it maybe because I have’t put a snippet-code inside RW?
SOLVED NOW
Hi @yuzool,
I can’t figure out this. How can I put the header inside the booking stack? Like the example from your site.
Thanks @Adri12 - it was just a Heading Stack inside a 1 Column Stack:
The RW project is included in the Stack download - but I’ve just sent it to you again via DM
See if that helps!