AO3 News

Post Header

Published:
2017-03-24 16:11:18 -0400
Tags:

We've fixed CSV downloads for gift exchange sign-ups, corrected fandom counts in collections, and made a whole heap of behind-the-scenes changes, test improvements, and other minor fixes.

Credits

  • Coders: Ariana, Cesy, cosette, cyrilcee, David Stump (Littlelines), DNA, james_, potatoesque, redsummernight, Sammie Louise, Sarken, Scott, tickinginstant
  • Code reviewers: Ariana, bingeling, james_, Naomi, potatoesque, redsummernight, Sarken
  • Testers: Betsy, Lady Oscar, mumble, Rebecca Sentance, redsummernight, Runt, Sammie Louise

Special thanks to redsummernight, who has contributed their first pull request as an AD&T volunteer and completed their training!

Details

Bug Fixes & Enhancements

  • [AO3-4844] - We've started using the Devise gem to handle admin logins.
  • [AO3-4834] & [AO3-4835] - In our tag set code, we had two places where users would get a 500 error instead of the nicer, more specific message we meant to give them. Now they'll get a "What Tag Set did you want to look at?" error instead.
  • [AO3-4877] - Following a recent release, it was no longer possible to download gift exchange sign-up CSVs. We've fixed that, and we've also added some tests that will hopefully keep it from happening again.
  • [AO3-4808] - Editing a work and removing its fandom used to save the work, but return a 500 error, resulting in an invalid work and a confused user. Trying to save a work without a fandom will now not save the work and show the user an error message instead.
  • [AO3-4045] - If your chapter was over 500,000 characters long, you'd get an error message that included the oh-so-helpful suggestion, "Maybe you want to create a multi-chapered work?" Since you were already trying to do that, we removed that from the error message.
  • [AO3-2431] - A lot of collections were showing fandom counts that were higher than the actual number of fandoms in that collection. We realized that was because the code was also counting meta tags, so we made it stop doing that.
  • [AO3-4858] & [AO3-4922] - As detailed in Issues With Posting Works (And What We're Doing to Solve Them), we deployed some new caching code to help speed up work posting. Unfortunately, the code didn't work and we had to revert it.

Behind-the-Scenes

  • [AO3-4883] - A security vulnerability was discovered for one of the gems we use, so we quickly updated to the patched version. (We only use the gem for our automated tests and don't believe we were at risk, but better safe than sorry!)
  • [AO3-4895] - The tool we use to check our code style and syntax was giving us suggestions that only worked in a newer version of the Ruby language than what we're currently using. We changed the tool's settings so it will only suggest things for the version of Ruby we're using.
  • [AO3-4780] & [AO3-4782] - We've added strong parameters to FAQ categories and invitation requests.
  • [AO3-4918] & [AO3-4920] - In order to deploy the caching changes for AO3-4858, we temporarily amended our deploy script so the deploy process would take less time, but require us to briefly put the Archive into maintenance mode. After we were done, we reverted those changes.
  • [AO3-4825] - We had some help files that were outdated and no longer in use, so we removed them.
  • [AO3-4851] & [AO3-4933] - We updated the database schema file in our repository, since recent changes to our database structure meant it was out of date.
  • [AO3-4443] - We've updated our version of Pry, a gem that provides a number of development tools.
  • [AO3-4856] - We had some unused code in the tag set nominations controller, so we deleted it.

Tests

  • [AO3-4830], [AO3-4897], [AO3-4908], [AO3-4901] - We've extended the automated tests for tag sets to cover more lines in the controller and more use cases. We've also reorganized the tests into smaller files in their own directory.
  • [AO3-4726] - We've brought test coverage of the comments controller up from 71% to almost 94%.
  • [AO3-4914] - We now have tests to cover all the types of tags you can use on a bookmark of an external work.
  • [AO3-4887] - We've begun improving the test coverage of the challenge assignments controller.
  • [AO3-4810] - Our test coverage for the prompts controller is now at 93%, which is much better than the 65% it started at.
  • [AO3-4889] - The series controller now has 96% of its lines covered by automated tests.
  • [AO3-4916] - We've added more tests for the external authors controller.

Known Issues

See our Known Issues page for current issues.

Comment

Post Header

Published:
2017-02-21 21:34:10 -0500
Tags:

Our mission to update Rails continues with more clean up, strong parameters, and tests, but we also have a big pile of small bug fixes and enhancements, not to mention a few new tools for the volunteers who keep the Archive running.

Credits

  • Coders: Ariana, CJ Record, cosette, james_, potatoesque, Sarken, Scott
  • Code reviewers: Ariana, bingeling, Cesy, james_, Naomi, potatoesque, Sarken, Scott
  • Testers: Alison Watson, james_, Lady Oscar, Sarken

Details

Tests

  • [AO3-4771] - We added tests for managing collection membership.
  • [AO3-4797] - We improved our test coverage for the works controller, bringing it up to more than 90%.
  • [AO3-4803] - We added still more tests for managing collection membership! In fact, the collection participants controller now has 100% test coverage. \o/
  • [AO3-4804] - We increased test coverage of the challenge assignment controller.
  • [AO3-4819] - Our skin (code) is now 93% covered.
  • [AO3-4823] - We added more tests for the tags controller code.
  • [AO3-4837] - We added tests for the collection profile controller.
  • [AO3-4822] - The owned tag sets controller now has excellent test coverage.
  • [AO3-4809] - We added some more tests for the bookmarks controller and in the process updated the success messages related to adding existing bookmarks to moderated collections.

Rails

  • [AO3-4791] - Just to make sure everything goes smoothly with our Rails update, we added mass assignment protection to some files where we weren't doing mass assignment and thus didn't need to protect against it.
  • [AO3-4798] - We added strong parameters to the subscriptions code.
  • [AO3-4799] - And to the favorite tags code.
  • [AO3-4821] - The skin code now has strong parameters.
  • [AO3-4817] - We added strong parameters to the code that lets site admins block email addresses from being used for logged-out comments.

Bug Fixes

  • [AO3-4524] - On our About page, the link to the Organization for Transformative Works FAQ page was broken. We've updated it to point to the right place.
  • [AO3-4529] - Since we were already working on the About page, we decided we should also fix the broken link for contacting the OTW's Communications Committee.
  • [AO3-4549] - There's a bug that lets users edit their works to remove the fandom tag, and while we haven't deployed the fix for that yet, we have made it so removing the fandom tag no longer prevents users from updating or accessing fandom-less works.
  • [AO3-4738] - While working on improving our automated test coverage, we discovered site admins' ability to change the default site skin was broken. (This is why test coverage is so important!)
  • [AO3-4747] - Now when a challenge moderator who has JavaScript disabled attempts to purge assignments for their challenge, they are taken to a page asking them to confirm the action.
  • [AO3-4846] - Shortly after deploying changes to the series navigation, we realized those changes weren't displaying on every work. So, quick like a bunny, we updated the caching code for it. (It's always caching!)
  • [AO3-4848] - A whole lot of empty space was inadvertently added to the top of collection profile pages while we were fixing another issue. We've gotten rid of that extra space.
  • [AO3-4849] - The error message that tells logged in users they cannot currently request invitations had an outdated link to the Open Doors contact page. The old URL forwarded to the new page, but we thought it would be good to update it anyway.
  • [AO3-4827] - When importing a multi-chapter work from another site, the word count only included words from the first chapter. We've fixed it so now all the words count.
  • [AO3-4644] - Comment emails were generally sent even if the comment was deleted moments after posting, but sometimes there would be so many emails queued up that the email would error. We changed the way comment emails are coded so comments' emails will always be sent, no matter how long the queue.

Enhancements and New Features

  • [AO3-4357] - We added the ability for site admins to disable work downloads so it will be easier to do routine site maintenance. (But don't worry -- we'll let you know before we turn it off!)
  • [AO3-4732] - The error 500 page previously said, "We've been notified about this issue and we'll take a look at it shortly," which was not true -- while we do log errors, we are not notified of each individual error. This message was dissuading users from contacting us about easily fixable things, so we changed it to say, "If you are receiving this error repeatedly, please contact Support. In the form, please include a link to the page you're trying to reach and how you're trying to reach this page."
  • [AO3-4788] - We added an Acknowledgements page to our GitHub repository so we can thank the companies who provide the tools and technology we use.
  • [AO3-4109] - We used to use angle quotation marks (« and ») as the links in works' series navigation, but they were difficult to use on touch devices, and confusing to anyone using a screenreader. We changed the links to say "Previous Work" and "Next Work" instead, which makes the links both bigger and clearer.
  • [AO3-4839] - We also added some dividers to the series navigation to make it clearer where the links began and ended.
  • [AO3-3991] - Some of the various pages related to creating and using site and work skins were missing navigation items or had their navigation items arranged in unexpected ways. We added the missing options and made the display more consistent with the rest of the Archive.
  • [AO3-4716] - We've given site admins the ability to search for multiple users by email at one time. This will help Open Doors cut back on the number of duplicate imports that happen when they upload an archive.

Internationalization

  • [AO3-4297] - We changed the way account activation emails are coded so the Translation team will be able to translate the email into a variety of languages.
  • [AO3-4301] - We also changed password reset emails to allow them to be translated.
  • [AO3-4302] - And the "you've been added as a co-creator of this work" emails!
  • [AO3-4303] - Also the email that lets you know your account's email address has been updated.
  • [AO3-4305] - Ditto the email you receive when you (or one of your co-creators) deletes a work.
  • [AO3-4306] - And, lastly, we've made it so Translation can translate the email we send when a site admin deletes a work.

Clean-up

  • [AO3-4806] - We deleted some unused challenge assignment code.
  • [AO3-4745] - Sometimes multiple users bookmark the same external work, or someone bookmarks a work that another user has cited as an inspiration. It was previously possible for site admins to combine these duplicate external works, which was a good idea in theory, but in reality, not something we have the resources to monitor. We've removed admins' ability to do that.
  • [AO3-4811] - We removed some unused prompt meme controller code we found while writing tests.
  • [AO3-4766] - We removed some Gems we weren't using.

Known Issues

See our Known Issues page for current issues.

Comment

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


Pages Navigation