AO3 News

Releases 0.9.70 - 0.9.78: Change Log

Post Header

Published:
2015-09-13 23:38:22 UTC
Tags:

Despite the summer vacation and three staffers moving house, we still found time to deploy some improvements to our documentation and automated tests, and provide useful tools for other busy Archive teams.

Credits

  • Coders: Ariana, Elz, james_, Lal, Sarken, Scott
  • Code reviewers: Ariana, Elz, james_, Sarken, Scott
  • Testers: Elz, james_, Lady Oscar, Sam Johnsson, Sarken, Scott

Details

Support and Issue Tracking

  • We are now able to record a history of changes made to user accounts to help with Support issues around account activation.
  • The tone of the automated response to Support requests was both overly casual and inappropriate for responding to users writing in to express dissatisfaction. It has been changed to something more formal and appropriate.
  • We recently switched our issue tracker from Google Code to JIRA, and we have updated the link on both our GitHub README and the Support form.
  • Our Support form has been updated to reflect the fact we now offer support in Tiếng Việt.
  • We've updated some comments in our automated tests to refer to issues on JIRA rather than Google Code.

Misc.

  • We've added a new admin tool to make it easier for our Abuse team to keep track of Fannish Next of Kin arrangements.
  • It was previously very easy to provide a phony IP address when leaving a comment. We've changed the way IP addresses are recorded to prevent that.
  • We've added more servers to help with wrangling and processing emails.
  • We have made it easier to deploy code when the servers are busy, and improved the configuration of the development environments for our volunteers.
  • If you signed up for a prompt meme challenge and the moderator edited the settings to stop allowing a certain field (e.g. Warnings), you wouldn't be able to edit your sign-up. It is no longer possible for challenge moderators to change the allowed fields once sign-ups exist.
  • Fixed a bug whereby works on external sites whose urls ended with similar numbers (e.g. "foo/123" and "foo/1234") could not all be imported because the importer would find the longer URL when searching for the short one and refuse to import it.

Known Issues

See our Known Issues page for current issues.