#ver2.0

Just a heads up before I get multiple messages about this bug and you know that I am looking for it. At the moment, my Fetch Data from AO3 links script does not work well with Not Rated, Explicit and Mature fics, filling only the language, word count and chapters. I suspect that something has changed in the base code in AO3 so I am looking for it.

I hope I can get this problem fixed soon! In the meantime, the easiest way to fill in needed information about those fics is to download an HTML file. That way, when you copy and paste tags, there are commas between them. :)

AO3 has been quite slow this year, and right now, Huurre's Fanfiction Reading Log gives a 525 error from almost every fic. As a workaround, I got tipped in Discord that maybe Transformativeworks could work. I tested it quickly and it worked! You can always change the link to the AO3 link after running the script. :) This way, you should be able to get most of the fics handled by the script.

The Fetch Data script might give the error 525 message. That's something I can't do anything about; it's in AO3's end (more in AO3's Tumblr). Run the script again. It might take a few tries before it works.

Also, with higher rating fics, the old script now works at least some of the time. Every fic I tried today filled the fandom that was a problem earlier. I don't know why and how, but let's just take it as it is. :D

Find the blog post also from Huurreauthor.com. There is also a video on how to open the Apps Scripts, otherwise, the contents are the same.

A bit over a week full of work with this. Unfortunately, it's not completed yet, I have some confusing problems with getting Fandom from the AO3 link and it seems that the script is quite slow at the moment. I'm not sure if there's anything I can do about that, but I will try.

So, first things first, what are the changes generally from the previous when thinking about how the script works?

Mature, Explicit and Not Rated fanfics have gotten new HTML at some point. At least I think so, since the script has worked before that well for all open fics. New HTML has only the date of the last update/completed. It means that these fanfics will not have a Published date.

Since I am going to publish the complete bug fix hopefully within the next two weeks, the script has only one Fetch Data script that has fandoms mentioned in the tags. This is just to make my work easier at the moment. :)

The script doesn't fetch Fandom at the moment. This is the main thing I'm going to fix with the next update. I'm pretty sure the fault lies in me with this as I couldn't get it to work, but a bit more time will help.

Popup when the fanfic is locked! This is a really good thing. I've got a message a few times that the script didn't do anything and then soon afterwards "Whoops, it was actually locked". Now that popup will tell you that the fic is locked and you have to fill in the information manually.

Lower rating fics are handled the same as previously, no changes there.

How to fix the script?

To make everything easier, I have downloaded the whole script to Google Drive where you can copy the whole code and replace the old code with it.

1. Open your file.

2. Choose Extensions > Apps Script from the top.

It opens a new window which can be a bit overwhelming at first.

3. Choose custom menu.gs from the left side panel.

4. Delete everything from that script.

5. Go to Google Drive through this link. Copy everything. (F.e. CTRL/CMD + A and then CTRL/CMD + C)

6. Go back to the tab where you have the script open. Paste the new content.

7. Save the script as shown in the picture below.

8. Close the tab and update the file page. The Fanfiction Management menu might take a few minutes to appear.

