AO3 News

Post Header

Published:
2017-01-05 08:08:45 -0500
Tags:

We deployed several batches of new code over the holidays, the vast majority of which concerned our automated tests and preparations for a major Rails upgrade. Happy New Year!

Credits

  • Coders: Ariana, Cesy, cosette, cresenne, james, potatoesque, Sarken
  • Code reviewers: Ariana, james, Naomi, Sarken
  • Testers: james, Lady Oscar, Sarken

Special thanks to cosette, cresenne, and potatoesque, who have contributed their first pull requests as AD&T volunteers and completed their training!

Details

Tests

  • [AO3-4730] - Made the output of our Cucumber tests more informative by adding the name of each test to the happy green dots that signify a successful run.
  • [AO3-4705] - Added another test for downloading works.
  • [AO3-4761] - Extended the tests for our internal API.
  • [AO3-4762] - Added a test for admins deleting an email address from the invite request queue.
  • [AO3-4707] - Improved test coverage for related works.
  • [AO3-4767] - Ditto for external works.
  • [AO3-4768] - Also improved our tests for displaying series.
  • [AO3-4773] - Extended test coverage for our Known Issues page.
  • [AO3-4777] - Completely unrelatedly, we've added more tests for prompt memes.
  • [AO3-4785] - And for user profiles.
  • [AO3-4722] - We also added more tests covering work-related errors.
  • [AO3-4772] - And more tests for tag set nominations.
  • [AO3-4734] - Also extended coverage for tag sets by removing a bit of code that wasn't actually used. Sneaky!
  • [AO3-4746] - Likewise, we removed several unused pieces of code concerning the display of external authors (i.e. authors of non-AO3 works and AO3 user had added to their bookmarks) and thus increased test coverage through the awesome power of maths.
  • [AO3-4802] - We also added some actual tests for external authors, though.
  • [AO3-4769] - Removed a #TODO comment for test cases that were, actually, done.
  • [AO3-4770] - Same.
  • [AO3-4724] - Sometimes different parts of our rspec tests were getting in each other's way in checking different parts of the code. We've made it easier to have a full reset step between each test to prevent these issues.
  • [AO3-4776] - We'd also run into issues with the tool we use to measure our test coverage and have now taken steps to prevent faulty results if a test has to be retried.

Rails

  • [AO3-4737] - Started the long, grueling path towards a significantly more up-to-date Rails version by rewriting a small part of the code controlling the public Wrangling Guidelines (namely to switch to strong parameters). This will be followed by many, many more small parts of our code, until we're ready for Rails 4.0.
  • [AO3-4752] - Such as the chunk of code controlling abuse reports!
  • [AO3-4753] - And admin settings!
  • [AO3-4755] - And notification banners!
  • [AO3-4756] - And the code for adding and managing languages.
  • [AO3-4757] - Also amended the Preferences code to use strong parameters.
  • [AO3-4758] - Ditto for admin posts, such as this one!
  • [AO3-4759] - Also for Support tickets.
  • [AO3-4763] - And for creating a new pseud.
  • [AO3-4764] - And finally for creating and updating a collection!

A Bug Fix

  • [AO3-4795] - Filtering a user's or collection's works for a particular fandom, character, rating and so on, and then trying to sort that subset of works (e.g. by kudos) would kick you out of the filtered view and back to all works. Now you can filter and sort at the same time again!

Nice.

Known Issues

See our Known Issues page for current issues.

Comment

Post Header

Published:
2016-12-11 05:50:14 -0500
Tags:

We fixed a handful of collection-related bugs, made life a little easier for AO3 admins, and continued to improve our automated test suite.

Credits

  • Coders: Ariana, cosette, james, Naomi, Sarken, Scott, tickinginstant
  • Code reviewers: Ariana, james, Naomi, Sarken, Scott
  • Testers: FishieMishie, Alison, Lady Oscar, mumble

Details

