AO3 News

Release 0.9.14 (Part 6): Change Log

Published: 2014-04-17 17:49:23 -0400

This deploy includes code contributions by Ariana, Cecilia, Emily E., Lady Oscar, Nathan J. Xaxson, Priscilla, sarken, Scott, and tuff_ghost and was tested by Ariana, Camilla M., Lady Oscar, matty, Qem, Sam Johnsson, sarken, Scott, and theteapot. Special thanks to Enigel for code review and merging!

Details

  • Collections & Challenges
    • The page listing all Collections can now be filtered by type: Gift Exchange, Prompt Meme, No Challenge, Any. The buttons for sorting results have been moved into the sidebar to be consistent with the "Sort and Filter" box for works.
    • If a user had multiple assignments in the same gift exchange (e.g. as a pinch hitter), the page heading was showing its HTML code. This has been fixed.
    • Having a work with a co-creator on some chapters, but not others, would partly break anonymity when adding the work to an anonymous collection. It now displays the "by Anonymous" bylines on all chapters.
    • Added some wording to the page for creating a collection to make it more obvious that spaces are not allowed in the Collection Name field. Also explicitly added this information to the error message that appears when a user tries to create a collection with an invalid Collection Name.
  • Works & Series
    • Large images in a work were cut off on small screens, e.g. phones. Users can now scroll to the side to see the whole picture, even if zooming out to fit the image on the screen isn't possible.
    • When the preference "Hide additional tags (you can still choose to show them)" was selected, clicking to reveal the tags on a work would show them in alphabetical order, not the order they were put in by the creator. This has been fixed.
    • The "Edit Tags" option, when used on an unposted draft, previously offered no way to re-save as a draft, only buttons for previewing and posting. A "Save Without Posting" button has now been added.
    • The "Works inspired by this one" link wasn't visible on the inspiring work if that work's last chapter was still a draft. This was fixed to show the note on the last posted chapter.
    • When deleting a work or chapter, a confirmation pop-up would ask you if you were really sure, but wouldn't spell out all the consequences for each. For works, it now says, "Are you sure you want to delete this work? This will destroy all comments and kudos on this work as well and CANNOT BE UNDONE!" For chapters, "Are you sure you want to delete this chapter?"
    • The plain text version of the email you get when you delete a work referred to "your story"; it now properly says "your work".
    • A series can now be properly deleted even when JavaScript is turned off.
    • In the series description, right-to-left text was forced into left alignment. This has been fixed for all fields containing descriptive user input or blocks of information, e.g. on user or collection profiles.
    • On the page for orphaning a series, some text was accidentally showing a bit of HTML formatting code. Now it does not.
    • The preference to hide work skins used to say "Hide other people's work skins", even though it hides all work skins, including your own. It now says "Hide work skins (you can still choose to show them)".
  • Statistics
    • Choosing to hide hit counts (whether on your works or Archive-wide) would also hide the sort by date option on your Stats page. This has been fixed.
    • The option to pick between "Fandoms" and "Flat" view on one's Statistics page was one toggle; we changed it to always show both buttons, with the selected one marked.
    • Draft works were showing up on one's Statistics page (with zero hits, kudos, etc.). The Stats page will now only list posted works.
  • Tags
    • Selecting the option to keep tags in a tag set hidden (e.g. during nominations) would hide the whole tag set from searches. The tag set is now findable by name, even if the tags in it aren't visible (yet).
    • We added the tag type to some links on tag wrangle pages, and some other text for clarity.
    • Based on feedback from tag wranglers and requests from the Tag Wrangling committee, we removed the 'Add new tags' field from tag wrangle pages to reduce clutter and simplify wrangling. The field only allowed adding canonical tags, and duplicated a function available on the tag edit page for the fandom.
    • On tag wrangling pages, links such as "Show All", "Canonical", etc. now turn into span elements to indicate the current selection. This is consistent with the behavior of navigation links everywhere else on the Archive.
  • Misc.
    • Updated the list of supported languages on our Support form. You can now send in questions and suggestions in العربية, Bahasa Indonesia, Deutsch, English, español, français, 한국어, italiano, Kiswahili, Nederlands, polski, português, suomi, svenska, Türkçe, and 中文!
    • The confirmation pop-up when deleting one's History now points out that this will also delete the "Marked For Later" list.
    • The "Marked For Later" button now retains its "pressed" appearance when viewing pages other than the first.
    • Cleaned up and standardized some navigation elements on the pages for changing one's username, password, or email address.
    • The help text for the "Plain text with limited HTML" option for comment replies was opening in the same window, potentially leading to loss of information you had already put into the comment text box. It now opens in the usual help text window.
    • The page for creating an account said, "You need to be over 13 years old to become a registered member of the archive. (Sorry to our younger readers! You'll be more than welcome when the time comes.)" - focusing specifically on written fanworks. It now addresses "anyone younger."
    • We added text to the Skin Wizard page to clarify that the wizard can only be used to create site skins. We also updated the help text for the "Percent of base font size (%)" box to better describe how it works.
    • In Internet Explorer 9, the HTML download display used the wrong font, due to a combination of a bug in IE9 and our stylesheets. We've amended our stylesheets to prevent this from happening.

