Fix for connecting harmonizely.com to Baikal #1020
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
See https://help.harmonizely.com/en/articles/4602263-connecting-baikal-calendar-works-but-the-availability-is-not-loading and sabre-io/dav#1244 (comment) for details. (I did not come up with this workaround - @Yannik did - but I can confirm that it made things work for me.)
|
This fix also works for me. Maintainers, what do you think of it? @phil-davis |
Member
|
I'm a bit worried that this might cause issues with other clients |
|
The link to the new help page is now https://help.simplymeet.me/index.php/Connecting_Baikal_calendar_works_but_the_availability_is_not_loading |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See https://help.harmonizely.com/en/articles/4602263-connecting-baikal-calendar-works-but-the-availability-is-not-loading and sabre-io/dav#1244 (comment) for details.
(I did not come up with this workaround - @Yannik did - but I can confirm that it made things work for me.)