Collections & Challenges

  • [AO3-4686] - The autocomplete for potential matches (in the No Recipient or No Giver tabs for gift exchange matches) would list the available matches in random order. They are now sorted by quality of the match.
  • [AO3-3380] - Posting a work and then quickly editing it to add it to an anonymous collection would result in a subscription notification with the creator's name in the title and "by Anonymous" in the body. Oops. We've now put in an extra check to make sure the work didn't suddenly become anonymous before sending out the subscription email.
  • [AO3-3686] - When signing up for a prompt meme or gift exchange with a pseud that was later deleted, the sign-up would still hang around but the actual prompt would vanish. This was very awkward and shouldn't happen anymore! (Now the whole sign-up will be transferred to the default pseud, as intended.)
  • [AO3-3788] - If a work that had been bookmarked in a collection was later deleted, collection management pages would throw errors, both for the collection maintainer and the bookmarker. That's fixed now.

Imports

  • [AO3-4636] - The importer used by Open Doors for rescuing older fanwork archives tries to detect information about the fanwork from the original archive, sometimes leading to wonky tags being created. Open Doors can now opt to turn off this automatic detection.
  • [AO3-4692] - When importing a work with two or more creators, none of whom has an Archive account, the byline on the work would only show one creator. /o\ We streamlined the byline code and fixed the issue, so credit is now given where credit was due all along.

Admin

  • [AO3-4667] - We've added a button to individual works that Archive admins can use to try and fix indexing issues that would lead, for example, to the work not showing up under the appropriate tag listings. (Note: This applies to cases where a work is not showing up in a tag listing where it should be. If a work is showing up where it should not be, this button will not fix it.)
  • [AO3-4668] - There is now also a button to queue up a whole tag for reindexing.
  • [AO3-4669] - We also gave Archive admins, e.g. Support personnel, a button to sort out some other common issues users write in about. This is still in an experimental stage and includes cases where users run into an error 500 when trying to access their subscription page.
  • [AO3-4721] - Searching for a user by username or email used to show partial matches for the name, but expect exact email addresses. It now shows partial matches for both!
  • [AO3-4703] - There used to be a page in the admin area of the Archive that had been broken for a long time, so we removed all traces of it from the code.

Automated Tests & Refactoring

  • [AO3-4689] - Better tests for deleting a prompt meme.
  • [AO3-4704] - Better tests for the wrangulator.
  • [AO3-4715] - Better tests for challenges.
  • [AO3-4739] - Better tests for skins administration.
  • [AO3-4701] - Better tests for parts of the code that specifically make sure a thing exists before proceeding (because otherwise pandemonium).
  • [AO3-4725] - As above, but specifically for user profiles.
  • [AO3-4717] - The code dealing with the admin section of the Archive was refactored and the related tests were updated.
  • [AO3-4719] - The code for work searches was likewise refactored.

Misc.

  • [AO3-4723] - We added caching to fandom pages. Also, automated tests! \o/
  • [AO3-4232] - On the interstitial adult content warning page, the "If you accept cookies from our site" note was floating oddly on wide screens. It now floats where it should.
  • [AO3-4462] - We retired the Archive 1.0 site skin, in that all the related files were removed from the Archive.
  • [AO3-4474] - When justifying italicised text, the letters would get cut off by a few tiny pixels on the right, as the italics where cheekily pushing the text outside of the justified borders. We have now added a little buffer zone for those extra pixels. \o/

Known Issues

See our Known Issues page for current issues.

Comment

Post Header

Published:
2016-10-30 17:20:42 -0400
Tags:

We fixed a couple of bugs, cleaned up some code, and also added a whole lot of Cucumber tests to our suite. Mmm, veggies!

Credits

  • Coders: Ariana, bingeling, james, Sarken, tickinginstant
  • Code reviewers: Ariana, james, Naomi, Sarken
  • Testers: Lady Oscar, mumble, Rebecca Sentance, Runt, Sarken

Details

