E2 Bugs

Gasp. We're not perfect. There are a lot of items that need work, and a lot of different things that are broken in minute ways. They are the growing pains of a publicly developed website. We are in a constant state of beta, but hey, it keeps things exciting. We'd like you to report any problems that you're having, because we, the caretakers and floorwashers, like this to be a generally pleasant experience for you.

Previously we had users report bugs in this document by just adding a writeup. It was simple, it worked fine for the time being. Heck, I'd go so far as to say that it made us happy. It became apparent however, that people were holding separate bug lists, had overlapping task lists, etc, and having simply these tasks were very hard to manage and coordinate.

So now.. we have SourceForge. Thanks captain.

http://www.sourceforge.net/projects/everything2

If you do not have an account on SourceForge, you can sign up for one, and submit the bug. Please don't post completely anonymously (at least include your username) so we can get back to you if we need to get more information. If you are super confused, you can still post here, and someone will merge it over to SourceForge so we can keep an eye on it. Please take a peek at the current list of suggestions, work items and bugs. If it's not on there, or if you have something to add, we'd be happy to hear from you

Things that probably are NOT bugs (eventually there will be a huge separate list):

• One-shot Server Error!s (which really only mean I or someone else forgot a ";" and it took him or her a second to find it)
• The page being slow or not loading for everyone (we'd need to fix that anyways)
• Being logged in as another user (trust me, it's not an E2 bug). This happens a lot in Great Britain. Talk to me if this is the case
• Not being able to stay logged in. It's a common problem that we'll have a documented fix for (delete your Everything2 cookie)
• Not being able to log in (there's usually a reason).
• Oh man, you're right. We spelled sumbit wrong. Thanks....

• Page the error occured on
• A screenshot if it's hard to describe
• A sample page code snapshot
• Your theme (it'll be obvious by above)
• Your browser (not so obvious)
• The time it occured, down to about a half an hour block. We don't need a stopwatch and second, just about when. Grep will do the rest.

Thanks