AO3 News

Releases 0.9.92 - 0.9.100: Change Log

Published: 2016-01-02 04:54:14 -0500

The first release notes of 2016 collect all the little improvements and fixes we added to the Archive in December of 2015. This includes a much needed upgrade of our Rich Text Editor, several invisible performance improvements, and the ability to refuse gifts.

2015 was a busy year full of fixes and features, and we'd like to thank all of our coders and testers, but especially first-time coders Nerine and l1n and first-time testers madelyn, torigates, truffulafruits, Claire B, Debris, Nerine, and Phoenixacid!

Credits

  • Coders: Ariana, Cesy, Elz, james_, l1n, Naomi, Sarken, Scott
  • Code reviewers: Ariana, Cesy, Elz, Enigel, james_, Naomi, Scott
  • Testers: james_, Lady Oscar, Matty, Michelle D, mugenmine, mumble, Sarken

Details

Works & Comments

  • [AO3-3145] - We've added the ability to refuse gift works. All work blurbs on your Gifts page now feature a "Refuse Gift" button; refused gifts will be collected on their own "Refused Gifts" page (visible only to you) in case you ever want to revisit your decision. When you refuse a gift work, the automated "For [user]" line in the work's Notes section will vanish. The thwarted gift giver will NOT be notified.
  • [AO3-4330] - When a spammer posted a lot of spam works to the Archive, the Abuse team used to have to delete each work individually after banning the spammer. Now they can delete all the works at once during the banning process.
  • [AO3-4383] - Mass imports of external archives would run into issues with some older code that parses incoming work content. This was solved by explicitly prioritizing content sent through the API used by Open Doors.
  • [AO3-4050] - We were running a very old version of our Rich Text Editor of choice, TinyMCE, and have finally joined the rest of the Internet in 2016 by upgrading to version 4.3.2. \o/ Among many other things, this takes care of the bug where single-word paragraphs would quietly get eaten. It also preserves simple formatting (such as bold and italics) when copy/pasting from Google Drive.
  • [AO3-4395] - The TinyMCE update also removed the "horizontal rule" button, oops. We've put it back now.
  • [AO3-4379] - The message that displays on the comment form for moderated works had a typo and said, "Your comment will not appear until it has been by approved by the creator." The extra "by" has now gone bye-bye.

Challenges & Tags

  • [AO3-4358] - If a challenge collection was moderated, the link to the sign-up form would not be included in its dashboard sidebar despite appearing elsewhere on the page. Now challenge sidebars will include the Sign-up Form link for Gift Exchanges and the Prompt Form link for prompt memes regardless of moderation settings.
  • [AO3-4382] - If a tag set had more than 20 additional (freeform) tags, the list of those tags wouldn't appear on the tag set. We added the missing = that caused the problem, and now the tags appear!

Users & Accounts

  • [AO3-3720] - If you changed your AO3 user name and someone wanted to give you a gift, the autocomplete wouldn't suggest your new name -- only your old one. Now when you change your user name, your old name is removed from the autocomplete and your new one is added.
  • [AO3-4321] - The change password page would incorrectly state that you logged in with a temporary password in the event you requested but didn't use a temporary password. Now the message only displays when you are redirected to the change password page after logging in with a temporary password.
  • [AO3-4374] - The page that you are taken to after creating an AO3 account wrote out a URL where it could have used a link and failed to capitalize the word "Archive." We've fixed both of those issues and spruced up the page margins and spacing between paragraphs as well.

Under the Hood

  • [AO3-4380] - Some slow code meant that users with extremely large inboxes were unable to access their dashboard or their inbox. We now use a single, faster query that will make these users' dashboards and inboxes accessible again.
  • [AO3-4392] - We started work on improving database performance and added a tool that points out queries in need of optimizing
  • [AO3-4362] - The byline generated for every work -- creator(s) by pseud or "Anonymous", as appropriate -- involved way too many database requests, especially for pages listing several works. To kill our servers a little less, we are now properly caching the bylines.
  • [AO3-4269] - Several of our automated tests would sometimes fail without a clear reason, making them somewhat less useful than we'd like. We've done some work toward fixing that. (See also: AO3-4402)
  • [AO3-4403] - New developers forking our code on GitHub couldn't connect their repositories to the service we use for running our automated tests. That's all fixed now.

