[GUI Plugin] FanFicFare

[frenchtoast]

Thank you all for the replies! I do indeed have Kobo Utilities. But when I do the above - say I have a WIP marked as finished in Kobo, when a new chapter comes in and I update it with new chapter, it's still marked as finished on Kobo. The "restore current bookmark" doesn't seem to work cos I see the Kobo reading location reads something like "OEBPS/title_page.xhtml#kobo.1.1" or OEBPS/cover.xhtml#kobo.1.1 which opens the book to the cover page. Is there any workaround to this other than manually setting it to the last page before I update the book?

[marshie250]

Originally Posted by frenchtoast

Thank you all for the replies! I do indeed have Kobo Utilities. But when I do the above - say I have a WIP marked as finished in Kobo, when a new chapter comes in and I update it with new chapter, it's still marked as finished on Kobo. The "restore current bookmark" doesn't seem to work cos I see the Kobo reading location reads something like "OEBPS/title_page.xhtml#kobo.1.1" or OEBPS/cover.xhtml#kobo.1.1 which opens the book to the cover page. Is there any workaround to this other than manually setting it to the last page before I update the book?

That is something that happens- I have an action chain that changes the bookmark for me, so the newest chapter opens up when I click the book. Its a bit involved, however. Do you have a custom column set up for Kobo Utilities to record the Current reading location?

[frenchtoast]

Yep I do!

[bpothier]

Have an odd issue w/ SOL adapter (yeah, yeah.. your *FAVORITE* one..
For paid users, there is an option to pop-up a reminder when their account is XX (default 3 days, but I bumped mine to 30...) days before expiration/renewal.
During this time, FFF "breaks" as story access goes to an intermediate page during the notification timeframe.
There is a link to "renew now" or "remind later"(url = /sol-secure/user/later.php?refer= ORIGPATH).

<h3 class="c">Notification!</h3>
<h4 class="c">Your premier membership is going to expire in less than 30 days</h4>
<h4 class="c"><a href="https://storyroom.com/sol-secure/subscribe.php">Renew</a> &nbsp; &nbsp; <a href="https://storyroom.com/sol-secure/user/later.php?refer=%2Fn%2F11600%2Fpollyanna">Remind Me Later</a></h4>

I was trying to add checks for it within performLogin, but they did not trip.
The intermediate page only shows when "doExtractChapterUrlsAndMetadata" accesses an actual story URL...
I tried adding the "Your premier membership is going to expire" to list of errors in "needToLoginCheck", but this doesn't really alert user to *why* it failed..
Using web, clicking the remind later link then allows direct story accesses.
It appears that the "later.php" sets a 48h or so cookie (called "pena") that will allow story accesses without the intermediate page.

Is there a way - within Calibre plugin - to raise an exception/pop-up to the user and still allow the connection thru (by accessing the later.php and getting the cookie...)?

Or maybe access the "later.php" page, silently accept the cookie and then fail the job - and user can see the error message and then re-initiate?

I saw the TOTP code, but not sure this works with Calibre - and is also in login code, not chapter code..

[JimmXinu]

Originally Posted by bpothier

Have an odd issue w/ SOL adapter (yeah, yeah.. your *FAVORITE* one..
For paid users, there is an option to pop-up a reminder when their account is XX (default 3 days, but I bumped mine to 30...) days before expiration/renewal.

This is an *optional* SOL feature? Not a default setting?

Because in that case, I'm going to say the obvious solution is "don't turn that feature on", just like FFF doesn't try to support all themes/skins for all sites.

But if somebody codes a solution for this, I'll accept it.

[JimmXinu]

New Test Version Posted

2025-10-10
- OTW(AO3): Accept /chapter/999 URLs without /works/999 for #1258 -- Use download link to get storyId.

[bpothier]

Originally Posted by JimmXinu

This is an *optional* SOL feature? Not a default setting?

Because in that case, I'm going to say the obvious solution is "don't turn that feature on", just like FFF doesn't try to support all themes/skins for all sites.

But if somebody codes a solution for this, I'll accept it.

For paid users, it defaults to 3 days. If your account expires, it defaults to "free" mode and is subject to the random "mangling" feature it implements for suspected "bots" (adds typos, etc..) ... I increased mine to 30 days as a reminder after it happened last year..

Currently, FFF reports the usual "NoneType object is not subscriptable" error during this pop-up phase, so not very helpful. I suppose adding an Exception type would at least allow reporting back *why* it failed (e.g. , but looking to add the minimum additional code to facilitate future maintenance... Likely at a minimum, would require adding exception class and handler and triggering the exception in the chapter function.

Looks like something similar to how "exceptions.AdultCheckRequired" uses "question_dialog_all" may be able to interactively prompt to accept/bypass the expire warning... well, I have 20+ days to work on and test it

For now, reducing the expiration notice time allows FFF to process normally.

[JimmXinu]

Originally Posted by bpothier

Looks like something similar to how "exceptions.AdultCheckRequired" uses "question_dialog_all" may be able to interactively prompt to accept/bypass the expire warning... well, I have 20+ days to work on and test it

For now, reducing the expiration notice time allows FFF to process normally.

I'm not interested in adding a new exception path to bubble this up to the UI level--it's too niche.

I'd accept a specific download failure exception message, it could include a brief mention of turning off the reminder. Or (optional?) bypass code.

[bpothier]

Pull 1262 created for basic alert message to user by just calling existing "exceptions.FailedToDownload" with appropriate description.

Trying to access the "remind later" URL to get the cookie set is failing to use the cookie in subsequent request calls. Not sure if SOL adapter is configured to use the cookiejar?
I tried calling "self.get_request(remindurl)" (to 'set' the remind me later cookie) then "self.get_request(url,usecache=False)" again with no change.

[estherflails]

FFF can't seem to detect Ao3 fics as Marked for Later anymore. A while back I did notice that the button changed (I use a dark theme and just that button turned white) so it seems it works slightly differently now. I changed the code a bit, this version works for now!

self.story.setMetadata('markedforlater',
                                   None != metasoup.find('button',text='Mark as Read'))

[marshie250]

Has anyone had luck configuring include_logpage: smart ?
the "smart" is not turning green for me, but true and false are.

[JimmXinu]

Multi-reply!

Originally Posted by bpothier

Pull 1262 created for basic alert message to user by just calling existing "exceptions.FailedToDownload" with appropriate description.

Trying to access the "remind later" URL to get the cookie set is failing to use the cookie in subsequent request calls. Not sure if SOL adapter is configured to use the cookiejar?
I tried calling "self.get_request(remindurl)" (to 'set' the remind me later cookie) then "self.get_request(url,usecache=False)" again with no change.

I'll look at it tomorrow.

Originally Posted by estherflails

FFF can't seem to detect Ao3 fics as Marked for Later anymore. A while back I did notice that the button changed (I use a dark theme and just that button turned white) so it seems it works slightly differently now. I changed the code a bit, this version works for now!

Only visible if you have History enabled in AO3, FYI.

It's a form now instead of a link. I'd rather keep it looking for the URL instead of text:

            self.story.setMetadata('markedforlater',
                                   metasoup.find('form', href=re.compile(r'/mark_as_read$')) is not None)

Also something I'll do tomorrow.

Originally Posted by marshie250

Has anyone had luck configuring include_logpage: smart ?
the "smart" is not turning green for me, but true and false are.

There are complexity limits to the highlighting code used. 'Other' settings like that don't high light; only standard metadata entry names and true/false get the green highlight.

FFF will, however, warn you and prompt to change it if do try to use values other than true/false/smart for include_logpage.