Kevin's Watch

The internal server errors are really getting to me. (Yes, I'm venting here because I just lost another post that I spent a fair amount of time composing.) I should not be required to save every single post before previewing/submitting it, f5 or whatever be damned. Posting then becomes a chore rather than a joy. This sort of thing is compromising the user-friendliness of KW. Sure, maybe I'm just whining, but it can't be denied that more and more people are becoming annoyed by this problem. I hope a solution can be found that does not involve making Watchers jump through even more hoops in order to simply post.

(We KW natives are becoming restless. Well, I am, anyway. And don't call me spoiled. Donald Trump is spoiled. Whitney Houston is spoiled. Not an ordinary guy who simply wants a hassle-free web experience on his favorite site after a long day at work. Grrrr...)

You're actually losing the posts? Back button usually takes me back to a page with the text still all there. Unusual if yours doesn't. The only boards I've had a problem with text vanishing when I leave a page then go 'back' is on vBulletins.

I lose the text too if it happens when I post.

--A

Thanks, Avatar! I don't know what the problem was, but it's working okay now.

I also lose the text, the private message, whatever I am typing when the internal watch error hits. I have been trying to remember to copy everything I have been typing, if it is of any significant length, just in case it strikes. That way I can do a paste job and try again.

However, every now and then it does go through. I had typed in a very long PM yesterday and I thought it had been eaten by an error, and stomped off in disgust at myself for having not remembered to save it before I posted it. But the recipient replied to it today, so it did go through somehow despite the error.

If I hit the back button when a post is eaten by an error, it just shows a blank box where all of my words had been...

I think this is a browser dependent behavior. I'm using Konqueror, so my posts never vanish that way, but I've been stuck with IE on a computer that wasn't mine, and then my posts did vanish.

My posts don't vanish that way, either. I am using either Safari or Camino.

my posts do vanish with the internal server error, but I have learned to save prior to preview or post.

I am using IE...

If it's a long post, I usually just highlight and copy it.

Glad something worked Sorus.

Yep, I'm on I.E. as well. Must be browser.

As for the PM's Duchess, I find that if it happens when you submit one, the PM is often actually in your outbox anyway. Occasionally it's not, but often. I think it depends on how far the process got before the error. Same with posting.

MM, if you're trying to post when it happens, try this:

Instead of "Back", press refresh.
I.E. should ask you if you want to resend the data. Choose "Yes"
You'll get a Watch error, (not a server error) saying that no post mode was specified, but your post should actually show up in the thread anyway.

I'm not sure if it works all the time, or even often, but it can work. Worth a try anyway.

--A

i'm getting error msgs but no posting problems and i'm using IE

I've gotten internal server errors with Firefox, but never when I'm posting. It happens sometimes when I first try to view a thread.

It's pretty much random. It's rare that it happens when I'm posting, but it does happen. Mainly viewing, and the search function barely works for me. (Not that I use it often.)

--A

For me, it seems like the ISEs (internal server errors) are more frequent when trying to view large topics and when trying to do large searches. I never get it when posting.

It seems that it will let you do a search for all of my posts (for example), but it won't let you do a search for someone with a ton of posts (say...Darth) (Heh).

I have the feeling that it's the result of the size (in terms of number of posts) that the Watch has grown to, but I'm not sure, so don't hold me to that.

I have no idea how to solve the problem myself. The only idea I have is to start limiting threads to X number of pages. Hopefully it's not an issue of the board size, and hopefully we won't have to start pruning posts.

Maybe pruning Mallory's would be a good idea. It may help the Watch's stability. Or...it may not. Heh.

Hopefully Vain will have some idea of how to solve this problem.

Right now though, it doesn't seem like a big deal to me. I don't get it that often. And when I do, I just try to reload the page and it usually works.

The only thing I can't do anymore is do large searches.

I understand that it's annoying people, though, and I apologize. I'll try to see if I can do anything about it.

Hm...-jay

Well, at least I now know that I'll never again be able to find my old posts using any sort od shortcut.

dANdeLION wrote:Well, at least I now know that I'll never again be able to find my old posts using any sort od shortcut.

What happens when you keep trying to view your posts until it finally doesn't give an internal server error:

Fatal error: Allowed memory size of 10485760 bytes exhausted (tried to allocate 8192 bytes) in /home/sites/ihugny/ihugny/kevinswatch/phpBB2/search.php on line 578

Heh.

Schweet!

Bad Request
Your browser sent a request that this server could not understand.

I just got this one, but found it quite funny.

What is this?

<span class="topictitle

Sometimes when I click 'Back' in the Sub-Forums, it comes up.

Just an error in loading I think...just refreshing should sort it out.

--A