Known Issues

See our Known Issues page for current issues.

Comment

Release 0.9.14 (Part 5): Change Log

Published: 2014-04-13 11:34:09 -0400

This deploy includes code contributions by Cecilia, Enigel, larissa, Naomi, Sam Johnsson, Sarken, and Scott and was tested by Emilie, Lady Oscar, and mumble.

Details

  • The first chapter title in multi-chapter works would only be displayed once a second chapter was added. This is now fixed to show the chapter title right from the start.
  • The code that deletes drafts a month after creation was sometimes failing to completely destroy the work and associated tags. This should now be fixed.
  • The information about drafts getting deleted after a month was only displayed on the page listing all drafts. We have now added the information, including the exact deletion date, at the top of each draft.
  • Embeds from YouTube were failing (unless users added the http: string to the embed code); this has been fixed to allow all embed codes from YouTube (and other permitted domains) as they are generated.
  • Some tags were showing a negative number for how many times they were used in works. The cause for this bug is in our chosen framework, Ruby on Rails, and will be fixed in future updates of Rails. In the meantime, we will run a script to fix those erroneous use counts, so any tags with zero uses will not linger forever.
  • When a tag wrangler's user account was deleted, their assigned fandoms to wrangle would show up on the "Fandoms in Need of a Wrangler" page even if other wranglers were still assigned to the fandom. This has now been fixed.
  • Linking to the /invitations page for a non-existent or misspelled user was causing an error 500; this has been fixed.
  • When hovering over the little square symbol in the top right corner of a bookmark blurb, the number of bookmarks previously popped up as title text, especially necessary for works with over 99 bookmarks where only a * is currently displayed. That hover text had vanished and is now back again.
  • The Status/Posted/Words information on the "My Assignments" page was stacked on top of each other; now everything displays in one line as expected.
  • Fixed some CSS for the public Wrangling Guidelines pages.

Known Issues

See our Known Issues page for current issues.

Comment

Release 0.9.14 (Part 4): Change Log

Published: 2014-04-04 11:30:14 -0400

This deploy consists of code contributions by Naomi and was tested by the combined efforts of many volunteers, including testers, coders, tag wranglers, and Support personnel. Special thanks to QA lead Lady Oscar for her diligence!

These code changes fix several issues with the way potential matches for a gift exchange are generated and displayed. Further refinements and improvements to challenge features are planned.

