Thank you for putting this work around out there. This worked for me.
Incidentally, I did try the browser cache path first, but it could never find the stories in the cache, even after making sure they were open in the browser and that I had gone through each of the chapters to load into cache.
I use the same feature for FF.net with no issues in FFF(issues caused by FF.net is another can of worms), so not sure why AO3's browser option failed me.
As I alluded to above, I've been finding for the last few months, that FF.net is not updating their chapter indexes on chapter 1. New chapters don't show up in the drop down, so FFF thinks the story is already up to date. Have you seen anyone else reporting this issue? I've gone back to some stories 2-3 weeks after an update and still the same issue despite clearing cache and reloading.
Quote:
Originally Posted by JimmXinu
(Very) Test Version Attached
Nobody said anything about the version I posted that did archive.transformativeworks.org as a separate site.
This version has a switch to force the usual archiveofourown.org adapter to instead use archive.transformativeworks.org for all network requests:
Code:
[archiveofourown.org]
use_archive_transformativeworks_org:true
Note that it cannot log in because log in doesn't work on archive.transformativeworks.org.
Other than the actual network reqs, this version still uses and records the normal AO3 domain.
This seems to work for me. I'd like to hear other peoples results.
|