Known Issues

See our Known Issues page for current issues.

Comment

The big news this time around is comment moderation. Many thanks to the users who helped us trial this feature, and to the Abuse team for their input! In addition, we have done some work on our automated testing infrastructure and made some corrections and improvements to our documentation.

A big round of applause and thanks to the Systems team for their hard work debugging and resolving the hardware-related downtime earlier this month!

Credits

  • Coders: Ariana, Elz, Naomi (shalott), Nerine, Sarken
  • Code reviewers: Ariana, Elz, Enigel, james, Naomi, Scott, Sarken
  • Testers: Lady Oscar, mumble, Sarken, madelyn, torigates, truffulafruits

Details

  • [AO3-3543] - Comment moderation is here! Please read the details below for updates to our previous post, Comment moderation is coming, including some additions we made after testing and user input.
  • [AO3-4364] - A handful of the tests in our automated test suite fail intermittently due to timing issues. We have disabled caching on these tests to reduce the frequency of failures.
  • [AO3-4320] - Added a link to the more detailed Tags FAQ to the tags help files.
  • [AO3-4141] - Updated the Edit Pseud form to link to the help file with the correct set of available HTML tags.
  • [AO3-4034] - In the Diversity Statement, we were "the archive" instead of "the Archive" when referring specifically to the AO3. Now we have a capital A! \o/
  • [AO3-4373] - A new database column (to track if a work has comment moderation enabled or not) temporarily broke search indexing, whoops! Fixed.

More Detail on Comment Moderation

Turning Comment Moderation On or Off

Comment moderation can be turned on and off at the per-work level. You can set it for a new work or edit an existing work to turn it on or off in the privacy settings.

Privacy options when posting or editing a work: only show to registered users, disable anonymous commenting, enable comment moderation

You can also turn it on or off for multiple works at once using the "Edit Works" tool from your dashboard or works page.

Privacy options when editing multiple works at once: anonymous commenting, comment moderation

Approving Comments

When you have comment moderation turned on, you will have to approve all the comments before they are posted publicly. You can review comments on a work by checking its "Unreviewed Comments" page:

Row of buttons at the top of a work, including the link to access all unreviewed comments on the work

Page showing all unreviewed comments on a work, to be approved, deleted, or marked as commercial spam

You will also be able to approve comments from all your works from your inbox (assuming that you have JavaScript enabled and have not turned off your inbox.)

Unreviewed comment on the user's inbox page

You will not be able to reply to a comment until it is approved.

You cannot "un-approve" a comment, but as before, you can still delete it.

Posting Comments

When you leave a comment on a work with moderated comments, there will be a note about the moderation before and after you post.

If you are a logged-in user, you will be able to edit or delete your comment after you post it, but your comment will not be linked from the work. If you want to be able to find it again, you can either bookmark your comment or turn on the preference to receive email copies of your own comments.

If you edit your comment after it is approved, it will go back into moderation (unless the edit is very small, like fixing a typo).

If you reply to someone else's comment, they will be notified of your reply when your reply is approved.

If You Need To Report a Comment

If you receive a comment that you want to report to the Abuse team, you can use the abuse report form and include a link to your list of unreviewed comments (which can be accessed by Abuse personnel), or to the work or comment in question. Since comments can be edited if they were left by a logged-in user, we recommend taking a screenshot (which you can send as an email attachment once the Abuse team responds to your report) or holding on to the comment notification you received.

Known Issues

See our Known Issues page for current issues.

Comment

Releases 0.9.79 - 0.9.86: Change Log

Published: 2015-10-28 17:53:46 -0400

Over the last month and a half, we've released several small batches of code fixes, including some improvements to help catch and ban spammers. Huge shout-out to the Abuse team for all their hard work - you are all heroes!

Credits

  • Coders: Elz, james_, Nerine, Sarken, Scott
  • Code reviewers: Ariana, bingeling, Elz, Sarken
  • Testers: Lady Oscar, mumble, Sarken, Scott

