AO3 News

Release Notes 0.9.36: Change Log

Published: 2014-12-14 03:41:24 -0500

Credits

  • Coders: Ariana, james_, Sarken
  • Code reviewers: Elz, james_, Lady Oscar, Sarken
  • Testers: Anika Kabit, Lady Oscar, legalizemavin, mumble, Priscilla del Cima, Runt

Details

  • When a user attempted to change their username to one that was less than three characters or more than forty, the error message they received would tell them which characters are allowed in user names. Now it will tell them how long a username must be.
  • A user who had archivist privileges and wanted to import their own works from another site would receive an error message incorrectly preventing them from importing their work. They will no longer receive this error message, allowing them to import their works.
  • The admin interface for creating translations of news posts had a dropdown menu that let translators choose which of the recent posts the translation corresponded to. However, our translators are awesome and want to translate some older news posts, so we changed from a dropdown menu with a limited number of posts to an autocomplete that will let them choose any news post they like.
  • In our previous release, we tidied up the margins on tags in work blurbs, but we also introduced a bug that moved the tags closer together. We've fixed the typo that caused the problem and tags are properly spaced out once again.
  • We made some minor improvements to the code used for manual imports, in particular to turn names listed on a line starting with "Characters:" into tags where possible.
  • When a logged out user tried to access an FAQ using an old URL (e.g. one ending with archive_faqs/30), they would get a 404 error telling them the page could not be found. Now they should be redirected to the new URL (e.g. one ending in /faq/ao3-internal-tools?language_id=en) just like logged in users are.
  • In works and site documentation, <h4> headings were hard to distinguish from the main text. Now text in <h4> tags will be bold to make it stand out more.

Known Issues

See our Known Issues page for current issues.

Comment

Release 0.9.35: Change Log

Published: 2014-12-02 15:25:44 -0500

Credits

  • Coders: Emily E., Lady Oscar, Sarken
  • Code reviewers: james_, Sarken, Scott
  • Testers: Agwen, 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.

Comment

Release Notes 0.9.34: Change Log

Published: 2014-11-18 21:44:48 -0500

Credits

  • Coders: Lady Oscar, Sam Johnsson, sarken
  • Code reviewers: Enigel, james_
  • Testers: Anika Kabit, Lady Oscar, Runt, sarken

Details

  • Misc.
    • Previously, if the original version of an AO3 News post was accidentally designated as being a translation, it couldn't be set back, creating a situation in which the post would permanently vanish from the main feed. It's now possible to restore the setting.
    • On the External Bookmark page, required fields were not correctly marked as being required. All required fields are now denoted with an asterisk (*) and error messages have been updated to be inclusive of non-text fanworks.
    • We have added a link to the Troubleshooting: Common Problems When Logging In News Post from the error message that is generated upon a failed login attempt.
    • We have reduced the number of emails sent out during the AO3 signup process. After signing up, users will still receive an email with an activation link, but will not receive a success email after activating the account, as this email contained no new information.
  • Skins
    • While using the 'Reversi' Skin, it was previously impossible to read the 'You have already left kudos' message. This has been fixed.
    • We have also edited Reversi to make it easier to read the tooltip information displayed when viewing Tag Set nominations.
    • We have added a '.book' style to the Basic Formatting workskin. This style will indent the first line of each paragraph and remove the blank lines between paragraphs to give an appearance similar to the text in a standard printed book. You can read more about Work Skins in our Work Skins Tutorial.

Known Issues

See our Known Issues page for current issues.

Comment

Release 0.9.33: Change Log

Published: 2014-11-02 09:39:14 -0500

Credits

  • Coders: Emily, Enigel, james_, sarken
  • Code reviewers: Ariana, Enigel, james_, Scott
  • Testers: Lady Oscar, mumble, Runt, Scott

