-
Notifications
You must be signed in to change notification settings - Fork 38
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
"This note does not exist any more.", but note hasn't changed #266
Comments
No need for remote changes either, just edit locally, eg. Change sched time Then open the notification... |
I'm just going by memory now, but I'm fairly sure this happens because each edit or update of a note means that it gets replaced in the database, and thus gets a new ID. So Orgzly has no way of finding the note referenced by the notification. I suppose something like #268 could help, but personally I find such generic IDs to be annoying clutter. It would be good to examine, and document in some issue, the feasibility of updating notes in-place, instead of replacing them. I'm guessing it would be harder for remote changes, but easier for local edits. (IIRC, remote changes in a notebook always means that all its notes are deleted from the database, and then new notes are created when loading the book.) |
I'm keep getting "This note does not exist any more." error after a notebook is edited remotely on another computer. This appears after trying to click on a notification pushed by orgzly (before the notebook was edited remotely). It happens irrespective of the change - even if done to another header in the notebook (e.g. prepending DONE to a header).
To reproduce:
Expected behavior:
I expected orgzly to only push this error when a that corresponding entry was edited. Or even better for it to just pull the changes and display the current version.
Possible solution:
store checksums of each item and when this error is detected attempt to find corresponding header using checksum (or combination of other heuristics).
[X] I have searched for existing issues that may be the same as or related to mine.
The text was updated successfully, but these errors were encountered: