[Bug]: exception on one of the attachments about joplin-utils HOT 10 CLOSED

Steps 1-5 above are canceled. You can download this zip and unzip it to get the tgz file, then use yarn add -D ./joplin-blog-0.7.0.tgz to install and regenerate to test it?

joplin-blog-0.7.0.zip

Modified a bit, now it will print the file name and extension to be copied

from joplin-utils.

Check if the file /Users/huy/.config/joplin-desktop/resources/7de408d4ec98e0fa8314c6b092156956.jpg exists

from joplin-utils.

/Users/huy/.config/joplin-desktop/resources/7de408d4ec98e0fa8314c6b092156956.jpg

I did. I already listed the output of ls above in my bug description. The file exists and I'm able to open it and see the image with macOS Preview app.

from joplin-utils.

/Users/huy/.config/joplin-desktop/resources/7de408d4ec98e0fa8314c6b092156956.jpg

I did. I already listed the output of ls above in my bug description. The file exists and I'm able to open it and see the image with macOS Preview app.

Sorry, I was too careless, can you try to run it locally?

1. git clone https://github.com/rxliuli/joplin-utils.git
2. cd joplin-utils/
3. yarn && yarn setup
4. cd apps/joplin-blog/
5. edit

   joplin-utils/apps/joplin-blog/src/blog/Application.ts

   Line 232 in 1150087

   const fileName = resource.id + '.' + resource.file_extension

6. yarn build
7. cd
8. yarn add -D /apps/joplin-blog
9. yarn joplin-blog blog

Editing Application.ts refers to printing fileName and resource.file_extension. I observed that the file name reported by the error seems to lack an extension, and the extension is obtained through joplin api. Maybe, this may be joplin itself An error

from joplin-utils.

If it is wrong, please try to use the most primitive api to obtain it (replace id and token by yourself), observe the file_extension field in the result, if there is no value, please report to joplin official.

curl 'http://localhost:41184/resources/<id>?fields=id,title,file_extension&token=<token>'

In addition, you can also try one of the simplest solutions, delete the image from this note, and then copy the picture from it and paste it again. Have a good time.

from joplin-utils.

Yeah, the file_extension field is missing from the DB. These are the attachments that succeeded plus the one that failed:

But I have a lot of attachments that have an empty filename_extension

from joplin-utils.

But I have a lot of attachments that have an empty filename_extension

Then you may need to report a bug to the official, which is obviously a mistake

from joplin-utils.

Unfortunately, Laurent is pointing me back to the joplin-utils repo: laurent22/joplin#5528 (comment)

So I'm stuck with no permanent solution. I guess I will have to hack my database to make it look ok.

from joplin-utils.

I have implemented a function to automatically repair file extensions based on mime in batches, you can try it

https://joplin-utils.rxliuli.com/web/joplin-batch-web/#/en-US/fixFileExtension

from joplin-utils.

@rxliuli Thanks for your efforts. I've actually decided to switch to Obsidian for now.

from joplin-utils.