Details

Admin

  • [AO3-4263] - Site admins, e.g. Abuse personnel, can delete references to external works (created by bookmarking non-Archive URLs); however, they couldn't do so from the main list of external works. Now they can.
  • [AO3-4264] - We cleaned up the menu of buttons that site admins can use to edit external work bookmarks.
  • [AO3-4265] - When admins hid a bookmark, they got an error 500 (even though the bookmark was successfully hidden). They now receive a more helpful message.
  • [AO3-4287] - The option for deleting news posts wasn't where our admins expected it to be, so we added a Delete button to the posts themselves and to the post editing form.

Collections

  • [AO3-4338] - Trying to edit an existing bookmark to add it to a non-existent collection now gives an informative error message rather than Error 500.
  • [AO3-4344] - Suspended/banned accounts can no longer create collections.
  • [AO3-4347] - There was an Uncategorized Fandoms option in the fandoms menu for collections, but collections do not have Uncategorized Fandoms pages. We removed the menu option.

Skins

  • [AO3-2439] - The < and > signs were getting stripped out of skins, making it impossible to use immediate child declarations in one's CSS. It is now possible!
  • [AO3-4340] - Add the ability to use the shape value for clip or x or y rotate values for transform when making skins.
  • [AO3-4345] - In the skin Reversi, the explanatory line "You may have mistyped the address or the page may have been deleted." on the Error 404 page had minimal contrast, making it hard to read. This has been fixed.

Infrastructure

  • [AO3-4329] - Now the number of memcached servers we use can be configured dynamically.
  • [AO3-4348] - We no longer use Coveralls to identify gaps in test coverage.
  • [AO3-4351] - We made a number of changes to the way we deploy code to the Archive.
  • [AO3-4352] - Due to a hardware problem, we have temporarily removed ao3-front02 from the pool of servers that run the Archive. We also updated our deploy script to reflect the fact that we temporarily removed one of our servers.

Misc.

  • [AO3-4292] - The advanced Works Search had very strong opinions about how date searches should be capitalized, and wouldn't return the correct results if you dared to search for 2 Weeks or 2 WEEKS instead of the lowercase 2 weeks. We fixed it so now you can even search for 2 wEeKs if the mood strikes.
  • [AO3-4322] - We were trying to close an <h3> HTML tag with an </h4> tag on works pages. That didn't work very well, so we changed it to </h3>.
  • [AO3-4337] - Updated the link on the Tag Wrangling Tools page to reflect the fact that we switched from Google Code to JIRA as our issue tracker.
  • [AO3-4360] - Even though the logged-in homepage doesn't show how many fandoms, users, or works the Archive has, we were still running the database query to count those items. This made the servers sad, so we stopped doing it.
  • [AO3-4363] - We fixed a potential security issue which could have opened user accounts to malicious phishing attempts.

Known Issues

See our Known Issues page for current issues.

Comment

Releases 0.9.70 - 0.9.78: Change Log

Published: 2015-09-13 19:38:22 -0400

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.

Comment

Releases 0.9.65 - 0.9.69: Change Log

Published: 2015-07-19 23:10:04 -0400

We've returned some formatting to kudos emails, cleaned up the language menu for news posts, and added some HTML classes for use in Archive skins.

Credits

  • Coders: Ariana, james_, Sarken, Scott
  • Code reviewers: Ariana, Enigel, james_, Sarken, Scott
  • Testers: Ariana, Lady Oscar, Sarken

Details

  • The language filter for AO3 News posts used to list all languages available on the Archive. It will now only include languages for which we have a locale set up, which will usually correspond to languages with news posts.
  • The kudos email lost some of its text styling when we prepared it for translation. User names will now be bold and red again, and work titles will be bold and italic.
  • We cleaned up the files that control the text of the kudos email.
  • There were some automated tests that weren't being run because they weren't working properly. They have been fixed and are now being run.
  • We've begun using a Ruby gem that will reduce the number of deadlocks in our database.
  • When challenge information was deleted from a collection, the collection would still claim to be a gift exchange or prompt meme in the blurb. We've cleaned up old instances of this bug and fixed it so it won't happen again.
  • After expanding the list of users on a work with over 50 named kudos, selecting a name that was previously hidden merely hid the list again. Now the name will correctly link to the user's profile.
  • We were using CSS to insert colons on the Statistics page, e.g. in "User Subscriptions: 2" or "Hits: 4", which was not the best way to do it. We now include the colons directly where they should be.
  • Work stats (word count, hits, kudos/comment/bookmark count) now come with individual CSS classes, so you can target dl.stats .hits in an Archive skin to hide hit counts from yourself across the site.

