-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
automatically transfer to some calendar #2991
Comments
If you configure the system to send email notifications, including an ical attachment, to the booker and you configure your smartphone calendar to automatically add bookings, then this should do it. Is that what you are looking for? Original comment by: campbell-m |
Hi Campbell, Thank you for your answer and especially for the very good work. Frankly, I have not yet found how to send the ics files. Also I don't know if there is an option to automatically add the ics files to the calendar, but I will look about it. So there is no way to somehow synchronize the entries with an online calendar (ex. Google Calendar) and then include it on the smartphone? Best, Original comment by: mmuller |
Have a look at the "Email settings" section of systemdefaults.inc.php.
See this article.
You can do an export of existing entries to your Google Calendar by going to the Report page and choosing the iCalendar report format. This will produce a .ics file which can then be imported into Google Calendar. Once you've done that you can make sure that any new entries go into your Google Calendar by using the automatic email notifications as described above. Original comment by: campbell-m |
It works now with Google Calendar. Thanks a lot for your work and the hints! Best, Original comment by: mmuller |
See also Issue #3742. |
Unfortunately I could not find anything in the search.
Is there any way to automatically transfer the booked appointments to some online calendar. The main thing is no manual steps and somehow get into the calendar of a smartphone.
Reported by: mmuller
Original Ticket: mrbs/support-requests/2301
The text was updated successfully, but these errors were encountered: