Skip to content
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

calendar export broken #2

Open
faroit opened this issue Oct 9, 2020 · 0 comments
Open

calendar export broken #2

faroit opened this issue Oct 9, 2020 · 0 comments

Comments

@faroit
Copy link

faroit commented Oct 9, 2020

I tried import the ical file into either apple ical or google calendar but without success (failed silently)

An online ical validator revealed that there might be some missing fields


Errors

    Missing required VERSION property near line # 1Reference: RFC 5545 3.6. Calendar Components
    Missing DTSTAMP property near line # 3Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 3Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 3Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 10Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 10Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 10Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 18Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 18Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 18Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 25Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 25Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 25Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 33Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 33Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 33Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 40Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 40Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 40Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 47Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 47Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 47Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 55Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 55Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 55Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 63Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 63Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 63Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 70Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 70Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 70Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 77Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 77Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 77Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 85Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 85Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 85Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 92Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 92Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 92Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 99Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 99Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 99Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 106Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 106Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 106Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 114Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 114Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 114Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 122Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 122Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 122Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 129Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 129Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 129Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 136Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 136Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 136Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 143Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 143Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 143Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 151Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 151Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 151Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 158Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 158Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 158Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 165Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 165Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 165Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 172Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 172Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 172Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 180Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 180Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 180Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 187Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 187Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 187Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 194Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 194Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 194Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 201Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 201Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 201Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 208Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 208Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 208Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 215Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 215Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 215Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 222Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 222Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 222Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 230Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 230Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 230Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 237Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 237Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 237Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 244Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 244Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 244Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 251Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 251Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 251Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 258Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 258Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 258Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 265Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 265Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 265Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 272Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 272Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 272Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 279Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 279Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 279Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 286Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 286Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 286Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 293Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 293Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 293Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 301Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 301Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 301Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 308Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 308Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 308Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 315Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 315Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 315Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 322Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 322Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 322Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 329Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 329Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 329Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 337Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 337Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 337Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 344Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 344Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 344Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 351Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 351Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 351Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 358Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 358Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 358Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 365Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 365Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 365Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 372Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 372Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 372Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 379Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 379Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 379Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 386Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 386Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 386Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 393Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 393Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 393Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 400Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 400Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 400Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 407Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 407Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 407Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 414Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 414Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 414Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 421Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 421Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 421Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 428Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 428Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 428Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 435Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 435Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 435Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 442Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 442Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 442Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 449Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 449Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 449Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 456Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 456Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 456Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 463Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 463Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 463Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 470Reference: RFC 5545 3.6.1. Event Component
    Invalid DTSTART value, must be a valid date or date-time value near line # 470Reference: 3.3.5. Date-Time
    Invalid DTEND value, must be a valid date or date-time value near line # 470Reference: 3.3.5. Date-Time
    Missing DTSTAMP property near line # 477Reference: RFC 5545 3.6.1. Event Component

@evansavage maybe it would help to merge in Mini-Conf#95 as it names calendar fixes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant