본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

recurring events where one event has been moved to another date show on wrong date in calendar

  • 1 답장
  • 1 이 문제를 만남
  • 6 보기
  • 최종 답변자: A.W.

more options

Hello,

I have synchronized a shared Google calendar via https://apidata.googleusercontent.com/caldav/v2/xxxxxxxxxxxxxxxxxxxxxxxxxxxx@group.calendar.google.com/events in Thunderbird. This basically works fine.

But if there is a recurring event (e.g. every two weeks on Wednesday) and someone moves a single one of those events e.g. from Wednesday to Thursday via her/his Google Calendar app on Android smartphone, this single event will still show in Thunderbird on Wednesday instead of Thursday. While it shows on Thursday in Google Calender app or on calendar.google.com (see Screenshots).

What can be done to show the event on the correct date in Thunderbird calendar, too?

(This is no synchronization problem, other events added later are shown in Thunderbird.)

Many thanks for your help!

Hello, I have synchronized a shared Google calendar via https://apidata.googleusercontent.com/caldav/v2/xxxxxxxxxxxxxxxxxxxxxxxxxxxx@group.calendar.google.com/events in Thunderbird. This basically works fine. But if there is a recurring event (e.g. every two weeks on Wednesday) and someone moves a single one of those events e.g. from Wednesday to Thursday via her/his Google Calendar app on Android smartphone, this single event will still show in Thunderbird on Wednesday instead of Thursday. While it shows on Thursday in Google Calender app or on calendar.google.com (see Screenshots). What can be done to show the event on the correct date in Thunderbird calendar, too? (This is no synchronization problem, other events added later are shown in Thunderbird.) Many thanks for your help!
첨부된 스크린샷

모든 댓글 (1)

more options

Problem seems to be solved in newest update of Thunderbird (78.8.0)