obsidian-ocr icon indicating copy to clipboard operation
obsidian-ocr copied to clipboard

Can't load plugin

Open Sunstroke98 opened this issue 1 year ago • 13 comments

Hi,

I tried installing the plugin through the community plugin tab directly on obsidian. I then downloaded tesseract as well as imagemagick from the links provided on the plugin page I added them to the path using the tutorial provided as well. However, when i try to enable the plugin i get the message:

image

I tried running the debugging console and it gives me the following message:

image

I'm guessing i didnt correctly add the executables to the path but i cant figure out what to change, could you help out?

Sunstroke98 avatar Jan 23 '24 19:01 Sunstroke98

Receiving the same error as shown above after installing the dependencies and adding them to the system path.

FranticPanic avatar Feb 22 '24 04:02 FranticPanic

Same issue happening for me.

gavinwright-engr avatar Mar 13 '24 19:03 gavinwright-engr

same issue for me ... just installed plugin and tried to enable it and got this error

fredjoe7 avatar Mar 24 '24 07:03 fredjoe7

Thank you for your issue. Can you please create a log file by enabling file logging in the settings and rerunning the steps that lead to the issue. After that you should have a log file in your vault. Please upload it to GitHub gists and link it here.

MohrJonas avatar Mar 28 '24 06:03 MohrJonas

Does anyone sent you the logfile @MohrJonas? I've got the same issue both with the automatic and the manuel installation process in Windows ...

P.S.: I think the idea behind your plug-in has great potential. Thank you! :)

mjelp0147854 avatar Apr 09 '24 04:04 mjelp0147854

@MohrJonas Tried installing today using the recommended flow on windows 10 and facing same issue, exe are in path however getting the absolute path error, i will try and log the install and get back to you if i can work through it, plugin looks great from the outside!

Wingout avatar Apr 15 '24 21:04 Wingout

Thank you for you kind words. Getting the log and (hopefully) finally resolving this issue would be great 😁

MohrJonas avatar Apr 16 '24 20:04 MohrJonas

About the log file, how do we enable file logging in Obsidian settings? I can't see it anywhere... I notice no-one else has linked a file to this thread yet. I'm also having the same problem.

Here's the console log shown in the screenshot anyway: https://gist.github.com/planetClaire/84c7435eb9902825a4c56944961ce9ce

Thank you for your issue. Can you please create a log file by enabling file logging in the settings and rerunning the steps that lead to the issue. After that you should have a log file in your vault. Please upload it to GitHub gists and link it here.

planetClaire avatar May 02 '24 08:05 planetClaire

About the log file, how do we enable file logging in Obsidian settings? I can't see it anywhere... I notice no-one else has linked a file to this thread yet. I'm also having the same problem.

Here's the console log shown in the screenshot anyway: https://gist.github.com/planetClaire/84c7435eb9902825a4c56944961ce9ce

Thank you for your issue. Can you please create a log file by enabling file logging in the settings and rerunning the steps that lead to the issue. After that you should have a log file in your vault. Please upload it to GitHub gists and link it here.

I see from another issue that the logging is in the plugin options, but the options aren't available until it's enabled.

planetClaire avatar May 02 '24 08:05 planetClaire

Yes, you're correct that the settings are only available when the plugin loads successfully. This, however is also valuable information, because now we know that the error happens before loading the settings.

MohrJonas avatar May 02 '24 16:05 MohrJonas

Yes, you're correct that the settings are only available when the plugin loads successfully. This, however is also valuable information, because now we know that the error happens before loading the settings.

Thanks for your reply. Just FYI, both tesseract and imagick are in my path.

planetClaire avatar May 02 '24 22:05 planetClaire

I followed line numbers from error in console image

At line 64610 in main.js is function external_node_path_namespaceObject.dirname with path to some local developer's directory And in line 64774 same thing

I replaced calls to those functions with empty string and plugin start to work

image

Sergeybond97 avatar Jun 12 '24 14:06 Sergeybond97

I followed line numbers from error in console image

At line 64610 in main.js is function external_node_path_namespaceObject.dirname with path to some local developer's directory And in line 64774 same thing

I replaced calls to those functions with empty string and plugin start to work

image

You hero.

py9mrg avatar Jun 14 '24 16:06 py9mrg