Bug Fixes

  • [AO3-3213] - Certain combinations of letters and characters in user-entered tags, such as "a.k.a." would lead to errors when trying to look at work listings for that tag. It was also impossible for wranglers to fix those, so a database admin had to step in. Now these can be wrangled just like any other tags!
  • [AO3-4375] - When logging in for the first time, new users are greeted with a small banner offering tips & tricks about Archive features and options. Our Docs team has now updated and clarified much of this information, and added links to our ever-expanding FAQ. (Hint: Tick the "Turn the new user help banner back on." option in your Preferences to access this content.)
  • [AO3-1654] - Deleting comments in a long thread could render undisplayed comments inaccessible. Now, you can properly access the rest of the thread.
  • [AO3-4663] - We added a meta tag to our layout which forces Internet Explorer to display pages in EdgeHTML mode, the highest standards mode supported by IE.
  • [AO3-4700] - We fixed a problem with the status badges in our README and switched the image links to a new service which provides a crisper look.

Automated Tests

  • [AO3-4684] - We use a little tool that tells us if our code is sufficiently covered by test cases. This release updates the necessary gems to improve the tool's accuracy.
  • [AO3-4677] - We also added coverage monitoring to the service we use for deploying new code to our Test Archive.
  • [AO3-4695] - Increased our fandoms-related test coverage.
  • [AO3-4694] - Increased our invitations-related test coverage.
  • [AO3-4690] - Increased our tags-related test coverage.
  • [AO3-4675] - Increased test coverage for our internal API.
  • [AO3-4673] - Increased test coverage for skins-related activities.
  • [AO3-4678] - 99 lines of tests on the wall, 99 lines of tests! Take one away -- actually, add 99 lines, which in this case cover tag wrangling procedures -- 15,289,462,899 lines of tests on the wall!
  • [AO3-4688] - In a continuing theme, we increased our gift exchange test coverage.
  • [AO3-4680] - Ditto, for AO3 admin activities.
  • [AO3-4670] - And even more admin activities.
  • [AO3-4679] - This one's for test cases relating to the invitation queue.
  • [AO3-4672] - AO3 admins can add languages to the Archive database, which will then appear in the language drop-down when posting a new work, for example. We added a test for this!
  • [AO3-4671] - There's now also a test for deleting or orphaning multiple works at once. "How are they not at 120% test coverage at this point???" I hear you ask. But apparently we are not.

Maintenance

  • [AO3-4646] - Updated the gem we use for parsing HTML in user-entered text.
  • [AO3-4697] - There were a lot of files that included old database tasks we weren't using anymore. Got rid of those! \o/
  • [AO3-4674] - We also cleaned up instances of devmode code that wasn't used anymore.
  • [AO3-4662] - Same for some outdated API code.
  • [AO3-4653] - Added some code to reduce the number of errors logged when tags are changed.
  • [AO3-4643] - This fix removes spurious errors logged when a subscription is deleted before the batch containing its notification is sent.
  • [AO3-4660] - This one is aimed at reducing errors we saw when works weren't being properly re-indexed.
  • [AO3-4645] - Sometimes, notifications weren't sent when works were added to a collection (due to a miscommunication between database records and mailers). We added code to address these errors.

Known Issues

See our Known Issues page for current issues.

Comment

Post Header

Published:
2016-10-09 17:41:43 -0400
Tags:

This release includes several bug fixes concerning gift exchanges, the usual handful of miscellaneous improvements, and a much improved challenge matching process!

We have drastically sped up gift exchange matching by reducing the number of database queries involved in the process. Through the magic of hash mapping, caching, batching, indexing, and pre-processing, we've made matching at least five to ten times faster, depending on your challenge settings -- and we've eliminated the recently-implemented constraints that were causing difficulties for challenges that relied on hand-matching. Note that you won't notice any difference when putting your challenge together -- all these changes only affect back-end processes.

We think that all gift exchanges will benefit from the new code, but some challenges will see especially noticeable improvements. This includes single-fandom exchanges as well as fanwork fests that let participants offer and request fic, art, podfic, etc. through Additional Tags.

(Shoutout to tickinginstant for not only making these changes, but for doing it as a drive-by contributor through our GitHub presence. Many, many thanks! ♥)

Credits

  • Coders: james, Naomi, Sarken, tickinginstant
  • Code reviewers: Ariana, james, Naomi, Sarken
  • Testers: Lady Oscar, Naomi, Sarken

Details

