rudism/freshrss-kagi-summarizer
1
1
Fork 0
Code Issues 1 Pull requests Projects Releases 3 Packages Wiki Activity

kagi_strings is not defined #4

New issue
Open
opened 2025-01-10 07:30:55 -06:00 by felipem775 · 9 comments
felipem775 commented 2025-01-10 07:30:55 -06:00
Copy link

Hi,
I installed the plugin and configured it.
Using chrome and edge I get this error:

ext.php?f=freshrss-kagi-summarizer%2Fstatic%2Fscript.js&t=js&1736340048:65 Uncaught ReferenceError: kagi_strings is not defined
at summarizeButtonClick (ext.php?f=freshrss-kagi-summarizer%2Fstatic%2Fscript.js&t=js&1736340048:65:30)
at HTMLDivElement. (ext.php?f=freshrss-kagi-summarizer%2Fstatic%2Fscript.js&t=js&1736340048:14:11)

I can see the button and press it but nothing success. If I open in new tab I can read the response json.

Hi, I installed the plugin and configured it. Using chrome and edge I get this error: ext.php?f=freshrss-kagi-summarizer%2Fstatic%2Fscript.js&t=js&1736340048:65 Uncaught ReferenceError: kagi_strings is not defined at summarizeButtonClick (ext.php?f=freshrss-kagi-summarizer%2Fstatic%2Fscript.js&t=js&1736340048:65:30) at HTMLDivElement.<anonymous> (ext.php?f=freshrss-kagi-summarizer%2Fstatic%2Fscript.js&t=js&1736340048:14:11) I can see the button and press it but nothing success. If I open in new tab I can read the response json.
rudism commented 2025-01-11 07:03:08 -06:00
Owner
Copy link

What version of FreshRSS are you using?

What version of FreshRSS are you using?
felipem775 commented 2025-01-11 07:11:03 -06:00
Author
Copy link

1.23.2-dev

1.23.2-dev
rudism commented 2025-01-17 07:55:30 -06:00
Owner
Copy link

Any chance you could try upgrading to the latest FreshRSS release (1.25.0) and see if the problem persists? I'm not able to reproduce any problems and don't have an easy way to test against older versions.

You could also try v0.2 of this extension and see if that works for you--it's possible that the custom CSS stuff I added in the latest release doesn't work correctly in older versions of FreshRSS (but v0.2 had been working for me as far back as v1.22.0 of FreshRSS).

Any chance you could try upgrading to the latest FreshRSS release (1.25.0) and see if the problem persists? I'm not able to reproduce any problems and don't have an easy way to test against older versions. You could also try v0.2 of this extension and see if that works for you--it's possible that the custom CSS stuff I added in the latest release doesn't work correctly in older versions of FreshRSS (but v0.2 had been working for me as far back as v1.22.0 of FreshRSS).
felipem775 commented 2025-02-08 08:24:12 -06:00
Author
Copy link

I updated to 1.25.1-dev. I don't know if -dev can have any issue but the problem persist (It's a clean installation in a new maquine)

I updated to `1.25.1-dev`. I don't know if `-dev` can have any issue but the problem persist (It's a clean installation in a new maquine)
rudism commented 2025-02-12 11:31:03 -06:00
Owner
Copy link

@felipem775 do you configure your FreshRSS with a non-en language?

If so I bet this is a problem with translation/language settings. The extension only has English strings defined, so I wonder if I have something misconfigured where non-english installations are trying to load translations that don't exist.

@felipem775 do you configure your FreshRSS with a non-`en` language? If so I bet this is a problem with translation/language settings. The extension only has English strings defined, so I wonder if I have something misconfigured where non-english installations are trying to load translations that don't exist.
rudism commented 2025-02-12 11:40:06 -06:00
Owner
Copy link

Could you try setting the "Output language" in the extension's settings to "English" instead of "Default" (or something else) and see if that fixes the issue for you? I think I just need to remove that option unless I actually add translations of the strings.

Edit: Actually that setting may be unrelated to FreshRSS, it should only affect the output language of the actual summaries provided by Kagi. I may need to do further research to figure out why FreshRSS is trying to load non-existent translations if it turns out that is the problem.

~~Could you try setting the "Output language" in the extension's settings to "English" instead of "Default" (or something else) and see if that fixes the issue for you? I think I just need to remove that option unless I actually add translations of the strings.~~ Edit: Actually that setting may be unrelated to FreshRSS, it should only affect the output language of the actual summaries provided by Kagi. I may need to do further research to figure out why FreshRSS is trying to load non-existent translations if it turns out that is the problem.
rudism commented 2025-02-12 12:08:58 -06:00
Owner
Copy link

I just tested using a fresh 1.25.1-dev docker instance, setting the language to Deutsch instead of English, but was still unable to reproduce the issue. The extension worked OK and showed the English strings, so I don't think missing or misconfigured extension translations is the problem.

Maybe you can walk me through the steps taken on the fresh install that reproduced the problem for you so I can follow along and see if I can get the problem to happen for me that way?

I just tested using a fresh 1.25.1-dev docker instance, setting the language to Deutsch instead of English, but was still unable to reproduce the issue. The extension worked OK and showed the English strings, so I don't think missing or misconfigured extension translations is the problem. Maybe you can walk me through the steps taken on the fresh install that reproduced the problem for you so I can follow along and see if I can get the problem to happen for me that way?
felipem775 commented 2025-02-12 15:35:19 -06:00
Author
Copy link

I use docker with image: freshrss/freshrss:edge (I don't know why choose it) Which version do you want me to try?

I use docker with `image: freshrss/freshrss:edge` (I don't know why choose it) Which version do you want me to try?
rudism commented 2025-02-12 15:54:52 -06:00
Owner
Copy link

Hmm, that is the same image I used.

> mkdir data ext

> docker run -d --net=host -e TZ=America/Chicago -v "$PWD/data:/var/www/FreshRSS/data" -v "$PWD/ext:/var/www/FreshRSS/extensions" freshrss/freshrss:edge

> cd ext && git clone https://code.sitosis.com/rudism/freshrss-kagi-summarizer.git

Followed by going to localhost:80 and creating an admin account, then logging in and going to extension config, enabling the Kagi Summarizer, then configuring my Kagi account token.

I was able to then go back to the feed list which showed the default feed of all the FreshRSS version update notes, and clicking "Summarize" summarized the posts without any error.

Is that similar to how you're setting it up?

Hmm, that is the same image I used. ``` > mkdir data ext > docker run -d --net=host -e TZ=America/Chicago -v "$PWD/data:/var/www/FreshRSS/data" -v "$PWD/ext:/var/www/FreshRSS/extensions" freshrss/freshrss:edge > cd ext && git clone https://code.sitosis.com/rudism/freshrss-kagi-summarizer.git ``` Followed by going to `localhost:80` and creating an admin account, then logging in and going to extension config, enabling the Kagi Summarizer, then configuring my Kagi account token. I was able to then go back to the feed list which showed the default feed of all the FreshRSS version update notes, and clicking "Summarize" summarized the posts without any error. Is that similar to how you're setting it up?
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v0.3
v0.2
v0.1
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: rudism/freshrss-kagi-summarizer#4
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?