Updated 2016-02-26 08:41:46 -0500
These are the major Known Issues that are currently affecting us on the Archive of Our Own. If you've encountered an issue you don't see here, or you'd like to give us more information or comments, we welcome your feedback via the Support and Feedback form.
The Archive is still a work-in-progress, and we'll be introducing a whole bunch of new features in the future. Since the Archive is designed, coded and tested by volunteers, the time it takes to introduce new features varies a lot, but we do listen to your requests and feedback and work to respond to it. If you are interested in helping us turn ideas into a reality, please volunteer to join the Archive team via the OTW's Volunteers page.
- Current Issues
- Posting Works
- Importing Works
- Collections and Challenges
- Navigating the Site
- Specific Browser Issues
- Sorting bookmarks by "Date Updated" doesn't work correctly: Due to issues with our search index, sort results will currently appear a little jumbled. If you want to follow a work in progress, please consider subscribing to automatically receive an email when a new chapter is added.
- Sorting works by Hits returns inaccurate listings: As of Release 0.9.13, new hits on a work are recorded in the database, but don't make it into the search index right away. The index gets updated only when other work information (new comment, new chapter, etc.) changes. The hit count will be correct in the work blurb, but sorting will be off for some works.
Rich Text Editor
Formatting lost when pasting from some word processors or editors: The Rich Text Editor (RTE) is an external component provided by TinyMCE. We most recently upgraded it in Release 0.9.13, which fixed several lingering bugs affecting our users. Unfortunately, issues remain when pasting from some editing programs. The wide variety of possible combinations available across all operating systems, word processors and Internet browsers makes it impossible to test all permutations, but here are some known problems we are already aware of:
- Microsoft Edge: The current version of the RTE appears to strip all formatting and line breaks when text is pasted in using Microsoft Edge, regardless of word processor. At this time, if you need to use the Rich Text Editor, our only suggestion is to use a different browser, such as Google Chrome or Mozilla Firefox.
- Google Drive: The way that Drive encodes styles differs from most traditional word processors, resulting in all character formatting and alignment being stripped out when pasting into the RTE.
- Microsoft Word: While left, right and centered alignment are preserved when pasting from modern versions of Word, justified alignment will not work. Please also note that first-line indents are never preserved. There is also an issue with paragraphs consisting only of a single word followed by a period (e.g., "Stop.") being stripped out when pasting from Word. If your work has such paragraphs, a work-around is to remove the period, paste the text, then re-add the period.
- Rich Text Editor suddenly stopped working: Some Windows users are running into a new problem with line breaks being lost when pasting into the RTE. Using "Paste" from the browser Edit menu or the right-click popup menu with some combinations of browser and word processor results in a wall of text with this version of the RTE. You should be able to retain formatting by using the keyboard shortcuts "ctrl-C" and "ctrl-V" to copy and paste your text. Alternately, Chrome seems to work regardless of the paste method.
- Can't add chapter notes and summary for first chapter: The boxes to enter a summary and beginning and/or end notes for chapter 1 won't appear until chapter 2 is posted. (The summary and notes boxes on the work posting form are for the entire work. In particular this means that any end notes entered here will be work end notes, attached to the end of the last chapter of the work.)
Editing Work Data
- Series order not updated: When the order of the works in a series is changed, this change is not properly reflected in either the work blurb or the summary at the top of the work. Clicking on the series title will show the series in its proper order, but the works will be labeled with the wrong part numbers. The series information at the bottom of the work text is updated correctly. This problem does not seem to resolve itself with time, but it's been reported to our coders to work on a fix.
- Adding an anonymous work to a new series will break anonymity: If your work is part of a collection or challenge that is currently set to anonymous and you add the work to a series, the series will show up on your 'Works in Collections' page, leading to the blurb containing all information for your work, but with "Anonymous" set as the author. It will still display as a Mystery Work at the top of your home page and on your work listing.
- Pasting with quote marks: Several versions of the major browsers are inconsistently converting regular quote marks to angled smart quotes when pasting in HTML code - for example, embed code - with attributes enclosed in quotes. These smart quotes in the HTML code will be stripped out by the parser, rendering the code unusable and causing the entire embed to be stripped out. You'll need to manually go through the pasted code and replace the “smart” angled quotes with "straight" double quotes. Unfortunately, we can't give reliable browser recommendations here, as this behaviour seems to vary for browser versions on different platforms.
- Can't embed audio files using Google's Flash player: Google has disabled the Flash file many sites were using for embedding mp3s. If you used Google's player to post podfic to the Archive, the streaming interface won't be available. Instead, we have made available the open source player Dewplayer for embedding audio files in your work. Please see our post Just Press Play! (Podfic Embedding on the AO3) for more information.
- Tags are not case-sensitive: You may find that when you enter a tag, it defaults to the capitalisation which already exists in the database, which may be different from the one you entered. If you think a canonical tag is wrongly capitalised you can submit a Support request and our tag wranglers will look into changing it (subject to wrangling guidelines).
- Tags with diacritics: Tags with diacritics (accented letters such as à or š) are currently not recognized as separate from spelling variants with non-accented letters. If necessary, wranglers can disambiguate problematic tags (where accented and non-accented versions actually mean different things), so if anything seems wrong to you, please contact Support to let us know.
Emoji and Emoticons
- Text-based emoticons in the HTML editor: Emoticons starting with < will confuse the HTML parser - it sees that as HTML code and assumes the rest of the work is a badly-formed HTML tag, removing it. You can work around this by manually entering the HTML for the left bracket (<) or by entering the emoticon using the Rich Text Editor.
- Emoji and Extended unicode on the Archive: Due to interactions between the database software and the code framework we use, the Archive does not support any Unicode characters past ✏ (U#9999 U+270F). This includes some language scripts and many common emoji. Our coders are aware of the issue, but we do not have a workaround at this time.
- Imports from FF.net: Imports of works hosted on fanfiction.net are currently not supported, as the Archive has been blocked from accessing their site - see this post on FF.net problems for more information.
- Imports from other sites: due to issues with the page layout, our parser is unable to interpret the content on pages from several other sites, including tumblr.com, Quotev.com, Adultfanfiction.net, and Wattpad.com, as well as files publicly shared at Google Drive/Google Docs, Word Online, and DropBox. This causes the import to immediately fail and generate an "error 500". Our best suggestion is to copy the content directly from the page and paste it into the Rich Text editor.
- Imports from sites with Age Verification confirmations: the Archive import code is not able to bypass most sites' age verification pages (it is only six, after all). It will return the age verification as content or the import will fail. To import from a site such as Livejournal or Dreamwidth that has an age verification page or pop-up, you will need to temporarily mark your content on the original site in a way that disables the age verification.
- Imported works post without preview: Importing multiple works in one go results in them being posted immediately instead of being previewed first. This is a bug and will be fixed in the future. You can work around this for now by importing works one by one.
- Multichapter importing: Currently, if you import a multichapter work (either from a single URL, or using multiple URLs and choosing to import as chapters of a single work) only the first chapter is viewable/editable before posting. Additionally, choosing to Edit before posting will cause your work to appear with two copies of chapter 1 and no chapter 2. You can avoid this problem by choosing either "Post" to post directly or "Save Work Draft" to save the work to your Drafts (so you can edit it before posting).
- Can't add someone else's work to my collection: It is currently possible to add your own work to a collection, but not to invite someone else's work. This isn't a bug - we just haven't built the feature yet. Please bear with us while we finish and roll out the necessary code. In the meantime, you can work around this by commenting on people's stories and inviting them to add themselves to your collection.
- I still have the option to submit a work to a finished challenge: At the moment, the dates functionality on the challenge settings page is for information only. If you're the owner of a challenge, you have to manually close the challenge at the finishing date.
- Signup Summary ignores Optional Tags: Fandoms entered in the "Optional Tags" box of Gift Exchanges (for example, "bucket list" offers) are not factored in when the Signup Summary page is created. Fandoms that have only been requested in this way will not appear in the Signup Summary at all.
- Problems with .mobi files: We are experiencing problems with the conversion tool we use to generate .mobi files from HTML, such as random characters appearing in place of spaces. In particular, the Â character will be inserted wherever the author left a double-space in their text, e.g. after a period or a closing HTML tag. We apologize for messy files and will look into better conversion options. In the meantime, you can try one of the other download formats that might be compatible with your device.
- EPUBS missing chapter end notes: EPUB downloads of works with chapter end notes will be missing those notes. Until we can find a better conversion solution, the best work-around is to download the work in a different format and then use a program such as Calibre to convert it to EPUB.
- Incorrectly transliterated file names: As of Release 0.9.53, our 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!
- Notifications about related works don’t go out if the work is posted without preview: If you are creating a new work with "This work is a remix, a translation, or was inspired by another work" ticked, choosing to preview at least once before posting will ensure a notification is sent to the author of the inspiring work.
- Edits to an already posted work don't trigger certain notifications to be sent: Notifications about related works/series subscription emails will currently not be sent if a remix or translation link/series name is added to a work after it's already been posted. You can monitor the numbers for Related Works in your Dashboard sidebar, and check series subscriptions manually if you are unsure. We are working on a fix!
- Not getting any emails: We've been getting reports about missing subscription notifications even when we couldn't see any problems with the mailing queue on our end. In all likelihood, these emails are getting caught in spam filters. Please check your junk mail folder and add email@example.com to your address book to increase chances of successful delivery. You can also follow these unofficial instructions for whitelisting all emails from the Archive.
- Hit counter doesn't respect settings: We've had user reports of hit counters showing up even though the user had selected not to see them. We're looking into possible reasons, such as caching weirdness.
- Commenting: Occasionally after commenting or leaving kudos on a chapter users will be booted back to the first chapter or full work, depending on the preferences set.
- Slow "Mark as read" update: Clicking the "Mark for later" button on top of a work will result in a success message, although you might have to wait a while until the work shows up in your history and the button changes into the "Mark as read" button at the bottom. Please keep in mind that due to caching, you might also need to wait up to ten minutes to see it vanish from your History > Marked for Later list once you've marked it as read.
- Share box always open: Some third-party browser userscripts cause the 'Share' button that usually pops up a pre-formatted block of work information to be replaced by the text it's supposed to hold. This is due to a conflict between the userscript and the jQuery plugin we use for our help boxes. The quick and dirty way of solving this problem is to disable AO3-related userscripts. For more information, see our Known Issues from Release 0.9.6.
- As noted above, the Rich Text Editor does not paste in any formatting, including line breaks.
- Testing is still ongoing for this browser. If you find any issues not listed here or above, please submit a Support ticket.
- Tags in the work blurb: The commas separating tags are not showing up in older versions of IE.
- Replying to comments: Some people are reporting problems replying to comments in IE. If you run into this issue, consider contacting us with the steps you were taking, so we can try and reproduce this bug.
- Internet Explorer 6, 7, and 8: We realize that some of our users are forced to use older versions of IE and are doing our best to make the site as functional as possible for them. However, some portions of the site will look broken or behave erratically. If you can, please upgrade to a newer version of Internet Explorer, or use a different browser.
- Tag feeds displaying as code: Clicking the "Subscribe to the feed" link on fandom/relationship/character tag pages will open a page of raw code instead of letting you choose a feed reader to subscribe with. This is a problem with Chrome and not something we can fix on our end. Please consider installing an extension such as RSS Subscription or Feedly, or using a different browser to subscribe to tags.
- Problems with the help boxes: The iBox pop-ups we use for our help content don't display well in mobile Safari, and other mobile browsers. We've been looking into fixes, but might have to change the way to display help content entirely to accommodate mobile devices. Please bear with us in the meantime. As a workaround, you can tap and hold on the question mark symbols to open these links in a background tab.