-
Notifications
You must be signed in to change notification settings - Fork 289
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
Baikal sets cal:calendar-timezone
to a timezone string instead of a VTIMEZONE when creating a new calendar via the web UI
#1241
Comments
For any readers here, as a temporary fix you can re-create your calendars in iCal (MacOS Calendar app): #1085 (comment) |
Please fix this. I don't have iCal. :/ |
I'm also very intererested in getting a solution for the manual installation on a webhosting service. |
I replaced the baikal\vendor\sabre\dav\lib\CalDAV\Plugin.php from the release baikal-0.9.5.zip with the the baikal-docker-hass/files/Plugin.php and now it works also with Home Assistant. |
You ca solve the problem like this: edit the baikal-file:
=>
|
do a PR for that. |
Baikal version: 0.9.4
Expected behaviour:
Baikal should set the field to a correct iCalendar object with a VTIMEZONE. This causes the following bug: #1085 which causes integrations to fail with Cal.com and HomeAssistant.
Current behaviour:
Baikal sets the field to the timzone string from the settings.
Steps to reproduce:
cal:calendar-timezone
fieldThe text was updated successfully, but these errors were encountered: