-
Notifications
You must be signed in to change notification settings - Fork 12
E-Mail Notification for locations #143
Comments
Hi, at Bolle Bonn (https://bolle-bonn.de), we are currently switching to using the CB plugin. We are very interested in this feature because our booking stations usually want to be informed who is coming when to grab the item. I would be willing to help in the implementation. Do you need any support? Cheers! |
Hey @sgrubsmyon, that´s great! Yes, support would be fantastic :) |
Any updates on this? I see that there is a branch for the issue: https://github.com/wielebenwir/commons-booking/compare/email_notification_for_locations. I will try to use it and test if it works OK. |
Hey, unfortunately not right now. Still working on it. Hope this month. |
Please note that I have implemented this here: https://github.com/sgrubsmyon/commons-booking/tree/email_notification_for_locations and merged it into the master branch at https://github.com/sgrubsmyon/commons-booking/tree/master. The way it is implemented (similar to https://github.com/wielebenwir/commons-booking/tree/email_notification_for_locations) is by using a regex to extract all email addresses from the contact information field of the location. Like before, an email is sent to the user and the global BCC address, afterwards emails are sent to all the location email addresses found. I also implemented email delivery in case of booking cancellation here: https://github.com/sgrubsmyon/commons-booking/tree/email_on_cancel. What I would like to still add: Check boxes in the settings that switch the email delivery to locations on and off. |
Update: there is now a check box to switch on/off the BCC email delivery to a location. See PR #172 or sgrubsmyon@70e875c. |
New update: Notification emails will also be sent when an admin deletes a booking from the booking table (only if the booking was not already canceled by the user and lies in the future). See #172 and https://github.com/sgrubsmyon/commons-booking. |
BCC of Booking Confirmation to stations.
The text was updated successfully, but these errors were encountered: