I just did an .ENEX import and a fair number of my imported records have raw XML markup at the top of the files, often after an image. They look like below whether I use the markup or WYSIWYG. Is there a way to clean this up?
Just the ENEX file for a note that has a problem is enough. So from your screenshot it would be for example the note titled "Mushroom and Spinach..." - simply right-click on it in Evernote and export as ENEX.
I reimported my recipes and a random spot check shows all except for one to have imported correctly. Wow. I'm impressed that you fixed this so quickly. Do you want me to send any other notes that I find that this issue shows up in?
P.S. obviously unrelated to this note, but like others here I'm doing a deep dive to determine if I can completely switch from Evernote. The inline media (specifically PDFs) may be a dealbreaker for me. It seems that you may be pretty far along in remedying that per this: Feature request: Inline PDF Is this on the near-term horizon?
Wow. I'm impressed that you fixed this so quickly.
Quite the culture shock coming from Evernote, isn't it? Where they're too busy to deal with bugs because they're trying to figure out exactly which shade of green the elephant logo should be.
The latest release should fix this: Release v1.5.14 · laurent22/joplin · GitHub I've recently added support for hidden sections in enex files, which I thought was quite harmless, but it caused a few small issues like this one.
I have been doing further testing on IOS and Android and records that render properly (and assume were imported properly) in the desktop app, are showing the same header garbage in the notes. I don't mean to be a PITA, is it useful for me to send these problematic notes? and if so, do you want the individual .ENEX for them, or something else?
If it's the SVG, it's because part of the fix was in the way they are rendered and that fix has only been applied to the desktop app at the moment. So once the new iOS and Android versions are released it should work.