Challenges

  • [AO3-4635] - We vastly improved the way challenge matches are calculated, which should ensure a much smoother experience for gift exchange mods and participants. Additionally, we now have much better automated test coverage for this feature.
  • [AO3-4505] - In the challenge settings, gift exchange mods can set a message to be sent to all participants with their assignment. Previously, line breaks in that message would not be preserved in the emails. Now they are!
  • [AO3-4652] - When a challenge assignment didn't include a rating -- either because rating wasn't an option on the sign-up form or because the recipient had not chosen a rating -- assignment emails included a line saying "Rating: Choose Not To Use Archive Warnings." This managed to be both inaccurate and unnecessary, so we removed it. Now ratings will only appear in assignment emails if your recipient has specified a rating.
  • [AO3-4654] - The assignment emails weren't properly listing all tag types (Rating, Warning, Relationship, etc.) that had been set to "Any" in the matched participant's sign-up. Fixed!
  • [AO3-4656] - In further assignment email bugs, a link to the user's Assignments page was mislabeled as "your archive dashboard"; this is now properly labeled.
  • [AO3-4657] - Challenge assignment emails included an ugly "Sent at sent_at" mishap in the footer. Now the line displays the actual time the message was sent.
  • [AO3-4655] - The "Optional Tags:" line in challenge sign-up blurbs was rather misaligned and has been nudged into its proper position now.

Misc.

  • [AO3-4664] - We fixed a security issue regarding pseuds that could occur when commenting, bookmarking, signing up for a challenge, posting a chapter, or nominating a tag.
  • [AO3-4343] - The automated response to Support form submissions also included the "Sent at sent_at" line in the footer. Not anymore! In fact, it's been fixed for all emails where this problem occurred. \o/
  • [AO3-4616] - One of our automated tests would sometimes fail for no discernible reason. A reason has been found and now it shouldn't fail anymore. (Rule #1: It's always caching. Rule #2: It's always caching.)
  • [AO3-4651] - We limit the number of abuse reports about any given work on the Archive, as even one message will make sure the Abuse team investigates the case. This feature came loose in our last deploy, however. Now it's working again!

Known Issues

See our Known Issues page for current issues.

Comment

Post Header

Published:
2016-09-24 19:29:41 -0400
Tags:

In this release, we are introducing changes to the abuse report form and fixing a couple of issues with subscription emails for anonymous works. Also included: some invisible code improvements and better documentation for developers wishing to submit bug fixes.

Please note that as of this release, email addresses are required when submitting an abuse report. You can read more about the reasons for this in our post about a clarification in the Terms of Service. Please help the Abuse team help you!

Credits

  • Coders: Ariana, dolleye, james, Sarken, Scott, tickinginstant
  • Code reviewers: james, Naomi, Priscilla, Sarken, Scott
  • Testers: Alison, Lady Oscar, Matty, mumble, Sammie, Sarken

Details

Abuse Reports

  • [AO3-4607] - The Abuse team started using a new ticket tracker, so we did the necessary rewiring on our end, while also making some changes to the form itself. An email address is now mandatory (for the sole reason of having a way to contact you if the Abuse team needs further information).
  • [AO3-4608] - Since we are able to provide assistance in languages other than English (thanks to our amazing Translation volunteers), we have made this option more obvious with a pull-down menu to select your language. Site admins can manage the list of available languages as new Translation teams sign up.

Collections

  • [AO3-4108] - If a work was in two anonymous collections, a notification would be sent to users subscribed to the creator when only one collection was revealed, not both. This would break anonymity. Fixed now!
  • [AO3-4367] - However, when works were in an unrevealed-but-not-anonymous collection, creator subscribers weren't notified at all when the works were revealed. Also bad! Also fixed.
  • [AO3-4273] - When using a non-canonical tag in a gift exchange sign-up, an error message would advise the participant to contact our Support team. As per updated policy, we ask participants to instead contact the challenge moderator(s), who can create a tag set for the exchange if necessary.

