Archive of Our Own ^beta

Credits

• Coders: Emily E., Lady Oscar, Sarken
• Code reviewers: james_, Sarken, Scott
• Testers: Agwen, Lady Oscar, legalizemavin, LtFoxYee, mumble, nightmarefluff, pendrecarc, Runt, Sara Heins, twofingerpost

Details

Tag Wrangling & Tag Sets

• When a tag wrangler attempted to create a tag containing certain restricted characters (i.e. , ^ * { } = ` \ %), the error message they received was incomplete and confusing due to the way the ^ character is interpreted by our code. We switched to using the numeric character reference for ^ and now a full, clear error message will be given.
• When a user attempted to nominate a tag or create a tag set using restricted characters (e.g. giving it a title with * or ^ in it), the error message they received was similarly incomplete. These issues have been fixed as well!
• The Wrangling Tools page (visible to logged-in wranglers) previously contained only a few links to the Wrangling Guidelines and the OTW-internal wiki. Now it includes a more detailed set of links to various pages of documentation and updated contact information for the committee staff.

Importing

• Attempting to import a work from a LiveJournal community or journal marked as containing adult content would instead import the contents of LiveJournal's support page. We adjusted the importing code so it will bypass the adult content warning and import the work itself.
• The "Post New Work Instead?" link on the import page was only reloading the import page. Now it will take you to the page for posting a new work.

External Works

• When a user bookmarks an external work, they are asked to provide information about that work based on the work's headers. However, the field for providing the work's category (i.e. F/F, F/M, Gen, M/M, Multi, or Other) was presented as a dropdown menu, which would only let the user choose one category tag. The options are now presented as checkboxes, so the user can select all categories that apply.
• Admins were unable to access the form for editing external work information due to a conflict with the "Hide my work from search engines when possible" preference. We've fixed the conflict so admins can access the page once again.

Stats

• The "Totals" section on a user's Statistics page lists how many users are subscribed to them as a work creator. It was previously labeled "Author Subscriptions," but because we have more than written works on the Archive, we changed it to "User Subscriptions."
• A work posted on or backdated to 31 December would not be included in the user's statistics for that year (or any other year). Now it will be listed in the correct year and any word counts, kudos, comments, hits, or subscriptions for that work will also be included in that year's totals.

Misc.

• In work blurbs, the first tag in a line of text was aligned differently based on whether it started on that line of text or had wrapped from the previous line. Now the tags will always align the same, creating a tidier margin on the left side of the tag section of the blurb.
• If a form's HTML provides certain information, most browsers will place keyboard focus on an input (e.g. a checkbox or text field) when a user interacts with its label. To improve usability and accessibility, we've added that information to the form on the reset password page, so the field will correctly receive focus.
• We recently changed the code for the pop-up search suggestions in the header (e.g. tip: lex m/m (mature OR explicit)) on most site pages. However, because our error pages use different code than the rest of the site, the search tip was always displaying there, not just when using the search field. The error pages have been updated and will now work the same as all other pages.
• The chapter number at the top of a chapter was supposed to be a link in Chapter-by-Chapter mode and plain text in Entire Work mode, but caching would sometimes result in the the wrong format being used in a given mode. Now the chapter number will always be a link, regardless of which mode is in use.

Known Issues

See our Known Issues page for current issues.