AO3 News

Post Header

2014-12-31 10:03:14 -0500


  • Coders: Ariana, Daniel Erenrich, Enigel, james_, Marie Markwell, Sarken
  • Code reviewers: Ariana, Elz, james_, Scott
  • Testers: Erialeduab, hele, Lady Oscar, mugenmine, mumble


Works & Stats

  • We have updated the text of the emails that go out (to existing AO3 users as well as creators who don't have an account yet) when an archive mod or site owner imports someone's work through our Open Doors project. (See what the team has accomplished this year in our News posts about Open Doors!)
  • On the Statistics page, reversing the sort order for Date, Kudos, Comment Threads, Hits etc. would not update the corresponding graph title. It now properly says "Oldest" or "Bottom Five By [Kudos/Comment Threads/Hits etc.]" when displaying the reverse sort results.
  • Drafts of a related work, e.g. fanart for another user's fic, were showing up in the author's sidebar, e.g. Related Works (1), even though the work draft was still invisible to anyone but the artist. Now the number in the sidebar only increments when the work has been posted.
  • The code responsible for deleting drafts one month after their creation was not working properly in some cases, resulting in the drafts still being listed on the user's draft page despite being deleted/inaccessible. It should be working properly now.
  • The big chunk of code responsible for handling works and work-related actions had become unwieldy and messy over time. It has now been refactored--cleaned up and reorganized--to adhere to best practices.

Collections & Challenges

  • When changing the settings for a challenge (Moderated, Closed, Unrevealed, Anonymous), the challenge blurb, e.g. on the main Collections index, would not be updated to reflect the change. This has been fixed!
  • If you posted a work to fulfill a challenge assignment and your recipient deleted their account, you would then be unable to edit your work (getting an error 500 instead of the editing form). This has been fixed!
  • In tag sets, the option for adding a chunk of relationship tags at once ("batch loading") wasn't working. Now it is.


  • Our tag cloud was displaying only a few very popular tags in large font size, with all the other tags being more or less the same size. It now calculates tag counts and display size differently, making the cloud more useful and easier to parse.
  • When selecting a tag from the dropdown menu to browse the AO3 News, but leaving the language selection blank, trying to get to the next page of results would lead to an Error 500. This was because the code expected a language selection - we now explicitly set the default language to English, so this error won't happen anymore.
  • In preparation for further work on a translatable interface for the Archive, we removed all lingering code related to a previous translation project.
  • Switched our Rails memcached client to Dalli, which is better maintained and should make pages load slightly faster.

Known Issues

See our Known Issues page for current issues.