Behind the Scenes

  • [AO3-4397] - We made some subtle code changes that should reduce the load on our database server.
  • [AO3-4398] - More TLC for the database server.
  • [AO3-4619] - Over on our project's GitHub page, we updated our README and added some formal contributing guidelines as well as a pull request template for those wishing to submit a bug fix (yes please!).
  • [AO3-4637] - We fixed a rather serious security issue, with many thanks to Harlan Lieberman-Berg for alerting us to the problem!
  • [AO3-4639] - After taking care of the above security issue, indexing for anything other than works wasn't working properly anymore. That's also fixed now!
  • [AO3-4640] - The automated tests for prompt memes were failing since our hypothetical "sign-ups close at" date was no longer in the future. Damn that passage of time. Anyway, we are no longer using a hardcoded date.

Known Issues

See our Known Issues page for current issues.

Comment

Post Header

Published:
2016-09-04 05:14:22 -0400
Tags:

We have whitelisted two new sites for vid embedding purposes (and removed a couple of others), made sure external services don't get stuck on the adult content warning when they're trying to reach a work, prettied things up a bit here and there, and squashed a handful of miscellaneous bugs.

Credits

  • Coders: Ariana, dolleye, james, Sarken, tickinginstant
  • Code reviewers: james, Naomi, Priscilla, Sarken, Scott
  • Testers: Alison, Lady Oscar, mumble

Details

Misc.

  • [AO3-4533] - Once upon a time, the Organization for Transformative Works website was somewhat unstable, so we had to temporarily host a donation page on the Archive. The OTW site is now much more reliable, so we've removed the temporary page and updated our Donate page with the new link and a reassurance that we will never link your financial information to your AO3 name.
  • [AO3-4516] - Most websites these days use the HTTPS protocol to make sure any communication they have with users' computers is secure. In order to switch the Archive to HTTPS, we have begun updating our code so our links no longer use absolute URLs like http://archiveofourown.org/works, but rather relative URLs like /works.
  • [AO3-3496] - It used to take so long for a work to be added to or removed from your Marked for Later list that it was easy to think it hadn't worked and you needed to click the button again. Unfortunately, that would just undo whatever action you originally intended to do. Now your Marked for Later list will be updated immediately, eliminating any confusion and just making things more convenient.
  • [AO3-4547] - Previously, even small updates to our notification banners (used to inform users about site-wide issues, or during OTW fundraising drives) would make the banner pop up again even if a logged-in user had already dismissed it. We have now added an option for admins to prevent this from happening.
  • [AO3-4585] - In very rare cases, trying to create a new account would bring up an 404 error page. We have put in a fix that will hopefully put an end to this.
  • [AO3-4597] - When a page on the Archive has many button-style links in a row, the buttons can sometimes wrap onto multiple lines (e.g. on narrow screens). Previously, there was no white space separating one row of links from the other, which looked bad and made the buttons harder to select on touch screens. This has been fixed!
  • [AO3-4628] - An encoding error was preventing Open Doors from importing works that had certain characters (like curly quotes) in metadata fields. This has been fixed!
  • [AO3-4564] - Our Ruby version has been upgraded from 2.1.9 to 2.2.5! Baby steps.
  • [AO3-4624] - We made a small update to our Rails install.
  • [AO3-4631] - When a bot tried to access a work with an R or E rating (or no rating), it was served the adult content warning rather than the work. That was annoying for sites like Pinboard and the Internet Archive, so now we're letting bots bypass the warning page.

Emails

  • [AO3-4420] - We've been working with the Translation committee to test some code for translating AO3 emails, and they found a problem with the way we coded plurals in kudos emails. We've fixed it now, so experimentation can resume!
  • [AO3-3947] - Even after setting the preference to turn off emails about gift works, users would still get those emails. Now they won't.
  • [AO3-4615] - A naked URL in the HTML version of our sign-up confirmation email was messing with the email's layout. We have now dressed up the link in the proper HTML.

Embeds

  • [AO3-4627] - We added Vidder Tube to our list of whitelisted domains, so you can embed vids into AO3 works.
  • [AO3-4335] - Same for the Internet Archive.
  • [AO3-4626] - Both Blip.tv and Viddler are now-defunct sites and have been removed from the whitelist.

