在Google日历中导入的iCalendar事件为空 [英] iCalendar events imported in Google Calendar are empty

查看:120
本文介绍了在Google日历中导入的iCalendar事件为空的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

将ics文件("iCalendar")导入Google日历时,导入成功,并且所有事件都出现在日历中,但事件的所有字段均为空.

When importing a ics file ("iCalendar") into Google Calendar, the import proceed successfully and all event appear in the calendar, but all fields of the events are empty.

显示的唯一信息是忙"(屏幕截图上的占用(e)").

The only information displayed is "busy" ("occupé(e)" on the screenshot).

  • 在导入过程中不显示错误消息.
  • 通过多个验证库和在线工具对ics文件进行了很好的验证.

推荐答案

在我的情况下,这是由于事件的CLASS属性为PRIVATECONFIDENTIAL引起的.

This was caused in my case by the CLASS property of my events being PRIVATE or CONFIDENTIAL.

请参见 RFC 2245 ,第4.8.1.3节分类".

See RFC 2245, section 4.8.1.3 "Classification".

由于ics通过公共链接添加到Google日历,因此Google认为它不应读取和/或显示未标记为PUBLIC的事件的内容.

Since the ics is added to Google Calendar via a public link, Google considers that it should not read and/or display the content of events not marked as PUBLIC.

因此解决方案是将事件的类别更改为

So the solution was to change the class of my events to

CLASS:PUBLIC


请注意,这可能是对该规范的误解,因为明确指出:


Note that this is probably a misinterpretation of the spec, as it is clearly stated that:

[...]由于大多数交换的盲目"性质 使用此备忘录进行处理,这些访问分类无法使用 作为接收iCalendar的系统的执行声明 对象.相反,它们提供了一种捕获目标意图的方法. 日历所有者以访问日历组件.

[...] due to the "blind" nature of most exchange processes using this memo, these access classifications cannot serve as an enforcement statement for a system receiving an iCalendar object. Rather, they provide a method for capturing the intention of the calendar owner for the access to the calendar component.

强调我的.

这篇关于在Google日历中导入的iCalendar事件为空的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