You have no idea how much I love that I've arranged a chance to report bugs so easily through the form that's linked in the Home tab in the file. I should probably figure out something that the form would note me if there is a new submission, but I usually check it almost daily and I hope (fingers crossed now that I say this) that there will be no acute bugs at any point. But yes, with these words to the bug that I checked now (and as always, I've edited this to the original files):

One of the users informed me that when you use all four reading statuses (TBR/Reading/Read/Did not finish), the Status Statistics box in the Home tab gives a reference error. I have no logical reason why UNIQUE formula would pick up five values when there are only four of them but it does.

The reason is my warning cell which is right under it so the fix is quite easy. I added the warning later, on January 3rd probably, so if you've made your copy before that, you don't have any problems. That's also the reason why this got through my fingers. :D

SO. There are technically two options: you can either delete the warning (it was mostly to notify everyone about that so no one would need to start their file again for deleted columns) completely/move the text to the Instructions tab OR if you want it to be as a reminder, unmerge the cell, move the text from cell J12 to J13 and merge J13:L15 again.

You can find the same blog post from Huurreauthor.com.

The first week after the release was definitely the busiest with bug reports and fixing them. There is one bug that has been such a nuisance and I'm still trying to get it fixed. It appears in the General Statistics tab with the Most popular in this fandom with some fandoms. I'm trying to map out if there is a specific pattern for this, so please, if you notice this bug, report it through the Bug Report form with the information of with fandom it appears.

I've got also some reports from the Fetch Data script when it doesn't do what it should and gives an error message TypeError: Cannot read properties of undefined (reading 'forEach'). So far it seems that it's maybe something on AO3's end (for example slowness as they have also reported that AO3 has been slow lately). So far the script has worked to the same link some time later.

If the script doesn't get the data to the file and does not show any error messages, the fanfic is most likely locked and therefore the script doesn't work on it.

I've got multiple good questions about the uses of different things and "Can I do this or that" in both Discord and Tumblr. I will gather them together soon, probably doing some kind of a collection blog post. Tumblr is a really good place to ask anything anonymously, but it is also possible through the Request a feature or leave feedback form that is linked to the file's Home tab. You don't need to leave your contact information and if there is a question without an email address, I will answer it at least in Tumblr. :) 

But now! To the real bug fix! I did this a bit differently because there were so many formulas to fix. For some reason, Most Popular Fandom and Most Popular Pairing have been giving random results in Yearly Statistics. These are already fixed to the public files so you can always make a new copy for yourself and copy fic information from your old file to the new one. I simplified the formulas a lot, although it meant also leaving out something. In this case, it doesn't count re-read fics when looking for the most common value. However, it will count them when the most common value is found.

First of all, you can find all the formulas and probably good enough instructions from this Google Sheets File. You can copy & paste fixed formulas for every year to the hidden support area you can find when you open the Yearly Statistics tab and click a small arrow in the top right corner. 

You can find the specific cell you should choose (but only click it once to choose it, not twice to activate it!) from the file. Note that the location is slightly different depending on if you have starting from 2024 or starting from 2025 version.

For additional help, please see the video below and if you need help further, please send an email or join my Discord! We can do it over screen share too, if necessary. (Though, it's not my favourite option and I can imagine that it's not that for other people either, especially with completely random, so I always try to get the problem sorted without that.)

You can find this post also from my website: https://www.huurreauthor.com/news/fix-for-all-time-statistics

Someone informed me that when copying the formulas and codes from Tumblr posts, the quotation marks turn wrong. You're still free to check out the steps in this post.

Bug after bug after bug. I am really thankful for the Discord Server where people have reported these problems whenever they notice anything amiss or wrong. Without them, it would be a lot more difficult to find them. You can join our Discord server through this link. I'm keeping also a master list of all known bugs there for everyone to see. While I'm quick to fix them at the moment, I don't see it necessary to keep that kind of list in the blog. However, I've now collected all the bug-fix posts to the Help page of my website too! 

One of the users noticed that they had wrong values in All Time Statistics in the Yearly Statistics tab. Some fighting and figuring out later, I'm here to give you fixes. First of all, I left the hidden support columns in the Yearly Statistics tab in such a messy state that I'm embarrassed that you have to see them, but... well, nothing I can do now. So, let's get to work, you know the jazz, I'll give you every step and cell and formula and you'll just follow them and hopefully it will work out! As always, these are already fixed to public files so you can always go to make a new copy for yourself and check out from there how they are set.

1. Grab the Yearly Statistics tab and open hidden columns.

2. Scroll to the right until you see columns Y, Z, AA, AB, AC and AD.

3. In the 2024 version, choose cell Z19. In the 2025 version, choose cell Z3. Hox! On the left side of them, is the text Fandom. Replace the old formula with this one:

=IFERROR(INDEX(UNIQUE(FILTER(R_Fandom, F_ReadingStatus="Read")), MATCH(MAX(COUNTIF(FILTER(R_Fandom, F_ReadingStatus="Read"), UNIQUE(FILTER(R_Fandom, F_ReadingStatus="Read")))), COUNTIF(FILTER(R_Fandom, F_ReadingStatus="Read"), UNIQUE(FILTER(R_Fandom, F_ReadingStatus="Read"))), 0)),"")

4. Go to one row down, so in the 2024 version cell Z20 and in the 2025 version cell Z4. Replace the old formula with this one:

=IFERROR(INDEX(UNIQUE(FILTER(S_MainPairing, F_ReadingStatus="Read")), MATCH(MAX(COUNTIF(FILTER(S_MainPairing, F_ReadingStatus="Read"), UNIQUE(FILTER(S_MainPairing, F_ReadingStatus="Read")))), COUNTIF(FILTER(S_MainPairing, F_ReadingStatus="Read"), UNIQUE(FILTER(S_MainPairing, F_ReadingStatus="Read"))), 0)),"")

5. Go to one row down, so in the 2024 version cell Z21 and in the 2025 version cell Z5. Replace the old formula with this one:

=IFERROR(INDEX(UNIQUE(FILTER(O_Rating, F_ReadingStatus="Read")), MATCH(MAX(COUNTIF(FILTER(O_Rating, F_ReadingStatus="Read"), UNIQUE(FILTER(O_Rating, F_ReadingStatus="Read")))), COUNTIF(FILTER(O_Rating, F_ReadingStatus="Read"), UNIQUE(FILTER(O_Rating, F_ReadingStatus="Read"))), 0)),"")

I know, I might often overdo formulas, stacking them on top of each other more than would be needed, but it's better to be safe than sorry.

I would like to remind you now that when counting the most appearing values, it only takes first-time reads into account. While counting how many of them are read will also count rereads. With Most read fandom, pairing and rating in All time statistics, it counts only first-time reads so basically the reading statuses. I will probably edit formulas one day to count in rereads too but it's something for a later date.

I'm also sorry for all the times I wrote raiting instead of rating! English is not my first language and I'm often having problems with that specific word.