Known Issues

See our Known Issues page for current issues.

Comment

Post Header

Published:
2016-08-10 16:43:11 -0400
Tags:

Our last 14 deploys contained a lot of behind-the-scenes work, including improvements to the tools our wonderful Open Doors, Abuse, and Tag Wrangling committees use. We also squashed some annoying bugs concerning challenges, chapter counts, and the font on work summaries.

Credits

  • Coders: Ariana, CJ Record, Elz, james, Naomi, Sarken
  • Code reviewers: Elz, Enigel, james, Naomi, Sarken, Scott
  • Testers: james, Lady Oscar, Matty

Details

Challenges

  • [AO3-4576] - When a challenge's potential match and assignment generation went on for a long time, the process would sometimes fail due to a lost database connection and then restart endlessly, requiring a database administrator to come to the rescue. We've fixed the cause of this and sped up match generation at the same time!
  • [AO3-4577] - The list of givers without recipients wouldn't load for large challenges due to the way we were alphabetizing the list. We've removed the alphabetization to make sure the page will load.
  • [AO3-4128] - If a challenge had more than 1000 sign-ups, the progress page for the matching process would start giving the moderator an error after the first 1000 sign-ups. Now it will work even after the 1000th sign-up is matched!

Servers, Databases, and Automated Tests

  • [AO3-4589] - We use static files called cassettes to speed up our automated tests for our work importing code. The tests started to fail because the cassettes were very old, so we updated the cassettes.
  • [AO3-4575] - When a task takes a very long time to complete, the database connection sometimes gets closed and the task stops running. Now we retry the task when we reopen the connection.
  • [AO3-4596] - We updated our deploy script to reflect the fact we took two of our old application servers out of service in order to provide power for two new database servers.
  • [AO3-4598] - We put one of our old database servers back to work as an application server.
  • [AO3-4601] - We reinstalled another of our old database servers as a unicorn worker.
  • [AO3-4611] - We added two new virtual machines: one to help the machine that currently handles downloads, and another to help the machine currently handling bots. (And all four of these are running our new operating system, too!)
  • [AO3-4612] - Another old server put back to work! This time, we turned an old application server into one that handles Resque workers for background tasks like tag wrangling and challenge matching.

Committee Tools

  • [AO3-3597] - Abuse sometimes receives reports of works that are written in one language but labeled as another. Abuse staff can now label the work with the correct language by themselves rather than waiting for a coder or sysadmin with database access.
  • [AO3-4588] - All tag wranglers had access to a method of editing tags that has the potential to overload the servers if used incorrectly. To ensure that no servers are overloaded, we've restricted access to this tool to tag wranglers with administrator access.
  • [AO3-4359] - The mass import tool used by Open Doors only handled works hosted on the sites they rescue. However, some of those sites include works which are only links to external sites. In order to preserve the collections as they are, we added the ability for Open Doors to import those works to AO3 as bookmarks.

Miscellaneous

  • [AO3-4593] - On the work posting form, the Rich Text and HTML buttons are supposed to use styling to indicate which editor is active. However, they weren't doing what they were supposed to, so we fixed that. (Obligatory reminder to please avoid composing your works in the posting form!)
  • [AO3-4578] - When a user tried to edit the pseud matching their user name, the page informed them that they could not change their "fallback pseud." It wasn't entirely clear what "fallback pseud" meant (it means "the pseud that matches your username"), so we changed the message to something more informative.
  • [AO3-4573] - Due to problems with spam last year, we turned off the ability for existing users to request invitations. It's unfortunately been off for almost a year, so the error message saying, "Sorry, new invitations are temporarily unavailable" felt a little misleading. We adjusted the wording and updated the links in the message as well.
  • [AO3-4554] - We updated some transformativeworks.org links in our Terms of Service and Terms of Service FAQ to point to the pages' new URLs.
  • [AO3-4514] - If a creator posted their work using the "Post Draft" button on their drafts page, the posted work would display a chapter count of 0/1. Now the work will show the correct chapter count.
  • [AO3-4567] - When we updated our version of Ruby, it pointed out two code errors that our previous version did not. We fixed those errors.
  • [AO3-4614] - In some browsers on some Android devices, users were seeing work summaries and a whole bunch of other text in a very light grey, which made it hard to read. It turned out that some recent Android updates were revealing a four-year-old mistake in the Archive's CSS. We corrected that mistake, and now the text should be legible once again.

