[GUI Plugin] FanFicFare

[BigBee]

2025-04-23
- adapter_archiveofourownorg: Add use_archiveofourown_gay, allow archiveofourown.gay input for story URLs.

Other users seem to have gotten this to work, but I cannot. Provides the same "HTTP Error in FFF '525 Server Error:" that attempting to use use_archive_transformativeworks_org results in on affected stories. For now cache is working but is quite inconvenient when updating a large number of stories at once.

I understand this is an ongoing issue with Ao3, but just wanted to throw out that this was not a perfect workaround.

FYI, I've added a new wiki page titled ProblematicSites to try to document the ongoing (and going and going) problems, especially with ffnet and AO3.

I do appreciate the new ProblematicSites page. This is my first post here, but I have frequented this thread over the years, and the most difficult part was always tracking down all the elements needed for hotfixes in one coherent order. Every issue being jammed in one thread makes it hard to navigate and keep track of who is responding to what issues, and what pieces you actually need. User-friendly would be the term, I suppose.

[ownedbycats]

Originally Posted by JimmXinu

FYI, I've added a new wiki page titled ProblematicSites to try to document the ongoing (and going and going) problems, especially with ffnet and AO3.

I've also done some moderate editing to the BrowserCacheFeature page and minor editing to the ProxyFeatures page.

Feedback is welcome.

This made me realize that the FanFicFare and eReaders page has spaces in the name, unlike most others. Should this be fixed?

[JimmXinu]

Originally Posted by BigBee

Other users seem to have gotten this to work, but I cannot. Provides the same "HTTP Error in FFF '525 Server Error:" that attempting to use use_archive_transformativeworks_org results in on affected stories. For now cache is working but is quite inconvenient when updating a large number of stories at once.

How many downloads/updates were you doing?

Originally Posted by BigBee

I do appreciate the new ProblematicSites page. This is my first post here, but I have frequented this thread over the years, and the most difficult part was always tracking down all the elements needed for hotfixes in one coherent order. Every issue being jammed in one thread makes it hard to navigate and keep track of who is responding to what issues, and what pieces you actually need. User-friendly would be the term, I suppose.

While one could argue that individual named threads for each issue would prevent duplication of reporting, the fact I can have 2 or 3 people open github issues for the same problem argues against it. Ditto all the duplicate threads that happen on MR in general.

There are pros and cons and I don't currently seen enough to motivate a change.

Originally Posted by ownedbycats

This made me realize that the FanFicFare and eReaders page has spaces in the name, unlike most others. Should this be fixed?

I wouldn't bother. There are several others.

[ownedbycats]

Question: Sometimes see "Title", enclose entire title. Regex to remove those without affecting other quotation marks?

[JimmXinu]

Probably a regexp something like:

 ^"(.*?)"$=>\1

I'd need an example story to experiment with to tell for sure.

[wildfire070]

Originally Posted by JimmXinu

FYI, I've added a new wiki page titled ProblematicSites to try to document the ongoing (and going and going) problems, especially with ffnet and AO3.

I read through the wiki on this and copy/pasted the code listed to use archiveofourown.gay, but came up with errors. Seems that there's a typo on the wiki.

The code listed is

use_archiveofourown_gay_org:true

but should be

use_archiveofourown_gay:true

After removing the "_org" part, it works great. I'm glad I don't have to mess with the browser cache anymore.

[JimmXinu]

Originally Posted by wildfire070

I read through the wiki on this and copy/pasted the code listed to use archiveofourown.gay, but came up with errors. Seems that there's a typo on the wiki.

The code listed is

use_archiveofourown_gay_org:true

but should be

use_archiveofourown_gay:true

After removing the "_org" part, it works great. I'm glad I don't have to mess with the browser cache anymore.

Thanks, fixed.

[JimmXinu]

New Test Version Posted

2025-04-26
- Remove base_xenforoforum_adapter, consolidate into base_xenforo2forum_adapter

All of the supported XenForo sites are on XF2 now.

Ideally, it should be an invisible change from the outside. But I think the INI precedence order of [base_xenforo2forum] vs [<site>] and [base_xenforoforum] may have been wrong before. Seems rather unlikely anyone is depending on that.

[BigBee]

Originally Posted by JimmXinu

How many downloads/updates were you doing?

I tend to update in batches so I can keep up with tag maintenance (I add a lot of custom tags and updating erases them). Initially I tried to do 10 at a time, which has historically been my go to, and when that failed I pared it down to 5, and when that didn't work, to 1. None worked with the archiveofourown.gay method. Actually, it was worse than the transformativeworks.org method, as the .gay one wouldn't even download unlocked works, which transformativeworks can still do.

Cache method slows things down because I have to do them one at a time or it makes using my browser nigh-impossible, as I have to use the 'open page' method to make it work. It's not some insurmountable thing, more of a convenience thing since I can't really walk away to do other things what with the tag updates I do. That's my own fault, though.

Originally Posted by JimmXinu

While one could argue that individual named threads for each issue would prevent duplication of reporting, the fact I can have 2 or 3 people open github issues for the same problem argues against it. Ditto all the duplicate threads that happen on MR in general.

There are pros and cons and I don't currently seen enough to motivate a change.

Understandable, there is no perfect solution that will work for everyone and every problem that happens. I do think having a set location for issues regarding the most common issues/sites makes sense, though, for casual readers of the thread who just want fixes and not necessarily want to understand the how/why discussion. I imagine the average reader is not programming/web savvy enough to parse everything said in this thread but is somewhat capable of following instructions (like me).

[Ghostcat]

Originally Posted by BigBee

... (I add a lot of custom tags and updating erases them)...

Do you have the "Keep the Existing Tags when Updating Metadata" box checked in FFF Configure?

FFF does not erase any of my custom tags.