Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change in config.lua breaks the plugin and user patch doesn't work. #25

Open
SalomoDavidson opened this issue May 18, 2024 · 6 comments

Comments

@SalomoDavidson
Copy link

Hi!
When I change the settings in the config.lua, the plugin doesn't give me the option add to Anki anymore, but it shows add to vocabulary builder. Also user patch doesn't work for me.
Thanks in advance for helping me out :)

@SalomoDavidson
Copy link
Author

With changing the settings in the config I mean change the word_field, context_field etc.

@nairyosangha
Copy link
Member

Please provide the crash.log file created by KOreader.

crash.log is a file that is automatically created when KOReader crashes. It can normally be found in the KOReader directory:

  • /mnt/private/koreader for Cervantes
  • koreader/ directory for Kindle
  • .adds/koreader/ directory for Kobo
  • applications/koreader/ directory for Pocketbook

User patch isn't gonna work if the plugin failed to load, and vocabulary builder showing up (which is a separate plugin bundled with KOreader itself) is a good hint that we indeed did fail to load. Probably you messed something up in the config.lua file. The crash.log might tell us what's wrong.

I've had to ask for people to post their crash.log one too many times, so I've finally set up issue templates now 😄
This is the push I needed

@Peance
Copy link

Peance commented Oct 2, 2024

Hi, I'm encountered with the same issue. Please find attached my crash.log.
crash.log

Thanks in advance for your time and energy!

@nairyosangha
Copy link
Member

Do you remember what you changed, did you change the word_field while still having other notes stored locally on the device by any chance? This may be a bug. The plugin keeps track of the word field on locally stored notes to have a simple form of duplicate checking. However if that field's name changes it's not gonna find it on older notes and it would crash

@Peance
Copy link

Peance commented Oct 3, 2024 via email

@nairyosangha
Copy link
Member

Can you try checking out the latest commit, that should hopefully fix your issue. I'm assuming OP had the same problem so I'll close this if you confirm it works for you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants