ENEX does not import correct when title of note matches the name of the attachment

[emlowe]

ENEX does not import correct when title of note matches the name of the attachment

[emlowe]

Normally one would expect to find 35fab64c7dba45e1a477262e36a2f1c4.pdf in the /Users/elowe/.config/joplin-desktop/resources/ directory

However, it's missing and not there.

[khuongduy354]

Hi, can you elaborate the reproduce steps? Is it import ENEX as markdown? In my case, after import, it chose the name already so I cant change it to make pdf appear ?

[emlowe]

Import as markdown

The PDF file itself is missing from the import on-disk - the Note references some UUID file name that doesn't exist.
You cannot make the PDF appear since it wasn't imported correctly

If you edit the ENEX XML file directly however, and change the title, then it will import correctly

[emlowe]

I'll note that the expected MD5 of the file listed in the markdown 35fab64c7dba45e1a477262e36a2f1c4 is NOT the MD5 of the actual attachment.

In fact, when I calculate the expected MD5 of the filename from the ENEX file it is cd892fa62f1bc4115cb2eceda654143c and that file IS in fact in the correct place

So, the file is there.

[khuongduy354]

The bug is in restore-note-link, it use link title to change Evernote's note-link to Joplin's note-link. The problem is the link title in your example is a resource-link (not note-link), and it has same name as note-link. so it mistakes and fix the link. The resource creation stills work fine.

Proof: comment out restoreNoteLinks function, and run, it works.
My solution: To distinguish a note-link and resource link, title alone is not enough, we need the resources' ids of the imported ENEX, I'll make a PR in the morning.

[khuongduy354]

#10149, how can I address this PR, without typing it in a comment like this ? Still don't know how to do it 😆 .