Gems

  • [AO3-4566] - There were a few gems we needed to update before we could upgrade our version of Ruby, so we updated them.
  • [AO3-4430] - In our quest to update all of our gems, we found a gem we weren't using. We've removed it so we don't waste any time maintaining it from now on.
  • [AO3-4574] - We updated the gems for a number of things in one go: reordering things like chapters, encrypting passwords, parsing skins' CSS, entering dates for challenges, uploading user icons, and a few more behind-the-scenes things.
  • [AO3-4446] - We've polished up the gem for the unicorns that run the Archive. (That is, we updated the gem for our web server.)

Known Issues

See our Known Issues page for current issues.

Comment

Post Header

Published:
2016-06-15 23:10:56 -0400
Tags:

Over the last eleven releases, we've tackled nearly forty issues ranging from performance improvements to infrastructure upgrades to new features -- not to mention more than a few minor bug fixes and enhancements.

Credits

  • Coders: Ariana, Cesy, james, jkingsman, Lin, Naomi, Sarken, Scott
  • Code reviewers: Ariana, Cesy, Enigel, james, Naomi, Sarken, Scott
  • Testers: CJ Record, Lady Oscar, Sammie, Sarken

Details

Features

  • [AO3-4536] - Guests would sometimes enter the wrong email address when leaving comments, and the rightful owner of that email address would ask us to make sure no one was able to use their email address on the Archive again. Now our site administrators can actually do that.
  • [AO3-2665] - We've implemented the changes announced in our post, "Maintainers Can Invite Works to Collections!" Surprisingly, these changes allow collection maintainers to invite works to their collections.

The Support Form

  • [AO3-4532] - Our Support team switched ticket tracking services, so we updated the form to work with the new service. This change includes removing the "Category" field, which wasn't particularly useful, and adding new fields for "Your name" and "Language," which will make it easier for Support to know how to address users and in what language to respond.
  • [AO3-2909] - There was some HTML showing in the subject line of all the emails our Support form sends to the Support team. This was ugly and made things harder to read, so we fixed it.
  • [AO3-4534] - The OTW website recently got a major overhaul (check it out -- the Webs team did great work!) that included moving AO3's back-up Support form. That meant the link on our main Support form no longer pointed to the right place, so we updated the link.
  • [AO3-4557] - We rewrote some of the text on our Support page to be a little less wordy.
  • [AO3-4569] - When we made changes to the Support form, Abuse reports stopped getting submitted to Abuse's ticket tracker. We fixed that ASAP, so the Abuse chair would no longer need to enter all the reports into the tracker manually.
  • [AO3-4570] - The new language field on the Support form was defaulting to Bahasa Indonesia, which is a lovely language, but not the one we meant to use. It now defaults to the site's default language, which is currently English.
  • [AO3-4568] - We removed some instructions from the Support form that were no longer necessary given the addition of a language option.

News Posts

  • [AO3-4535] - Translations used to be listed at the top of news posts with each language and news post title on a separate line. This was fine when we only had a few translations for each news post, but our awesome Translation team is huge now, and we sometimes have ten, fifteen, or even twenty translations for a post! We've switched to a comma-separated list of languages instead, which will take up much less room. We also moved the tags from the bottom of news posts to the top.
  • [AO3-4538] - Our news posts occasionally contained wide images that made the page scroll horizontally or display awkwardly on narrow screens. Now these images will shrink on small screens but continue to display at their actual size on large screens.
  • [AO3-4123] - To make sure news post translations were listed in alphabetical order by language, our Translation team used to have to post the translations in alphabetical order. We've helped them out a bit by automatically alphabetizing the list according to the languages' standard two-letter abbreviation.
  • [AO3-4522] - On the homepage, we have "Read more..." links for each news post. Having multiple links with the same text can be confusing for people who use a screenreader, so we clarified the text that screenreaders use.

