JohnRyanAudio
commented
4 years ago Now in July, I am still able to reproduce this issue.
Open nicksiv opened 4 years ago
JohnRyanAudio
commented
4 years ago Now in July, I am still able to reproduce this issue.
asymmetric
commented
4 years ago Same here: the SCHEDULED field is added above the PROPERTIES drawer, which then renders the item unsyncable.
It does seem like an inconsistency in org-mode that the SCHEDULED item is inserted at the top, whereas the simple timestamp is added where the cursor is.
alejandrogallo
commented
1 year ago You should just leave a newline between the heading of the entry and the SCHEDULING. If you have an org-capture template just put a line between the scheduling and the headline. This is not a bug of org-caldav but an issue with org-mode, I submited a bug report to the org mailing list
jackkamm
commented
1 year ago SCHEDULED is supposed to be above the property drawer. If you put "SCHEDULED" in the main body, it's not actually considered a SCHEDULED timestamp, just a normal timestamp that preceded by the word "SCHEDULED". That's what org-mode/org-caldav exports to calendar event.
By default, org-mode doesn't export the SCHEDULED timestamp to a calendar event, but you can modify org-icalendar-use-scheduled if you want to change this behavior. Specifically, I think you probably want to add event-if-not-todo to it.
For reference I'm linking the org-mode mailing list thread here: https://list.orgmode.org/87o7ppxe8f.fsf@gmail.com/T/#t
Hello, I faced this issue last week, probably after an update: For items not having their property drawer first (immediately at the next line of the item), caldav don't sync them with my calendar. The specific items had their SCHEDULED: property above the PROPERTIES: drawer. When I repositioned the properties drawer one spot higher they synced correctly.
I'm on emacs 26.3 and org version 9.3.6. I sync on a nextcloud calendar.