You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Syncing two-way is working well, but only for headlines at level 1. Is this expected behavior? I am only syncing DEADLINE marked entries, but these entries are at multiple levels some at level 1, 2, etc.
IDs are being assigned on the right entries (i.e. even non-level-1 headlines, which is expected behavior), but only level 1 headlines are actually being exported to the icalendar export (and thus being synced).
I suspect skip conditions is the culprit: if any parent heading (on level 1 for instance) would be skipped according to skip conditions sub headings are also skipped when syncing, regardless of whether skip conditions apply to them and even though ID:s are correctly generated for them. At least that's what I make of the code. ID:s are generated by org-caldav-create-uid while the questionable logic described above is applied in org-caldav-skip-function. I personally "solved" this issue by overwriting org-caldav-skip-function with a dummy-function (that does nothing apart from sending a warning to the message buffer). Seems to work. Mind you, this breaks any functionality associated with org-caldav-days-in-past.
@r39ex would you share your override?
I'm interested in that because my Todo are structered:
PROJECT
** NEXT
Because PROJECT has no timestamp there are sync errors, because the target calendar does not accept items without a date.
If I try to filter out these PROJECT items to underlying NEXT items don't get processed.
Syncing two-way is working well, but only for headlines at level 1. Is this expected behavior? I am only syncing DEADLINE marked entries, but these entries are at multiple levels some at level 1, 2, etc.
IDs are being assigned on the right entries (i.e. even non-level-1 headlines, which is expected behavior), but only level 1 headlines are actually being exported to the icalendar export (and thus being synced).
See below config.
The text was updated successfully, but these errors were encountered: