DemonGoddess

Well yes, we moderate, but we don't QC. As I said, sure it would be nice to be able to offer that to our authors in original. But with the fanfiction being hosted as well, we can't.

@Joe Long We've had the suggestion here, as well, to offer subscriptions for pay for original, but that's a big problem for us. Hosting fanfiction means that we cannot in any way, shape or form, make money from people clicking in to read a story via a subscription. So, that would be why you'd never see AFF turning in to any kind of a pay site.

Here's what's going on for the coding to display it. Manta has run in to a bit of a looping issue. I expect she'll have that worked out this weekend (I'll double check on that though). I could theoretically insert the OLD code to display the hit counter, but we'd end up back with the white screen of death, as THAT code is certainly not compatible to php 5.x. I can't help with the looping issue, because when I write code on my own, I have a penchant for making the endless loop from hell. So, my input would only make it worse on that end. So, it's safer to just wait for Manta.

found and fixed. I was unable to replicate it, which tells me the cookies were working from prior to the upgrade. I know I've not cleared mine, so that would be why I didn't see it myself when clicking. There are 3 spots in the age cookie setter to direct to the subdomain it's in. Apparently there was ONE spot where the link went to anime2 instead of anime, but I've corrected it now, so should no longer be an issue.

Yeah, we are. Thanks for asking!

sounds to me like you need to clear your browser cookies.

That member was deleted at some point. That's why you're seeing the white page in the old author page format.

yep, they're accumulating in the db. Just not visibly. She said something about working on it after work today.

Not sure, really. Right now, we just want the code to parse 15 years of data. Refining things with search filters is something I expect we'll tackle much later.

That's planned for later, yes.

Just tried and went straight to anime, not anime2

Sure, this FAQ tells you how

@24CaratCoal The banner ads have not changed in size. They're still 468x60. If you meant the area in which they're displayed, I could always reduce the physical size of the table, to make it so it's more mobile/touch screen compatible. The table size has also not changed. You're right, on a desktop, this is not an issue. @sherlocked17 No, the hits are still accumulating. The DISPLAY of them relies on old code database calls which will kill things, which is why the display of them in new code is not yet restored. You can see them in the general story listings.

as far as I'm concerned, downrating out of spite is troll behavior

Nope, not miffed. I am a terse sort of person when I communicate. Especially when I'm in the middle of things. What I would LIKE to see with ratings (and I'll go over this with manta) is that who rated how is not necessarily visible, except to staff. Reason for that being when there are stories with 4 and 5 ratings all of sudden getting downrated to 1 and 2? It's a spite thing. I need to be able to find the ones doing it. This would also require login for rating, and it would no longer be truly anonymous. By doing this, it'll kill instances where this is used to abuse authors for no apparent reason. (The reason is almost ALWAYS a disliked pair)

I'm not saying the ratings won't come back. What I AM saying is that they should not come back in their current form. It's been used to abuse authors far too many times over the years.

Rating has not been restored as of yet. Given that people used this as a tool to harass authors who write pairings in some fandoms that they don't like, and downrate it out of spite, I'm pondering never having it return. At least not in its old form of being completely anonymous. I'd like to be able to track that form of trolling, the downrating.

Yup! Manta did a terrific job, as usual!

Reviews are once again enabled, pagination is changed to give next/back arrows now.

I actually use the browser increase/decrease myself.

Your continued patience is helpful! A quick fix for the reviews and nav I was pondering absolutely wasn't going to work. This is why I check before trying it.

No, this is temporary, and has to do with having to rewrite parts of the code quickly to make it so the chapter data showed.

Firstly, I'd like to welcome all the new users we're seeing daily! Glad to have you here! Please do familiarize yourself with the Terms of Service and Content Guidelines. This IS a moderated archive. Server Upgrade Update There are some issues, which I'm sure you'll have noticed. First of all, when we attempted to upgrade one of the core languages a little bit more (after prepping the site files for it), it made visible some big issues that were already there with upgrading php from 5.1 to 5.3. When we went to 5.4, and then reverted back, the issues that were there stayed there and visible. So,this meant a complete rewrite of the file which shows the chapter data itself. Between Manta2g and myself, that was 30 hours combined, on the 12th. Just to get that part working again. In the process of doing that, there were some things we've not added back yet. This is TEMPORARY. Will be working on restoring: “next” at bottom of chapter chapter numbering hits (these still show in the story listings in the archive, going to see about it in other places) review ability Understand that with the code stuff, I defer to Manta in this (just as she does with me for the database). I will certainly give it my best effort, but any changes I make will not go live until she's had a chance to go over them. We don't want to break things all over again. Odd characters, (diamonds instead of apostrophes as an example) are the result of the database having been changed to utf8 encoding when mysql was updated as part of the server upgrade. Utf8 is the default for later versions of mysql. For the moment, in your browser settings, change the encoding of the page to utf8 from whatever your browser has defaulted to. To completely fix this I have to do a couple things. First, anywhere any header commands reference charset, I'll change that for utf8. Secondly, I have to convert the data from what was default before (latin1) TO utf8. As the database is 9.3GB, this is going to be time consuming. Further, I have to be very, very careful in that I don't scramble anything when I do this. I'll be doing the conversion table by table. Thank you for your continuing patience! Please remember that the authors you read do like to hear from you! Leave them a review or two, and let them know how they're doing! (yes I know, I'll get this fixed first) DemonGoddess061

@HP_Reader, The chapters you mention in the first story, display correctly. The second story also loads, but with the diamonds. As I said, to fix that temporarily, set your browser to utf8. As the database is 9.3GB, the conversion is going to take me some time. So rather than wait, I'd go ahead and set that in your browser. In the meantime, I'll also set the charset where it asks for it in the file itself in header information. That'll help somewhat, but won't correct it entirely.