Details

  • The option to remove requests or offers while filling in a challenge sign-up wasn't working when there were required tag fields on the sign-up form. Now it works again.
  • There was some old bookmark code hanging around, not doing anything. Now it's gone.
  • The "Bookmark External Work" button was available to visitors on the bookmark listings for tags. Only logged-in users can create bookmarks, so we removed the button.
  • When browsing your subscriptions page on mobile devices with small screens, the links for accessing only series, user, or work subscriptions weren't working when tapped. Now they work.
  • The little tooltip pop-up for the header's search field (suggesting possible keywords and sort options) only worked for users navigating by mouse or trackpad. Now it will work for people using keyboards, screen readers, or touch screens as well. Additionally, now it only appears when the search field is selected, rather than popping up whenever the cursor is nearby.
  • We used an HTML attribute to label many things in various listings on the site -- for example, the titles of works. Unfortunately, some screen readers read the content of this attribute instead of the actual text, which made it sound like every work on the Archive was named "Title." We've removed this attribute from everywhere it could impact screenreaders in this way.
  • When an admin went to a user's dashboard, any restricted works the user had posted were hidden from the admin. Now the admin can access those works from the user's dashboard, just like regular logged-in users can.
  • We moved to an even stronger encryption method for safely storing passwords.
  • Previewing a work for the first time automatically creates a draft. However, subsequent previews don't update that draft unless the user explicitly chooses "Save Without Posting". We removed the message that implied otherwise. Remember, don't use our posting form as your only writing tool! Browsers can crash, things can go wrong, your draft might get eaten. Always have a backup somewhere else.
  • We considerably spruced up the README file used for displaying information about the AO3 software project on GitHub.com.

Known Issues

See our Known Issues page for current issues.

Comment

Releases 0.9.30 - 0.9.32: Change Log

Published: 2014-10-29 15:56:11 -0400

Credits

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

Details

  • There was a "Bookmark" button on user dashboards, implying that you could bookmark another user, although no such functionality exists yet. We have removed the button and the "Coming soon!" page for now.
  • The log of admin activities (used primarily by Abuse personnel) was returning errors if a page contained an admin account that had been deleted. It now displays the activity with an "Admin deleted" note.
  • The log also wasn't accessible from the main Admin menu. Now it is!
  • We deployed a temporary donation page (put together by Development & Membership staffer Kristen!) for our October Drive, and made some edits halfway through the Drive week. Thank you all so much for your donations!
  • Relatedly, we reached our goal for the Drive after only two days and had to make some on-the-spot edits to our "progress bar" code to allow for stretch goals. Next year we'll be better prepared!

Known Issues

See our Known Issues page for current issues.

Comment

Releases 0.9.27 - 0.9.29: Change Log

Published: 2014-10-10 18:49:41 -0400

Credits

  • Coders: james_, sarken
  • Code reviewers: Ariana, Enigel, james_, Scott
  • Testers: Lady Oscar, mumble, Runt

Details

  • Challenge sign-up forms used checkboxes instead of autocomplete unless there were more than 500 tag options for a given field (e.g. fandom). That many checkboxes was not user-friendly. Now it will switch to autocomplete when there are more than 20 tags.
  • Fixed a broken link on our site map.
  • Removed parts of the AO3 admin interface which were no longer required.
  • Fixed a bug that would prevent admins from accessing comments left on restricted (locked to AO3 users) works.
  • In the most recent version of Safari (7.1), the comment field would jump around when clicking into and out of it. This has been fixed!
  • In preparation for our Membership Drive, we added a new feature to the site-wide banners used for such occasions.

Known Issues

See our Known Issues page for current issues.

Comment

Release 0.9.26: Change Log

Published: 2014-10-06 17:35:19 -0400

Credits

  • Coders: Emily E, james_, Lady Oscar
  • Code reviewers: Ariana, Elz, james_
  • Testers: Lady Oscar, mumble, Scott

