when export note as markdown file with local image, the image file in the attachment will be exported as
dst_folder/attachment/b77fc476.png, but the image path in the markdown file is not consistent with actual path, is dst_folder/attachment/cd4f570c-3dd9-42b7-8f4a-08a2b4c8d093/b77fc476.png
no need to modify the markdown path manually.
Assume that ${NOTE_NAME} denotes to the current note name.
attachments/${NOTE_NAME}/${IMAGE_NAME} , ${IMAGE_NAME} denote the generated image name. attachments/${IMAGE_NAME}, but the code in the markdown file remains , so the image can't be properly displayed.So I have to manually delete the ${NOTE_NAME} part to make it works.Can you provide steps to reproduce the error?
Can you provide steps to reproduce the error?
@ZeroX-DG sure, I add some detailed description.
I have the same problem when I simply export a single note to a markdown file.
image files are exported to "attachments" folder, but paths in a markdown are not updated and wrong.
e.g. a path looks like
[e60b4f55.png](:storage/597a1f9e-f176-45b5-b5c2-a607829bb1bc/e60b4f55.png)
and it is not updated to "attachments" folder.
--
environment
Boostnote 0.11.17
Mac OS 10.14.4
Hi,
I have exactly the same problem. Do you have a plan to fix this issue?
Env
BoostNote Version 0.13.0 (0.13.0)
Mac OS Version 10.15
I have just tested this on Windows 10 and exporting a note with images produces the following code in the .md file:
...
## Image



...
These links will indeed not work, because the note name is no longer present after the export.
In addition when exporting a "storage" to markdown, no attachments are exported at all !, no attachment folders are created in the respectively exported boostnote folders.
@marcodings Thanks for the report! I have created a separate Github issue for this problem #3336. Because the cause of your problem is different from the one mentioned in this issue. (Attachment link formatting, versus attachment presence in export).
Hello, guys, I have replicated this same issue in BoostNote 0.13.0 and Mac OS 10.15, if you plan to fix this issue it would be a great opportunity for me to start contributing to this project. Let me know so I can create a PR.
@AlfredoGJ I don't quite understand. Do you wish to contribute by making a PR that fixes this issue or will you start contributing once we have fixed this issue?
In case of the former, then feel free to submit one as soon as works for you. Anybody is welcome to provide fixes/solutions to the open GitHub issues! :D
Sorry, I meant I wish to contribute by fixing this issue. I' will start working on in. Thank you very much
Hey guys, can you provide some feedback about the PR I sent for this issue?