I have updated a note and synced it, and repeatedly my new changes were lost, over-written by an old version. There was no warning, no error message. The changes were just lost. Evernote acted as if it doesn't recognize the edits I have made.
Finally I enabled detailed Activity Log and seem to have found the problem to this particular note -- However the bigger problems is that Evernote encountered a problem and didn't flag it to the User. So changes were lost but the User was not informed.
The file is 10,202 characters long, mainly of text, some links, some cut-and-paste which may contain formatted text in addition to plain text. It is a file I use multiple times a day. There may have been some kind of unacceptable character in the file that Evernote couldn't handle. The messages in the Activity Log are:
17:55:43 [12520] Client synchronization finished, status: complete
17:56:01 [14764] Note 4285 ENML Validation error: Excessive depth in document: 256 use XML_PARSE_HUGE option
17:56:01 [14764] Can't save note uid=4285, error: CantConvertNoteContent
17:56:32 [9020] Client synchronization started
It is just a text file, including some URL links, also includes some double-byte Traditional Chinese characters and some double-byte Simplified Chinese characters. There is no graphic, no picture.
1. The file size is below the maximum.
2. There shouldn't be any content that Evernote cannot handle.
3. If Evernote cannot handle some content, it should flag it right away during edit. It should not have accepted the edit.
4. After accepting an edit, it should be able to save.
5. If it fails to safe, it should notify the User instead of acting like everything was normal.
Please open bug report and fix it.
Sorry I don't have the original buggy note. In the process of discovering the problem, I've copied it to Notepad and back to Evernote, which eliminated the error. (That's why I suspect there was some special character that Evernote could not handle and caused the bug.)
Idea
Gerald Yu 1
I have updated a note and synced it, and repeatedly my new changes were lost, over-written by an old version. There was no warning, no error message. The changes were just lost. Evernote acted as if it doesn't recognize the edits I have made.
Finally I enabled detailed Activity Log and seem to have found the problem to this particular note -- However the bigger problems is that Evernote encountered a problem and didn't flag it to the User. So changes were lost but the User was not informed.
The file is 10,202 characters long, mainly of text, some links, some cut-and-paste which may contain formatted text in addition to plain text. It is a file I use multiple times a day. There may have been some kind of unacceptable character in the file that Evernote couldn't handle. The messages in the Activity Log are:
17:55:43 [12520] Client synchronization finished, status: complete 17:56:01 [14764] Note 4285 ENML Validation error: Excessive depth in document: 256 use XML_PARSE_HUGE option 17:56:01 [14764] Can't save note uid=4285, error: CantConvertNoteContent 17:56:32 [9020] Client synchronization started
It is just a text file, including some URL links, also includes some double-byte Traditional Chinese characters and some double-byte Simplified Chinese characters. There is no graphic, no picture.
1. The file size is below the maximum.
2. There shouldn't be any content that Evernote cannot handle.
3. If Evernote cannot handle some content, it should flag it right away during edit. It should not have accepted the edit.
4. After accepting an edit, it should be able to save.
5. If it fails to safe, it should notify the User instead of acting like everything was normal.
Please open bug report and fix it.
Sorry I don't have the original buggy note. In the process of discovering the problem, I've copied it to Notepad and back to Evernote, which eliminated the error. (That's why I suspect there was some special character that Evernote could not handle and caused the bug.)
Link to comment
8 replies to this idea
Recommended Posts
Archived
This topic is now archived and is closed to further replies.