Details

  • The Locales page now lists all locales that the Archive supports. (What's a locale?) Users can now suggest new locales, and Admins can edit or add existing locales from this page.
  • Previously when following incorrect links to AO3 News posts, pseuds, works, or tags, the Archive would redirect you to the next best page, e.g. the main works index, and display a brief message. Instead of redirecting, we now show an Error 404 page. This preserves the address (work, tag, etc.) you were trying to reach in the address bar, allowing you to fix a typo and try again, for example.
  • If for some reason your browser cookies for the AO3 get deleted or corrupted, you will be automatically logged out of the Archive and shown a page informing you of the action. (See our post, https://archiveofourown.org/admin_posts/1277, for tips and tricks on dealing with log-in problems.)
  • We fixed and updated a number of our automated tests (which ensure that the Archive will still work as expected when we change or update code).
  • We also added and improved automated tests that cover administrative actions (such as posting a new AO3 News post, or managing invitations), moving us closer to 100% code coverage of those features!
  • The Technical Support and Feedback form has been updated to correctly list all the languages Support can answer questions in. The new ones are: català, čeština, magyar, and Русский.
  • We have updated a section of the Archive TOS FAQs. The final sentence of the "Can I archive original fiction" question has been changed to: "We presume that, by posting the work to the Archive, the creator is making a statement that they believe it's a fanwork. As such, unless the work doesn't meet some other criterion, it will be allowed to remain.". Previously, the final sentence read: "In general, when there is doubt as to whether a particular work counts as a fanwork, we will trust the judgment of the work's creator."

Known Issues

See our Known Issues page for current issues.

Comment

Release 0.9.24: New FAQ code!

Published: 2014-09-29 17:06:34 -0400

Credits

  • Coders: Elz, james_, Sarken, Scott
  • Code reviewers: Elz, Enigel, James
  • Testers: Camilla M, helebr, Lady Oscar, Mei, mumble, Priscilla, Ridicully

Extra special thanks to Scott for helming this project through sunshine and rain! ♥

Details

This code update includes many improvements to the Archive FAQ, our help section for new and experienced users alike. This part of the site grows and changes with the Archive, and will see even more improvements in future updates. For now, we offer these new features for your enjoyment:

  • You can now browse our FAQs in languages other than English! Since both the FAQs and their translations are a work in progress, only a few categories have translations right now. We'll be adding more during the coming months, and will update outdated information across all sections.
  • As soon as at least one FAQ category (e.g. Pseuds, Bookmarks, Comments, etc.) is available in a language, that language will show up in the dropdown menu at the top right of the main FAQ index. Only translated categories will be listed, so if you can't find the information you're looking for, please refer back to the English index. (Work in progress!)
  • There are now buttons on the main index to show all available questions ("Expand Categories") and to hide them all again ("Collapse Categories"), so you can skim the page or search for exactly the information you're interested in.
  • At the top of each category, you'll find a list of available questions, so you can quickly jump to just the answer you need.
  • The system now allows for direct links to each question/answer pair on a page (e.g. How do I subscribe to a work?), which wasn't fully supported before.
  • The new FAQs have "pretty" URLs, which means they don't just contain the id of the FAQ category (as in, /archive_faqs/17), but rather the title of the page (as in, /faq/orphaning).
  • Contrary to expectations in our original announcement, there will be no broken links. Old links (e.g. archiveofourown.org/archive_faqs/7) will automatically redirect to the new pages (e.g. Pseuds).
  • Our public wrangling guidelines, which were previously (and somewhat awkwardly) part of the FAQ section, have gotten their own home! You can consult these pages when in doubt about how to best format a new tag, or if you're wondering about specific wrangling concepts and policies.

Extra Credits

Our AO3 Documentation volunteers are working very hard to update the old, sometimes very outdated FAQs, and our many translators are working on translating them: either the new and improved documentation or, in some cases (when we have the volunteer power), some old documentation that might still be helpful, while waiting for it to be updated.

  • Documentation writers: AnneVictoire, C-chan, DekuDani, ltfoxyee, MadameHardy, Sammie, trickybonmot and 12 AO3 Documentation volunteers
  • Translators: Agnieszka Górniok, Amalia Blondet, ambersnake, Ana Carolina Nonato, Ana Solis, Aneta Sikora, Ania Kopertowska, Anne-Katrin Koch, Arithanas, Artmetica, balistener, birggitt, Blacktablet, Charlotte, ChristyCorr, Daniela Kreimerman, DeeCharlotte, Eilean, Eimry, Ely_Baby, Elysandra, Fatma Bahr, fluffygreenpillow, Gloria Monika (Rizu), Hayyu A (Alinka), headinthecloudsgirl, Jocelin Potash, John (rcmero), Karagodina Elena, Kaysa (Sarah K.), Konomon Freezlight, LilyC, Liselot, Luisa, M.Rios, Meep, MrBalkanophile, Nana, Nerine Luna, regenorakel, Ridicully, rocksound, soniclipstick (veriscence), SunnyB, Tatanka, tamat9, White Hawk, Yenelie, and 76 translators

Known Issues

When you pick a language from the dropdown menu to access available FAQs in your language, for example Spanish, the language information will be included in the URL, like faq/about?language_id=es. When you leave the FAQ section, e.g. by selecting the All Fandoms link in the header menu, this language information will follow you to that page. Since so far only the FAQ section is translated, however, there will be no other effect. When you continue browsing, the next page you visit will have the normal URL again.

See our Known Issues page for other current issues.

Comment


Pages Navigation