Since 102 Convert message to task only works for local calendar
Version 91 works correctly on other machines. On one machine that is updated to 102.0.1: Create a New Task DOES work for CalDav calendars. Convert mail to task DOES work for local Home calendar. Convert mail to task does NOT work for CalDav calendar. No task gets created. (It does still work in 91.) Move a task from Home to CalDav DOES work if the Home task was created with New Task. Move a task from Home to CalDav does NOT work if the Home task was converted from mail message. CalDav is DAViCal (on Linux, Apache) which is still serving TB ver. 91 machines. All TB 91 and 102 instances are running on Windows 10 21H2 with Firefox 102. Any advice? What more can I tell you?
Alle Antworten (4)
A little more information. The tasks that were converted from mail to CalDav using TB 102 ARE BEING STORED in DAViCal: They appear as normal in the task lists in TB 91! They do NOT appear in the task lists for the same user with TB 102. The tasks that were converted from mail to CalDav using TB 91 behave normally in TB102. They DO appear in the task lists for a user with TB 102.
... and one final update. After applying the update to 102.0.2, this issue appears to have solved itself. Nothing in the change log to suggest that it was actually addressed, but 102.0.1 still produces the problem, while 102.0.2 does not. I'll take it. Thank you.
Spoke too soon. Problems that go away by themselves, come back by themselves. To summarize: When using TB 102 to convert email to a CalDAV task, the task never makes it into the 102 task list. The task DOES appear in the same user's TB91 task list. If the message is converted to a task by TB91, it DOES appear in the TB102 task list. In all cases the task IS stored in the CalDAV server. Something about the 102 conversion that the 102 calendar finds problematic?
Hi, I have this problem although in 102.3.2 and 102.3.3. When I 'Convert a message to Event' (in a remote caldav calendar) it all looks fine, but doesn't save. I can Ctrl+E and create a new event, but not Convert to an Event. It has been doing it since I upgraded to 102, which was yesterday. It has just upgraded to 102.3.3 but that hasn't addressed the issue. 64 bit system running on Win 11.