Tomboy notes are not converted to XML on Tomboy sync
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu One Servers |
Fix Released
|
High
|
Rodrigo Moya |
Bug Description
STR:
0. Reset tomboy note sync so that it is in clear state.
1. Create a new HTML note with the following content via futon:
{
"_id": "0781989f6f7c47
"_rev": "5-f1826e7fb801
"create_date": "2010-01-
"application
"Tomboy": {
"tags": [
]
}
},
"title": "I am a HTML note",
"last_
"content": "I am a note in HTML format<
"record_type": "http://
"record_
}
(This is available at http://
2. Wait until the note is replicated to u1
3. Perform tomboy note sync.
Actual result:
Note sync fails with no error displayed in the UI but with the following printed to the terminal:
[INFO]: Initializing Mono.Addins
[ERROR]: Synchronization failed with the following exception: 'br' is expected Line 6, position 64.
at Mono.Xml2.
at Mono.Xml2.
at Mono.Xml2.
at Mono.Xml2.
at System.
at Tomboy.
at Tomboy.
at Tomboy.
(/usr/lib/
Expected result:
Note sync is performed correctly.
You will also see that the note in couchdb is not converted to XML for future lossless sync and note_format is not added.
Note sync seems to be performed correctly for new notes that are stored in XML format from the start.
As you can see, the parser expects closing </br> but it also means that <br>s got sent to Tomboy which is not right since Tomboy XML uses CR/LF characters for new lines i.e. conversion is not done.
See also: bug 406816 and bug 501020, comment #32.
visibility: | private → public |
tags: | added: desktop+ notes webui |
Changed in ubuntuone-servers: | |
importance: | Undecided → High |
assignee: | nobody → Ubuntu One Desktop+ team (ubuntuone-desktop+) |
description: | updated |
Changed in ubuntuone-servers: | |
status: | New → Fix Committed |
Changed in ubuntuone-servers: | |
status: | Fix Committed → Fix Released |
I've tried with several of my notes stored still in HTML on the server, adding <br>'s and &, and the conversion seems to be ok. So not sure where d.oes this come from. Shouldn't this already be fixed by the close-brs branch? If the HTML has a <br> the code replaces it with the correct <br/>