DemonGoddess

Okay, putting up a schedule for the next time. I'll be setting the archive portion of the site to read only access at approximately 5 pm on Wednesday, February 10. I'll have it set back to normal access by 10 pm of the same day. Times are EST. The table sets and associated subcategories I'll be working in: bleach books buffy cartoon celeb comics ff When I get to the final phase, where the conversion has been checked and I'm ready to switch tables, I do delete the old table and rename the new converted ones. This takes approximately 3 to 5 minutes altogether, where you won't see any data AT ALL in the subdomain where I'm doing this. In other words, all blank pages, not the white page of doom, but there is no data to draw FROM while I do this last part. If you do see that, be patient, it'll be back up within a few minutes. Each table set takes a minimum of 45 minutes to convert and then check, so I might not get all the ones listed above done. Of course, the 45 minutes is based on the last set of tables I did, where I ran in to issues and had to come up with fixes. So, it could very well take less time this time around. I won't know until I actually do it. Now that I know for certain the oddball side effects that this conversion causes, I also know what to do to fix it all before I even make the tables live. That will certainly speed it up.

Chapter nav is to the left, in order. So, if you bookmark on chapter 30, and go back to read, edit your bookmark to reflect the latest chapter you stopped at.

Personally, I think the cat pokes are funny. That's the whole POINT of them though, really. To be funny.

To do what you want with the title in the browser bar would mean taking a step back and decentralizing the code. We're working on getting AWAY from that.

It's definitely possible, it's just a color setting in the stylesheet for that division. As I said, there are definite tweaks to be made on that end. But, right now, the code and whether or not it works, and the database and whether or not it's stable, are the priorities. Function first!

First of all, the colors can be adjusted in the style sheet. I expect there will be further tweaking of it. As to the ratings, while we'd like to maintain them, it's not possible. Still looking at ways to get the aggregate exported and then imported in to a new table though. Just saying that it's not likely at this point in time to be able to do it. Although I'll never say never on that, because I thought I couldn't fix the extra lines after the database character conversion and was able to anyway. Just remember, all of this, this rewrite is a complete work in progress. So there are many things that will be changing. As to the NEED for any kind of change? It was definitely there. The scripting was incompatible to newer language cores, as we saw when I attempted to update to php 5.4.x. The database language core had a change in character set, which is what going read only for a limited time is about. I have to convert the text data from one character set to another. Further, without doing this conversion, and with the updates to language cores, it made the likelihood of a major database crash inevitable. So there are things that must be done, period. I'm not talking about cosmetics in this part either. Cosmetics are not a primary concern for me at this point in time. Integrity of the database, STABILITY of the database is what I'm working on, and is what my number one priority is at the moment. Once I have that taken care of, then other things can be focused on. manta2g does the coding. She is centralizing most everything, which is a GOOD thing. She is also making it so any of the archive scripting is compliant several versions AHEAD of the php version we're currently running. It makes the site run more efficiently. Again, the mechanics and stability are also HER priority at this point in time. Cosmetics are always the very last thing.

We actually do factor in opinions on many things. You're the first person who's disliked the cats though.

which subdomain?

Site is now back to normal for use. I will be putting it back to read only again Wednesday night, starting at approximately 6 pm, until approximately 9 pm, EST. In the process of conversion, I also fixed the issues with the wallotext in the stories. An unfortunate side effect was that it added extra linebreaks to current stuff. It's easy enough to fix, you simply delete the extra empty line. I MIGHT come up with something else to do that system wide, but I don't honestly know if it's doable. These subdomains are converted: anime2 anime hp ne original Something else that I fixed today, was the stretching of the latest listing. It no longer does that. Also fixed it so you should NOT see any oddball characters the user did not intend to be there.

NO ONE can login until I turn the site back from read only, which I'll be doing in a few minutes

if you select Paste or Paste from Word, you should be fine. However, you'll have to wait to try that for a little bit yet while the site is read only.

That last phase takes me at best 5 minutes, where I drop the old tables and rename the converted tables.

I'm Your Hoochie Coochie Man - Muddy Waters

Yes

huh, that must be the shiny new update manta was talking about last night. I'll ask her later about search, and what's the what there.

The archive goes read only from 9 am EST to 5 pm EST today, for database character set conversion. This WILL log you out, so don't be surprised at that.

The old search format for stories is still there. Just like before, you have to be within the archive where you want to search, to search for a specific story.

That'll fix once the archive is rewritten enough to support PHP 5.4

The issue is your use of uploading files instead of direct copy/paste. First of all, the archive does not support actual file upload of .rtf and .html files. Only .txt files. Secondly, in order for a .txt file to retain formatting, you HAVE to know some rudimentary html, as in how to contain the text in a paragraph, or make a line break. when creating a text file, these are not automatically added by the text editor. It may LOOK like it is, but it is not. Those lines between paragraphs in a plain text file are a visual thing only, and don't actually work with the mechanics of things, such as actual html, which is what the rich text editor converts a file TO.

it's the mystical ass womb! That is all...

The textsizer java actually interferes with screen readers because of the java embedded within the screen readers themselves. There's a conflict between the java commands. Makes me wonder if that's why browsers instituted zoom...

Checked with manta, and the reason the textsizer is gone, is because it interferes with screenreaders like JAWS. As one of the things we were and are aiming for was to make the site play nice with screen readers,

You can easily adjust the font size using your browser to zoom in. I was doing that already, because even with the textsizer, it wasn't quite big enough for me.

Provide me a link to the story so I can have a look please. As I said, this really only affected a few stories.

What jayDee said is the only way of know of to search your content older than a year.