Wallabag KOReader sync behaviour

jt196 · 02-10-2025, 03:34 AM

A little late to the party here but I'm trying to figure out how to sync finished status to Wallabag. I'm running a Kindle PW2.

How do most folks manage this?

My first thought was to uncheck "Remotely Delete Finished Articles", then either mark a wallabag article as finished, or delete it. Upon sync (I assume Retrieve articles is the sync method), I expected the article to be marked as finished in Wallabag, but it wasn't. The article was simply redownloaded onto the KOReader device, nothing happened inside Wallabag. If I run the retrieve with finished articles, nothing happens remotely, no articles are downloaded either.

When I check the Remotely Delete option, the deletion works in Wallabag.

Am I missing something here? The wiki doesn't really explain reading/syncing workflow.

I guess ideal behaviour would be either:

1. The plugin removes finished articles from the device, marks it as finished remotely and downloads an article to replace the old one.
2. As above but the finished article remains on the device.

Frenzie · 02-10-2025, 06:43 AM

Just a note, current nightlies have quite a few changes relating to Wallabag.

jt196 · 02-10-2025, 12:32 PM

OK Thanks @Frenzie, looks like they've added an "Upload article statuses to server" which does exactly what I was mentioning in 1, only you have to click the "Download new articles from server" to add more.

I've had a bunch of crashes since installing it the other day, I'm hoping that a fresh (apart from copied settings) install of the KOReader nightlies might help things. Otherwise, I guess it's off to the GitHub issues page for me.

02-10-2025, 03:34 AM	#1
jt196 Junior Member Posts: 2 Karma: 10 Join Date: Feb 2025 Device: Kindle PW2	Wallabag KOReader sync behaviour A little late to the party here but I'm trying to figure out how to sync finished status to Wallabag. I'm running a Kindle PW2. How do most folks manage this? My first thought was to uncheck "Remotely Delete Finished Articles", then either mark a wallabag article as finished, or delete it. Upon sync (I assume Retrieve articles is the sync method), I expected the article to be marked as finished in Wallabag, but it wasn't. The article was simply redownloaded onto the KOReader device, nothing happened inside Wallabag. If I run the retrieve with finished articles, nothing happens remotely, no articles are downloaded either. When I check the Remotely Delete option, the deletion works in Wallabag. Am I missing something here? The wiki doesn't really explain reading/syncing workflow. I guess ideal behaviour would be either: 1. The plugin removes finished articles from the device, marks it as finished remotely and downloads an article to replace the old one. 2. As above but the finished article remains on the device.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[GUI Plugin] KOReader Sync	kyx84	Plugins	23	02-07-2025 03:26 PM
Wallabag not working with KOreader in Kobo Forma	Hhvh	KOReader	7	06-12-2024 11:23 AM
What KOReader sync server?	dmpop	KOReader	4	04-28-2022 08:17 AM
can anyone get koreader + wallabag + https://bag.g3l.org/ working?	arooni	KOReader	1	09-04-2021 07:28 AM
Koreader only for cloud sync	LnZ	KOReader	3	02-21-2019 07:09 AM

02-10-2025, 06:43 AM	#2
Frenzie Wizard Posts: 1,726 Karma: 730679 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	Just a note, current nightlies have quite a few changes relating to Wallabag.

02-10-2025, 12:32 PM	#3
jt196 Junior Member Posts: 2 Karma: 10 Join Date: Feb 2025 Device: Kindle PW2	OK Thanks @Frenzie, looks like they've added an "Upload article statuses to server" which does exactly what I was mentioning in 1, only you have to click the "Download new articles from server" to add more. I've had a bunch of crashes since installing it the other day, I'm hoping that a fresh (apart from copied settings) install of the KOReader nightlies might help things. Otherwise, I guess it's off to the GitHub issues page for me.