Sync fails if one tasks if moved to a different project #11

New issue

Closed

opened 2026-05-29 18:26:19 +02:00 by fpindado · 1 comment

fpindado commented

2026-05-29 18:26:19 +02:00

Owner

When a task is moved from one project to another (drag and drop or with mouse right click), the plugin does not detect the change and it does not raise a sync, so in next manual sync or probably next automatic one, takes md file as master and return it back to its original state.

fpindado added the

bug

label

2026-05-29 18:26:19 +02:00

fpindado self-assigned this

2026-06-10 18:28:13 +02:00

fpindado commented

2026-06-22 18:00:58 +02:00

Author

Owner

Confirmed working — closing.

This is effectively the same bug as #27 (Round 6), which was fixed by detecting project moves via the taskUpdate hook: when a task is moved between projects its payload carries changes.projectId (the destination), and the plugin then notifies all sessions so both the origin and destination Markdown files are updated. syncAllNow() was also changed to run SP→MD first so a manual sync captures moves too.

taskUpdate is a valid hook name on SP 18.9.1D (unlike the old persistedDataUpdate), so the mechanism works here. This issue was simply never closed after the #27 fix.

Verified on macOS 18.9.1D via console: moving a task between projects logs
taskUpdate: project move detected — notifying all sessions, followed by batch updates to the affected projects, with no typia/registration errors.

Closing as fixed (resolved by #27).

Confirmed working — closing. This is effectively the same bug as #27 (Round 6), which was fixed by detecting project moves via the `taskUpdate` hook: when a task is moved between projects its payload carries `changes.projectId` (the destination), and the plugin then notifies **all** sessions so both the origin and destination Markdown files are updated. `syncAllNow()` was also changed to run SP→MD first so a manual sync captures moves too. `taskUpdate` is a valid hook name on SP 18.9.1D (unlike the old `persistedDataUpdate`), so the mechanism works here. This issue was simply never closed after the #27 fix. **Verified on macOS 18.9.1D** via console: moving a task between projects logs `taskUpdate: project move detected — notifying all sessions`, followed by batch updates to the affected projects, with no typia/registration errors. Closing as fixed (resolved by #27).

fpindado closed this issue

2026-06-22 18:00:58 +02:00