Known Issues

See our Known Issues page for current issues.

Comment

Release 0.9.64: Change Log

Published: 2015-07-01 04:03:36 -0400

The Archive is now using a newer, shinier version of the Ruby language.

Credits

  • Coders: james_
  • Code reviewers: Elz, Ariana
  • Testers: Claire B, Debris, james_, Lady Oscar, Mei, melannen, Michelle Dong, mugenmine, Nerine Luna Cyran, Phoenixacid, Sammie J, Scott, Qem

Details

The Archive was using version 1.9.3 of the Ruby programming language, which is no longer supported. To ensure that the Archive remains sustainable and secure, we have upgraded to Ruby 2.0, and we will be upgrading to even more recent versions of Ruby (and other software!) in the near future.

We'd like to offer a special thank you to our testers, who worked tirelessly to check that all the Archive's features continue to work normally after this update.

Known Issues

See our Known Issues page for current issues.

Comment

Release 0.9.63: Change Log

Published: 2015-06-15 22:12:04 -0400

We've made a few minor bug fixes and enhancements and cleaned up some old code.

Credits

  • Coders: Ariana, james_, Sarken, Scott
  • Code reviewers: Ariana, james_, Sarken
  • Testers: Ariana, briar_pipe, Lady Oscar, mugenmine, Nerine Luna Cyran

Details

  • In some situations, the mass importer Open Doors uses for at-risk archives would incorrectly report that a work had already been imported. We've modified how the mass importer checks a work's import status to prevent this from happening.
  • On the posting form, using an Archive URL beginning with https to cite a related work would result in an error message. Now you can successfully use AO3 URLs beginning with either http or https.
  • Fandom names were indented slightly on challenge prompts and external work blurbs. Now they line up correctly with the title.
  • All tag wrangling pages included an "Unsorted Tags (#)" link, which meant that every time a wrangler loaded a wrangling page, we were counting all the bookmark tags that had yet to be marked as Fandom, Relationship, Character, or Additional Tags. Because this is bad for performance, we moved the link so it will only be included on pages where it is necessary.
  • We had code for emailing co-creators when edits were made to their work. However, we weren't using this code, so we have removed it.
  • The Content Policy workgroup recently proposed changes to the Open Doors Terms of Service. The changes have now been incorporated into our Terms of Service page.

Known Issues

See our Known Issues page for current issues.

Comment

Release 0.9.62: Change Log

Published: 2015-05-30 07:50:45 -0400

This deploy includes several invisible changes which are paving the way for more exciting things to come. Eventually, you'll be able to set a language preference and receive notifications in your chosen language. Work on a fully multilingual Archive continues!

Credits

  • Coders: james_, Ariana
  • Code reviewers: Ariana, Sarken, Scott
  • Testers: hele, Lady Oscar, mumble

Details

  • The list of locales the Archive supports used to be hardcoded into the system; they are now easier to edit.
  • We've started using a tool called rollout which allows us to turn on new features for selected users (the development team, in this case), so we can thoroughly test things within the proper Archive environment before making them available to all users. (Note that is strictly for testing purposes and not to be confused with premium features for paying users. Once something has been deemed ready by the testers, it will be made available to everyone.)
  • We are introducing a new feature which will enable users to select a locale in their Preferences, resulting in customized email notifications in the appropriate language. (Not available yet!)
  • We have started the process of preparing all our email templates for translation, which is a lot of fiddly work and will take a few more deploys. Many thanks to the Translation team for all their help and support in this!

Known Issues

See our Known Issues page for current issues.

Comment


Pages Navigation