AO3 News

Post Header

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

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

Post Header

Published:
2015-09-13 19:38:22 -0400
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.

Comment

Post Header

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

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

Post Header

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

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

Post Header

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

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

Post Header

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

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

Post Header

Published:
2015-05-11 13:40:20 -0400
Tags:

We addressed some issues with the filters that had cropped up on some mobile devices after our last code update, so sorting & filtering should be working again for everyone. We also fixed a few tiny bugs.

Credits

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

Details

Filters

  • In an earlier code update, we had changed the way filters appear on mobile devices, to prevent the need for excessive scrolling just to get to the sorting options. On some devices, unfortunately, it was impossible to select some options in the filters due to the way they overlaid the other page content. We've now changed the layout so that when you tap the "Filters" button, the Sort and Filter sidebar pushes the other content out of the way.
  • The "Filters" button was missing when accessing a user's bookmarks while logged out; this has been fixed.
  • The "Filters" button (and the "Bookmark External Work" link) is now included when accessing a collection's bookmarks.

Misc.

  • Upon request by the Development & Membership committee, we made changes to the Drive page in preparation for the AO3 Membership Drive.
  • We made a small change to one of our automated tests which was failing because of a date-related issue, and another small change to another test that was failing intermittently for unknown reasons.
  • We added more caching to some of the administration settings on the Archive, which will reduce database calls during peak times.
  • We updated some of the database schema files that had become outdated due to previous code releases.
  • An image used in the Tumblr share code on works and bookmarks was causing a security warning when accessing the Archive using https. Now we use a protocol-relative URL for the image to prevent such warnings.

Known Issues

See our Known Issues page for current issues.

Comment

Post Header

Published:
2015-04-30 18:43:08 -0400
Tags:

We fixed a few bugs and took care of a performance issue caused by the dropdown user menu. Also, no more endless scrolling to reach the Sort and Filter box on mobile devices!

Credits

  • Coders: james_, Sarken, Scott
  • Code reviewers: james_, Sarken, Scott
  • Testers: Lady Oscar, mugenmine, mumble, Sam Johnsson, Scott

Details

  • The filters for works, bookmarks, and so on were positioned at the bottom of the page for users on small screen devices, which made for a lot of scrolling. For users who have JavaScript enabled, we have added a button that will cause the filters to open on top of the page. (For users with JavaScript disabled, the button will jump down to the filters at the bottom of the page.)
  • The numbers in the "Hi, user!" dropdown menu (e.g. "My Works (17)") had to be calculated every time a logged-in user loaded a page, any page. This was bad for performance. We've removed these counts to reduce the strain on our database. (This doesn't affect the dashboard menu, where you can still find all relevant numbers.)
  • Like FanFiction.Net, the website Quotev blocks any attempts to import fic from their site. We have added a warning and an error message to our Import Work page to let users know about the block.
  • There was no way to tell which email address was associated with your account if you did not have the "Show my email address to other people" preference enabled. Now it will be displayed on the Change My Email page.
  • A user's History page includes information about the last time that user accessed any given work. However, this information was only updated if the user accessed the first chapter of a multi-chapter work. Now it will update regardless of which chapter the user accesses.
  • Admins must choose a language when posting a translation of a news post. However, the list of available languages was very long and included languages we do not currently offer translations in (e.g. Latin and Klingon). We've limited the list to only include languages for which we have translated news posts or FAQs.
  • The links in a user's dashboard menu were difficult to select when using a mouse or trackpad with the Dash Line skin (or with the default skin, which uses the same code as Dash Line on any screen narrower than 640px). We've fixed the overlapping elements that caused this issue, and now the links should be easier to select.
  • We've added a simple page which our load balancer can use to ensure a server is up and running before sending work its way.

Known Issues

See our Known Issues page for current issues.

Comment


Pages Navigation