DemonGoddess

While I've not experienced this aspect of life for myself, my hubby has with both his mother and brother. Mostly his brother. Yes, it is horribly stressful for any of you who have to experience this. There were many, many things I overlooked BECAUSE of the stress he was dealing with at the time. After all, his first and only priority at that time should have been his ailing family members. When he felt guilty about it, mini and I reminded him to not, because it's not like any of them asked for this. His brother didn't ask for cancer, and his mother didn't ask for leukemia. To ease his mother's burdens, he took on all the care of his brother. You're right. It's a thankless job. Know that the person you're caring for, though, even if he or she doesn't mention it, DOES appreciate it.

I have no way of verifying what the actual hit count was for the story, which is why I came up with the method above.

regal renege rambunctious rules

Here's how I'm fixing this: I look up your stories in the subdomain in question. I compare dates, and take the adjustment from the stories in the date range of publication.

We're trying to NOT go in to the old code at all for any tweaks. Chances are high it'll cause big issues.

Well, just my two cents, but if the author stated it was going to be published, it's LIKELY the author removed it before hand because of that.

@24CaratCoal Thank you! I've got some things I'll be covering in a news post on Sunday, related to the upgrade and further tasks, and how they're going to affect users.

With the ratings being disabled, it doesn't matter at this point, really. Plus, there are other things I'll go in to about the ratings and how they'll come back, in the upcoming news post.

The most common reason I've seen for downvoting is that the person who does this doesn't like a pair written about in the fandom.

yep, I adjusted it according to other popular stories in your category, published in the same time range.

You may just need to refresh your bookmarks. Story update date/time has been added to current reading list too, by the way.

We've seen that with a few, and that had to do with the rewrite of the hit counter itself. Why it only affected some stories, but not the bulk of them, I'm not sure.

We're actually looking in to a full text chapter search, but if it bogs things down too much, that's not likely; as far as internal search engine. Yes, I've added things to the indexes for google and whatnot to allow for chapter text searching. Did that a couple years ago.

Okay, moved to the correct forum, for starters. Secondly, it appears the author has removed them from the web.

No, it won't be anonymous. I'll actually be able to track back malicious downrating. It'll be awhile before it returns, it requires a complete rewrite of the function, as well as additional tables.

aw jeez, that's the old one In any case, you need to activate. Instructions sent.

You're welcome!

@24Carat, yes, your email can be changed. Email me at technical_support@adult-fanfiction.org with your updated information. As to the tags, they are going to be a set of tables, and selectable. Not input on the fly though. That'll make it much harder to set up filters and for searching, and be sluggish as well.

Tags will be rewritten as far as how they work, entirely. This is going to require the creation of additional tables for the tags, and a subroutine to add then and whatnot. Not sure yet how exactly this will work in search, unless we're looking at filtering using the tag field. I'll ask on that.

thank you!

I'm not sure, unless it was converted with the new hit counter? I'll look in to it though.

Actually glad you pointed out that error, as the function referenced no longer exists, so the string is now corrected so it no longer calls for a non existent function. As we're making things more centralized to run GLOBALLY across the domain, the only title you'll see is the subdomain (archive) title.

And once again I'll address this. The goal with the code is to make as much of it execute from one area, as we can. This means we're not running 23 different instances of the same script copied locally to the subdomains to open a story anymore, in different subdomains. We're using ONE script, in ONE subdomain to open stories EVERYWHERE.

And again, I say not broken, but CHANGED. That isn't broken at all. That means we CHANGED it. The end goal for the scripting is to make as much of it run GLOBALLY from one spot, than from 23 different spots.

Blue_GhostGhost is actually being published in a few places. She still has completed works up on this site, but her newer stuff she's got Patreon links and the like, where you pay to read. Good for her! Glad she's making a success of it.