Caching and Performance

  • [AO3-4512] - To improve performance, we've started caching the list of tags associated with each work.
  • [AO3-4510] - Some overenthusiastic caching meant the icon on a user's old comments wouldn't update when the user changed their icon. We've tempered the cache's enthusiasm somewhat and now the icons will eventually update.
  • [AO3-4230] - When a tag wrangler changed the capitalization, diacritics, or suffix of a tag, the tag on the work blurbs didn't always update. We've fixed the caching issue that caused this.
  • [AO3-4495] - We've started caching the number of bookmarks a work has to give the site a little performance boost.
  • [AO3-4401] - We were adding a lot of works to users' history pages at one time, and it was pushing the limits of our database. Now we add fewer works at a time to make the database happier.
  • [AO3-4581] - We've started caching the total number of unwrangled fandom, character, relationship, freeform, and unsorted tags on the Archive in order to improve the performance of various tag wrangling pages.

Upgrades

  • [AO3-4365] - We have joined the modern era and switched our doctype from XHTML to HTML5.
  • [AO3-4542] - Two of our gem updates from a previous release began causing an issue that prevented works and bookmark listings from updating, so we removed those changes for the time being.
  • [AO3-4543] - We upgraded the gem we use to communicate with internal services like Elasticsearch, which powers our searching and filtering code.
  • [AO3-4555] - We updated the software that allows our Translation team to work on the Archive.
  • [AO3-4427] - We upgraded the gem that controls our database.
  • [AO3-4563] - We upgraded our version of Ruby to 2.1.9.

Deploys and Automated Tests

  • [AO3-4545] - Whenever we deployed new code for testing, our test site would run around naked until a database administrator wrangled it back into its skin. We've corrected this behavior and our testing process now involves 100% less nudity.
  • [AO3-4527] - The continuous integration service that runs our automated tests was set up to send emails to our main coding discussion list. It was a lot of emails, so we switched it over to a secondary mailing list where it won't drown out our discussions.
  • [AO3-4450] - We added more automated tests for pseuds.
  • [AO3-4386] - We added automated tests for part of our tag set code.
  • [AO3-4528] - We had a brief scare in which we thought we found a code bug with the bylines of works imported by Open Doors archivists, but it turned out to be a caching issue. Still, we added automated tests to make sure we don't end up with a code bug there in the future.

Miscellaneous Bug Fixes

  • [AO3-4491] - When we deployed responsive layout changes earlier this year, the layout was somewhat lacking in margins. We hurriedly threw some tiny margins in to make up for the oversight, and now we've made them a little bigger and more consistent throughout the site.
  • [AO3-4525] - There was a little "-" loitering in the upper left of work pages. We didn't want it there, so we sent it on its way.
  • [AO3-4580] - Inviting a work to an anonymous or unrevealed collection would immediately make the work anonymous or unrevealed, hiding either the creator's name or the entire work from other users. Now the work won't be made anonymous or unrevealed unless the creator accepts the collection invitation.
  • [AO3-4500] - Sometimes works imported by Open Doors would be missing the creator's name, and this would break any RSS feeds that included the work. We've fixed the problem with the feeds, although we still need to track down why the creator name is sometimes missing.
  • [AO3-4523] - Fandom lists on users' dashboard pages were always showing both the "Expand Fandoms List" and "Collapse Fandoms List" links. We've fixed it so it only shows the relevant option.
  • [AO3-4561] - Our DMCA Policy page had links pointing to chillingeffects.org. The links now point to the pages' new locations on lumendatabase.org.
  • [AO3-4587] - When a work you've bookmarked is deleted by its creator, it leaves behind your bookmark notes and a little message saying the work has been deleted. Trying to edit or delete this sad shell of a bookmark resulted in a 404 error, but we've fixed that now.

Edited 23:41 UTC June 16, 2016: We also fixed AO3-4591, wherein a user could not delete their AO3 account if they had a bookmark of a work that had been deleted.

Known Issues

See our Known Issues page for current issues.

Comment


Pages Navigation