AO3 News

Releases 0.9.55 - 0.9.56: Change Log

Published: 2015-04-24 09:40:32 -0400

We've increased our cache storage space, fixed a handful of small but annoying bugs, and made some improvements for the Archive's Abuse and Tag Wrangling teams.

Credits

  • Coders: Enigel, james_, Sarken
  • Code reviewers: Elz, james_, Sarken, Scott
  • Testers: Lady Oscar, mugenmine, Runt, Sara Elizabeth, Sarken

Details

Works

  • Draft works on the Archive are deleted one month after their creation. As a reminder, the deletion date is now included on the draft blurb. (Don't forget to back up your drafts!)
  • It was possible to leave guest kudos on a restricted work by opening the Archive in a second tab and logging out prior to selecting the Kudos button. Doing this will now give an error message.

Bookmarks

  • Editing the tags on a bookmark did not expire the bookmark cache, so the changes did not appear in the bookmark blurb. Now changes to a bookmark tag will appear much more quickly.
  • Ratings on the Bookmark External Work form were listed in alphabetical order. Now they are listed in the same order we use elsewhere on the site (Not Rated, General Audiences, Teen And Up Audiences, Mature, Explicit).
  • In blurbs, the fandom tags on bookmarks of external works (and on series) were indented slightly. Now they line up directly beneath the series or work title.

Invitations

  • On the Request Invitations page for logged-in users, we have added a note stating that requests are manually reviewed and may take several days to be approved.
  • When checking an email address's position in the invitation queue, the page would sometimes give contradictory information, like "There are currently 5 people on the waiting list," and "You are currently number 27 on our waiting list!" We've changed the way position is calculated so that will no longer happen.

Misc.

  • We had more cache storage space available to us than we thought, so we've started using it. \o/
  • Abuse sometimes receives an overwhelming number of reports for a particular work. To ensure that Abuse is able to deal with reports quickly, we have limited the number of times any individual work can be reported in a month.
  • If two tag wranglers were trying to simultaneously wrangle unsorted bookmark tags, they would receive an error page that also had a success message. Now their work will be saved and they will not get an error message.

Known Issues

See our Known Issues page for current issues.

Comment

Release 0.9.54: Change Log

Published: 2015-04-01 03:00:13 -0400

This release focuses on improving the tools Open Doors uses to mass import archives.

Credits

  • Coders: Ariana, Elz, james_, Sarken
  • Code reviewers: Enigel, james_, Naomi, Sarken, Scott
  • Testers: Alison W., Anika Kabit, Lady Oscar, Michelle D., Runt

Details

Importing

  • The Archive doesn't allow users to create warning tags, but importing a work labeled "Warning: Wombats" was leading to the creation of a "Wombats" warning tag. "Wombats" will now be added as an additional tag instead.
  • When Open Doors wanted to do mass imports of rescued archives, they either had to wait for a coder to create custom code for the import or import the entire archive by hand. Now they have a semi-automated method to speed up their work. \o/
  • Works imported by Open Doors are usually placed in a collection named after their original home, e.g. the 852 Prospect Archive collection. However, this had to be done one work at a time, which was very time consuming for large archives. Open Doors now has the ability to mass import works to a collection.
  • If the creator of a work imported by Open Doors used certain characters in their name, the work would be incorrectly attributed to the Open Doors archivist who imported it. Now it will be correctly attributed to the original creator.

Misc.

  • We recently introduced a feature to mark tags as favorites and list them on your home page, but some users were not sure where to find the favorite tags list. We have expanded the message that appears when you favorite a tag to explain that the favorites are listed on the home page.
  • The editing pane on the New Work form does not automatically save its contents; if you leave the page, disconnect from the internet, or if an error occurs in your browser or in the Archive, you will lose all the contents of the form. We have added a message to make it clearer to all users that they must not compose their work directly in the posting form, and should instead save it elsewhere and copy-paste it in.

Known Issues

See our Known Issues page for current issues.

Comment

Release 0.9.53: Change Log

Published: 2015-03-15 13:37:37 -0400

This release contains one bug fix and several background changes that will enable us to upgrade to newer versions of Ruby and Rails in the future.

Credits

  • Coders: james, Enigel, Sarken
  • Code reviewers: Ariana, Elz, Enigel, Sarken, Scott
  • Testers: Lady Oscar, mugenmine

Details

  • We've upgraded to a more recent version of Rails, the framework the Archive runs on.
  • To make our downloads compatible with as many systems as possible, we were using an application called iconv to clean up their metadata (e.g. a work titled "Un Niño" would have a download file named, for example, "Un Nino.epub"). However, iconv will not be supported in newer versions of Ruby, so we have switched to a new method of cleaning the metadata.
  • The YAML parser we previously used to read our configuration files (which control things like how many works are listed on a page) is not supported in newer versions of Ruby. We've now switched to Psych, which is the default parser in Ruby 1.9.2 and up.
  • Attempting to access the Edit page for a Tag Set containing more than 20 tags of a single type was giving an error page. Now it should work again.

Known Issues

The new code for generating MOBI/EPUB/PDF/HTML file names automatically transliterates languages that use non-Latin alphabets, e.g. Japanese or Russian. We can't control how work titles are transliterated, and since it's an automated process, some results will not be correct. Previously, however, titles composed entirely of non-Latin characters were blanked, leading to identical file names like "-.epub", so this is an improvement. The transliteration will only affect the file name and not the contents of the file itself. In particular, titles will still appear correctly in your e-reader or app!

See our Known Issues page for other current issues.

Comment

Release 0.9.51: Change Log

Published: 2015-03-01 04:50:18 -0500

This release includes a few minor bug fixes and enhancements.

Credits

  • Coders: james, Lady Oscar, Sarken, Scott
  • Code reviewers: Ariana, Sarken
  • Testers: Lady Oscar, Michelle Dong, Scott

Details

  • Due to the Children's Online Privacy Protection Act, we require users to confirm they are over 13 years old when creating an account. However, the wording we used could easily be mistaken to mean users had to be 14. We've rephrased it to be clearer that users only need to be 13 years plus one day old to create an account.
  • There were Download links on work drafts; however, attempting to actually download the draft would give an error because we are unable to generate downloads of draft works. We've removed the links.
  • Buttons like "Favorite Tag" and "Subscribe" had more space around them than other kinds of buttons. We've tidied that up.
  • When accessing a work in an anonymous collection, our Abuse team was previously able to see the name of the work's creator. However, this information went missing at some point. We've put it back, and now the work's creator will be able to see their name on the anonymous work as well (it will appear as "Anonymous [username]" or "Anonymous [pseud (username)]").
  • RSpec -- one of our automated testing tools -- was out of date. We've updated to the latest version.

Known Issues

See our Known Issues page for current issues.

Comment

Release 0.9.49: Change Log (New Homepage!)

Published: 2015-02-25 14:22:13 -0500

Credits

  • Coders: Sarken \o/
  • Code reviewers: Elz, james_
  • Testers: james_, Lady Oscar, mugenmine, mumble, Nerine Luna Cyran, Sammie J., Sara H., Scott

Details

New Features

  • We made the Archive homepage more useful for guests by listing available fandom categories to browse, highlighting recent news posts, and pointing out the benefits of creating an account. For logged-in users, we added a random selection of their marked-for-later works, the latest unread comments from the inbox, and a list of favorite tags.
  • With the new Favorite Tags feature, you can now pin up to 20 canonical tags (fandom, character, relationship, etc.) to the homepage, so you can always access your most frequently visited tags when logged in. To add a Favorite Tag, simply go to the tag's work listing (e.g. Polyamory) and select the "Favorite Tag" button. A link back to the tag's work listing will immediately be added to your homepage.

Inbox Fixes

  • We were experiencing intermittent problems with deleted works/chapters leaving behind "ghost comments" in some users' inboxes. Because these comments counted as unread comments, but couldn't be deleted or marked read, users could be left with a permanently incorrect inbox count. We think we've tracked down the cause for this and fixed the bug now.
  • When paging back in the inbox and deleting an old comment, users would get redirected to the first page after successful deletion. Now they'll stay on the page they were on.
  • While a work is in an anonymous collection, comments left by its creator are displayed as "Anonymous Creator", with a dedicated icon that's different from the Archive default icon. The icon wasn't used in the inbox view for anonymous comments; now it is!

Misc. Fixes

  • When subscribing to or unsubscribing from a work, series, or user, the page would previously reload with a success message. Now we're using AJAX to handle these tasks, which saves us a page reload. \o/
  • It was impossible to delete a work from your history with JavaScript disabled (you'd get an Error 404 when trying). Now it works!
  • Canonical tags have a separate name we use for alphabetical sorting, so tags like "The Fandom" will be alphabetized by "F" instead of "T." Some older tags were missing this name, though, so we added it in order to make it possible to alphabetize users' Favorite Tags lists.
  • Fixed an issue with some forms having white-on-white text when using the Reversi skin.

Known Issues

See our Known Issues page for current issues.

Comment

Releases 0.9.47 - 0.9.48: Change Log

Published: 2015-02-16 04:03:48 -0500

Credits

  • Coders: Ariana, Elz, james_, Lady Oscar, Sarken
  • Code reviewers: Elz, Enigel, james_, Scott
  • Testers: Agwen, Anika Kabit, james_, Lady Oscar, Matty, Michelle Dong, mugenmine, mumble, Sarken

Details

Works & Tags

  • No language was being set for imported works, which meant the works would not show up when users filtered by language. Since our code can't detect the language of an imported work, it is now automatically set to English at the time of importing. If necessary, you can change it to the correct language by editing the work.
  • In certain circumstances, it was possible to leave kudos on your own work. This will now trigger an error message and the kudos won't be recorded.
  • The page listing the 20 most recent comments left on works all across the Archive is now only accessible to site admins.
  • Tags that used to be canonical but which were later made synonyms of new canonicals were still appearing in the Top 10 Tags list in the filters. This should no longer happen going forward; however, old instances still need to be cleaned up.

Wording Fixes

  • The browser page title for our 503 error page incorrectly said, "Exceeded maximum downloads per minute." Now it will say, "Page responding too slowly."
  • The help text explaining the "General Audiences" rating has been updated.
  • There was a button and a link on your invitations page that said "Request More," which was confusing/misleading if you'd never requested invitations before. Now it says "Request Invitations."
  • Where "invites" was used as a noun on the site, we have replaced it with the more correct "invitations".
  • The button labels on a user's Manage Invitations page are now capitalized to match our usual style.
  • On the page where creators can claim their works after an Open Doors fanwork archive import, we changed some wording and the link to contact Open Doors.
  • Updated the help message listing the CSS properties that can be used in skins.

Invisible Fixes

  • The code for our Abuse form and Support form has been refactored (rewritten to follow good coding practices), with no changes to functionality.
  • When accessing a single bookmark listing for an external work, there was an extra, empty HTML element on the page. It has been removed.
  • The page that asks you to confirm you are willing to access adult content was missing some HTML tags. They have now been added.
  • We changed our server logs to be angrier and take up less space (i.e. started using the lograge gem for Rails).

Known Issues

See our Known Issues page for current issues.

Comment

Release 0.9.46: Change Log (The invitation queue is back!)

Published: 2015-02-01 04:45:18 -0500

This batch of code includes several new features and enhancements aimed at assisting the Abuse team in their work, as well as some changes under the hood to protect us against attacks from download bots while keeping disruptions for our users to a minimum.

When we announced that we'd be suspending our automated invitation queue at the beginning of the month, we didn't plan for it to be closed quite this long! Writing, testing, and improving the new code, while also working with Abuse and taking care of our servers through planned and unplanned downtimes, took considerably longer than we expected.

While the queue was closed, we continued to provide invitation codes to existing users upon request. According to our records, we handed out over 5000 such invitations this month, which is more than three times our usual number. To everyone who reached out to friends and strangers to share invitations, we thank you!

If you wanted to create an account in January and couldn't - we're very sorry for making you wait! The queue is now back in business: request an invitation today and receive a code in 48 hours or less!

Credits

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

Details

Admin

  • In order to combat spam works (e.g., works consisting solely of advertisements), our Abuse team will now be automatically notified of accounts with a suspicious level of activity or works with suspicious content, allowing them to investigate before the problem gets out of hand.
  • When our Abuse team hides a work that is under investigation, the creator(s) of the work will now receive an automatic email, letting them know the work has been hidden intentionally and not as the result of a bug. The email also contains a link to the work so that they (but no one else) can access it while it is hidden.
  • Users whose accounts have been permanently suspended (banned) are not allowed to create new works, but it was still possible for other users to list them as co-authors. Now they cannot be added as co-authors unless the ban is lifted.
  • When a user's account is temporarily suspended, the error message they receive when attempting to post, comment, or perform other actions will now let them know when they can expect their suspension to be lifted.
  • Attempting to post, comment, or perform other actions using a suspended account previously resulted in an error message that said, "Please contact us for more information." The message has been clarified to say, "Please contact Abuse," and now provides a link to the appropriate contact form.
  • When an admin deleted an invitation request submitted through our automated queue (e.g., because the requester was likely to be a known spammer), they would be redirected to the first page of the list, which was annoying if they needed to delete more than one request on the same page. Now they will be returned to the page they were on.

Downloads

  • We were receiving reports from users whose IP addresses were blocked from accessing the Archive for downloading too many works too quickly, even though they hadn't done anything wrong. This would happen, for example, if their browser tried to download a file many times, despite the user having only clicked the download button once. We have added code and tweaked server settings to make this much less likely. In particular, we are now serving cached copies of downloads to users, which are currently refreshed on the server as soon as a work is updated.
  • During site-wide downtime because of an overwhelmed server, users were receiving an error page that incorrectly stated they were downloading works too quickly. We've corrected the error page we give when the Archive is down and also added a dedicated error page to let users know when they are posting works too quickly.

Known Issues

See our Known Issues page for current issues.

(Please note that while it looks like we skipped several version numbers since our last batch of updates (Release 0.9.41), you haven't missed out on any new code! The jump is due to a few test deploys to get our deploy script into shape after adding another server to our line-up.)

Comment

Releases 0.9.40 - 0.9.41: Change Log

Published: 2015-01-11 08:00:49 -0500

Credits

  • Coders: Elz, Enigel, james_, Marie Markwell, Sarken, Scott
  • Code reviewers: Elz, Enigel, james_, Sarken
  • Testers: Anika Kabit, Lady Oscar, Matty, mugenmine, mumble, pendrecarc, Sarken

Details

Accounts

  • It was previously possible for suspended accounts to request new invitations and access the ones already granted. We're now blocking those accounts from using their invitations (e.g. to invite friends or create a new account) and from requesting more.
  • The big chunk of code responsible for handling accounts and user-related actions had become unwieldy and messy over time. It has now been refactored--cleaned up and reorganized--to adhere to best practices.

Challenges

  • Challenges that were set to "moderated" (i.e. works can be submitted, but must be approved by a mod before they appear) were not included on the Open Challenges page. Now they are.
  • Previously, if you went to the posting form and used one of the Open Assignments checkboxes to fulfill a gift exchange assignment, but the gift exchange collection was closed, you'd get a 500 error. Now you will be redirected back to the posting form.

Works

  • To help battle spam works (see our post Urgent Anti-Spam Measures for context), we've started recording the IP addresses from which works are posted, with the information only visible to site admins, e.g. Abuse personnel. This allows us to suspend spam accounts (accounts specifically set up to flood the Archive with advertisements) more efficiently.
  • On the "Import New Work" page, the link to the relevant Importing & Mass Editing FAQ was broken, as it hadn't been adjusted to the new FAQ structure yet. It works now!
  • The button for displaying a work in individual chapters, rather than all on one page, was renamed from "View Chapter-by-chapter" to "Chapter by Chapter" for button labeling consistency.
  • The "Subscribe to the feed" button on work lists by tag (e.g. Agent Carter (TV)) was renamed to say "RSS Feed", to distinguish it from our Subscription feature. (Read more in our Subscriptions and Feeds FAQ.)

Misc.

  • The Error 500 page was displaying a sad little Archive mascot juggling Error 502 messages before, which was misleading. It is now merely sad.
  • As our temporary donation page (created for the last Membership Drive) will be in use a while longer, we adjusted some wording and links to avoid confusion.
  • The help text for the "Apply to make public" option for Site Skins was advising to use CSS comments for attribution and notes. However, due to the way we currently sanitize CSS, the comments are getting stripped out. The help text now tells you to use the Description field. Note: We are currently not reviewing submitted Site Skins, and are thinking of better ways to handle skins in general.

Known Issues

See our Known Issues page for current issues.

Comment


Pages Navigation