Details

  • Previously, the "Matching" page included a list of all the potential givers for each participant, sorted by quality of match, which frequently caused the page to take way too long to load: it timed out and just displayed an error. We changed the way matches are generated and saved, so the page should be much more stable.
  • In addition, the page consisted of separate forms for dealing with various issues (users without potential matches, users who didn't have an assignment, etc.), leading to a messy and confusing layout. We have now put each listing on a page by itself, so you can focus on each problem (no match at all, no assigned recipient, etc.) one by one.
  • Very infrequently, invalid sign-ups can be created, e.g. due to a server hiccup during times of high traffic and a large volume of sign-ups. This previously caused the assignment process to crash silently in the background. We now alert individual users if their sign-up is invalid. We also check for invalid sign-ups and notify the moderators by email before running potential match generation, so they can fix them before they get to the problematic step.
  • The assignment view has been rearranged - all assignments now list an ID and a pair of recipient and giver. Clicking on the assignment ID will show you their respective requests and offers to gauge the match.
  • The help text on the various little forms (accessible through the little blue question marks) has been updated and expanded.

Known Issues

See our Known Issues page for current issues.

Comment

Release 0.9.14 (Part 3): Change Log

Published: 2014-03-05 08:21:13 -0500

This deploy includes code contributions by Ariana, Enigel, and Sarken and was tested by Ariana, Lady Oscar, Naomi, and Sarken.

Details

  • The form that allows Archive admins to change various site settings and put up admin banners wasn't as user-friendly as it could have been: the text was crowded, the options were ordered randomly, and we couldn't see the full text of the admin banner when we needed to edit it. Now similar options are grouped together and everything is easier to read, which makes our admin team much happier.
  • The interface for posting and editing AO3 News posts now has an autocomplete function for the post tags.
  • Users can filter News posts by tag or language, but the filter form wasn't coded as accessibly as it could have been. Now the labels are properly associated with their dropdown menus, so screen readers will tell users what the menus are for.
  • If you attempted to share a multi-chapter work on Twitter while in chapter-by-chapter view, the only thing in the tweet would be the URL. Now the tweet says, "[TITLE] by [PSEUD] - [FANDOM TAG] [URL] via @ao3org" as it already does for oneshots.
  • The forms for editing and posting works contained a field called "Custom Stylesheet" that allowed users to apply a Work Skin to their works. We changed the name to "Select Work Skin" to make its function clearer.
  • The form for editing information on multiple works wasn't as user-friendly as it could be. We've made the "* Required information" notice stand out some more and rearranged the Visibility and Comment Settings checkboxes to make it easier to see which checkbox corresponds to which option.
  • User who set their preferences to hide warnings or additional tags may have noticed that, if they selected the option to reveal the tags, there were two commas between each tag. Oops! Now it's one comma per tag.

Known Issues

See our Known Issues page for current issues.

Comment

Release 0.9.14 (Part 2): Change Log

Published: 2014-03-01 14:31:56 -0500

This deploy includes code contributions by Enigel, James, Sarken, and Scott and was tested by Camilla, Emilie, Lady Oscar, mumble, pocketmouse, and Qem.

Details

  • In the tag wrangling interface for fandom tags (showing characters, relationships, etc. for that fandom), we replaced the button for showing "non-canonical" tags with a "synonymous" button. Now it only shows tags that are synonyms of canonical tags, since there is already a separate listing for unfilterable tags (tags that are neither canonical nor synonymous).
  • When sorting incoming tags by number of uses, tags with the same count are now ordered alphabetically. This will make it much easier for wranglers to keep track of which tags to wrangle or edit.
  • There was some slightly wonky HTML on the "My Sign-ups" page; it's fixed now.
  • The message at the top of the "Unposted Drafts" page about drafts being automatically deleted was too easily overlooked. We added a cautionary yellow background to the message (and also urge all users not to use Archive drafts as the only place to store their work).
  • When posting a new work, you could mark it as "a remix, a translation, or inspired by another work." We have added "a podfic" to this part of the form to make the option explicit.
  • Our emails, e.g. kudos or comment notifications, will now include sender information ("Archive of Our Own") and won't merely display the do-not-reply address anymore.

Known Issues

See our Known Issues page for current issues. If you're having trouble with lost formatting since our Rich Text Editor upgrade, please have a look at the RTE-related issues and workarounds.

Comment

Release 0.9.14 (Part 1): Change Log

Published: 2014-02-26 05:31:24 -0500

(For Release 0.9.14, we will be trying something new! Bug fixes and improvements will be tested in very small batches, and then pushed to the Archive as soon as they're ready. This will make for much smaller, more frequent Release Notes, until we consider version 0.9.14 done! Stay tuned.)

This deploy includes code contributions by Enigel, Lal, Sarken, and Storm and was tested by Ariana, Lady Oscar, Naomi, and Scott.

Details

  • Fixed another issue with signup summaries generated for gift exchanges. This remains a somewhat brittle piece of code, and we continue to work on improvements.
  • Removed the Subscriptions count in the user menu in the header for performance reasons. In the same menu, Preferences now says My Preferences, to match the rest of the items.
  • The order of the Language, Custom Stylesheet, and Privacy options in the work editing form was different from the order when editing multiple works at once. Both forms now follow the same order.
  • Fixed the page titles for our FAQ and Terms of Service pages. They previously said "Tos" and "Faq", now follow proper capitalization.

Known Issues

See our Known Issues page for current issues.

Comment

Release Notes for Release 0.9.13

Published: 2014-02-20 08:14:30 -0500

Welcome to Release 0.9.13. Ariana, Elz, Emily E, Enigel, james_, Naomi, sarken, Scott, and Stephanie S. contributed code to this release, which was tested by our awesome testing team: Alison Watson, aralias, Ariana, Camilla M, Emily E, Eve Forbes, Lady Oscar, Michelle Dong, Naomi, mumble, runt, Sam Johnsson, sarken, and Scott.

We're starting the year with a much needed performance fix, a major update of our Rich Text Editor, and a few importing fixes to make the lives of our Open Doors team a little easier. We have many big plans for the next several months and are also working continuously, and often invisibly, on upgrading and improving our server setup. For downtime announcements (both planned and unplanned), please watch our @AO3_Status Twitter account.

Highlights!

TinyMCE Upgrade!

We've updated our Rich Text Editor of choice, TinyMCE, from version 3.5.6 to 4.0.11. This takes care of several long-standing bugs in one fell swoop, and enables us to integrate bug fixes more regularly going forward. We took great care to make TinyMCE work properly with our own HTML sanitizer, which formats the underlying code more or less to our liking. However, some combinations of writing software, browsers, and formatting choices still pose a problem that cannot be easily fixed.

In particular, Google Drive/Docs documents will not retain their italic and bold formatting when pasted into the editor, and text from Scrivener is best pasted from the HTML output option. We've included a bunch of notes and usage tips in the new Rich Text help, accessible through the little question mark symbol after "Type or paste formatted text."

We are doing our best to make the Rich Text Editor work for as many writing platforms as possible, but we're limited by the features and bug fixes TinyMCE's own tireless team of developers gives us. For very complicated formatting (or even colors!), please consider writing your own HTML and using a work skin.

Archivist Imports!

Our amazing Open Doors volunteers have been hard at work preserving stories from at-risk archives! With the exception of two very large collections which were imported in bulk (Smallville Slash Archive and 852 Prospect), they've been mostly using the same importing tool that is available to all our users. Regrettably, they've had to work around several bugs for a while now.

This release takes care of a few smaller issues relating to imports and import management, and introduces a fixed and enhanced archivist feature. This allows designated archivists to import works for others, adding the author's handle and email address from the original archive. Archivist imports automatically generate an email notification to the author with links to further information and claim/delete/orphan options. This page was also updated in this release.

Better caching!

When a user accesses a work listing, e.g. all works for a particular tag, we cache that list of works and serve it to other users wanting to browse the same list. This means the information doesn't have to be retrieved from the database every single time, which makes for happier servers. However, somewhere in the code we have to make sure the listing is refreshed when anything changes, e.g. a new work with that tag is posted.

Previously, that check was done whenever a listing was accessed. We have a lot more people reading or looking at works than posting or editing, and those turned out to be a lot of checks: Was a new work added to this collection? Did this user delete a work? Was this tag added to an existing work? and so on. In short, the database server wasn't quite as happy as we wanted it to be.

We now update all data ("expire the cache") as soon as a change happens, not when a work listing is assembled. This required extensive changes to many parts of our code, as a lot of user actions affect work listings. All kudos to Elz for persevering through several rounds of testing and fixing all the things!

Known Issues

See our Known Issues page for current issues.

We've been having some server overload issues, detailed in our post, What's up with the recent downtimes? In order to cut down on excessive reindexing, we're currently not adding works to the reindex queue when their hit counts are updated in the database. Instead, the work information is refreshed when some kind of feedback (e.g. comment, kudos) is left or when the work gets a new chapter, forcing an update overall.

Sorting works by hit count will be slightly inaccurate as a result, and will lag considerably for works getting traffic but no kudos/comments/bookmarks/new chapters.

Release Details

Bug fixes

  • Works
    • The cache expiry for work listings was rejiggered to happen when data is updated, not when a listing is accessed.
    • New hits on a work are recorded in the database, but don't make it into the search index currently. Instead, the index gets updated when other work information (new comment, new chapter, etc.) changes.
    • Work drafts (showing author and title information) were visible on the Related Works page; this has now been fixed.
    • There was an issue where kudos left by a guest weren't properly added to the list (thanks to stuck caching) unless a signed-in user left kudos right after. This has been fixed and all kudos should show up in the list at the bottom of the work immediately.
    • We've had reports of blank kudos notifications for a long while, and were never able to hunt down the cause. This release includes a fix of what we now believe is the cause. We'll be monitoring the situation!
    • Marking a work for later *and* marking a work as read would both bring up the same success message. This was changed to properly indicate that the work was added to or removed from your list. Please note that changes will take a while to show up!
  • Work Importing
    • Trying to import a work as an archivist was throwing an error 500; this is now very much fixed.
    • Updated Claim page for newly imported external authors.
    • Fixed several bugs with importing from efiction archives, e.g. an issue with the same chapter being imported over and over again for certain story links.
    • The code for our Redirect Lookup Tool to find imported works on the Archive was refactored and streamlined.
    • Improved URL matching in the Redirect Lookup Tool. Extra bits such as ?mode=reply or #comments and other slight differences in the link (www/no www) are taken into account when looking for the existing import.
  • Automated Testing
    • We continue to work on updating and expanding our automated tests. To this end, we have begun using a code coverage tool called Coveralls.io. You can view the current state of our code coverage by visiting our Github page (look for the little badge in the README section).
    • One of our automated testing tools, called Fakeweb, was outputting deprecation warnings every time we ran our test suite. This was inhibiting easy understanding of the test logs, so we have switched to Typhoeus. We also fixed the causes of other deprecation warnings in the process.
    • At one point, an error 500 was generated when attempting to delete your account and remove yourself as an author from co-authored works at the same time. This was fixed in another release, and we have added automated tests to cover this particular account deletion situation.
  • Misc.
    • Signup summary generation was slow and included a query that was causing issues for the database. We made some changes to help it run more efficiently.
    • Fixed a number of issues with the Rich Text Editor, including non-functioning alignment buttons, problems with the browser spellcheck, missing formatting when pasting from MS Word documents, and others!
    • When toggling between HTML input and Rich Text, the help text "Plain text with limited HTML" would be displayed at all times. It now switches to "Type or paste formatted text" when in Rich Text mode. There is also a new help section for the RTE.
    • In the navigation header, put items under "Browse" and "Search" in the same order (Works, Bookmarks, Tags, Collections/People) for consistency

Comment

Release Notes for Release 0.9.12

Published: 2013-12-21 09:00:28 -0500

Welcome to Release 0.9.12! Cecilia, Elz, Emily E., Enigel, James_, Karangunii, Sarken, Scott, Stephanie, and tuff_ghost, contributed code to this release, which was tested by our awesome testing team: Camilla, Enigel, JanOda, Lady Oscar, MilenaDaniels, mumble, Runt, Sarken, and Sumeria.

This is our last deploy of this year, and we sincerely thank everyone who contributed to this or previous releases, in whatever small or big ways. Every line of code, every minute of testing, every supportive cheer helps this project prosper.

A look back at growth stats for this year will be posted in January, for all fans of hard data and color-coded charts. The Accessibility, Design & Technology team will take a short break over the holidays, but will stand by for any emergencies. We have big plans for 2014 and will share any news with you as we start new adventures. See you next year!

Highlights!

Backend improvements and server work

We've had an interesting couple of months, with growing traffic and increased server load, eventually leading to a collapse of our search index. You can find details about this in our updated news post, Site slowness and other currently known issues. We've been doing a lot of server maintenance in the past few weeks to tweak things, correct some settings, and generally make sure that the site will be running more smoothly. A million thanks to our all-volunteer Systems team, and especially sysadmin James_, for all their hard work! ♥

One issue we've consistently run into is with the code that refreshes the search index for works and bookmarks. This happens, for example, when a tag is edited by our wrangling team to reflect a new tag relationship or a new character name. Since we have a lot of works and bookmarks, updating the index to reflect all changes was taking a lot of time. More often than not, one re-index run wasn't even done when a new one was started.

This deploy includes a code change in how we handle these re-indexing tasks. They are now run by a tool called Resque, which we already use for many other tasks on the site that involve a queue (e.g. all subscription notifications going out at a certain time). This change allows us to monitor the re-indexing process and throw more power at it if necessary.

We are hopeful that this change will alleviate some of our problems during the traffic-heavy holidays, but we will also continue to look into further improvements both in our code as well as our server settings.

Known Issues

See our Known Issues page for current issues.

Release Details

Bug fixes

  • Works & Bookmarks
    • Work and bookmark re-indexing is now being queued and run in the background using Resque, making it more robust and less of a strain on the servers.
    • Backdating wasn't working correctly when posting a work without previewing first. This has now been fixed.
    • Unposted drafts (created when previewing) had no revision date, causing errors in several places on the Archive, such as item management pages for collections. We fixed this recently, and are making the fix permanent now.
    • The "Works (#)" button on user dashboards (below the five most recent works) had accidentally vanished in a previous deploy. We have now restored it and also added "Works (#)" and "Bookmarks (#)" buttons to collection dashboards for consistency.
    • The "↑ Top" button on a work page was forcing a full page refresh; it now just jumps you back to the top of the work as intended.
    • The gifts page now displays gifts a user has received in order from most recent to oldest.
    • Searches with slashes in them (i.e. all relationship tags) were giving Error 500 after a recent Elasticsearch update. We fixed this problem shortly after being alerted to it; this deploy makes the fix permanent.
  • Downloads
    • PDF and MOBI downloads were broken; we quickly fixed them after the last deploy and are making the fix permanent in this one.
    • Trying to download a MOBI file directly from a Kindle device would frequently lead to errors; we have changed the MIME type of our MOBI files so the Kindle browser can handle it correctly. (Due to another issue, multi-chapter works may need to be downloaded twice to get a functioning file.)
  • Tag Wrangling
    • If a tag wrangler ticked the "Turn off emails about comments" option in their account preferences, they would also no longer receive comment notifications from tag discussions. They will now always receive such comments.
    • Updating an unsorted tag from a page other than the first would redirect you back to page 1; this no longer happens.
    • There was a small display issue with autocomplete fields on tag editing pages; this is now fixed.
  • Misc.
    • The account creation page advised newly signed-up users to contact Support if the activation email hadn't arrived within two hours. We adjusted the time to 24 hours to account for clogged mail queues or issues with some email providers, which are delaying email delivery.
    • Our maintenance page (sometimes used for downtime during a deploy) was promising new features after the downtime; this wasn't always true, so we removed the line.
    • On our Invite Requests page, we were only displaying the number of people already in the queue. We have added the number of invites we automatically send out every day, which currently makes for a wait time of 24 hours or less.
    • On our Public Skins page, the skin descriptions were frequently one unbroken line, forcing sideways scrolling. In user inboxes, comments containing long unbroken words were also breaking the page. We have now added a fix that forces linebreaks. (In some browsers the lines won't be wrapped in the inbox; in that case a scrollbar at the bottom of the comment list should make it possible to read anyway.)

Comment


Pages Navigation