Hi friends, sometimes after a post you could see this error message:

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

I made some test and it seems that the problem is due to Posy   that hangs the whole server   ... It doesn't happen every time... But your post will be written anyway, so don't post it twice (or more). I'm lurking the gurus' forums in order to solve the problem... Sorry for the inconvenience...

Typical woman...  

Ozymandias Jones";p="13963 wrote: 

Typical woman...  

Virtually Speaking of coarse!       

I make a habit of when I get an error to recheck the thread for my post to see if it made the database before the timeout that causes the error, rather then reclicking the submit button. Pretty much every time my post is there.

Torm, you could check and see what "timeouts" are available for you to configure and maybe give them a larger value. The downside to that is anyone who experiences the delay will have to wait that much longer for the system to catch up with them.

Thank you Landman, but there is very little things that I can do with godaddy's service, because they want more money to give me some control and the statistics. I'm out of money so I have to suppose... I can only check disk space and bandwidth consumed.

I wonder if you could add an "if/else" statement into the PHP code that when an error occurs, it automatically marks the current thread as read (pardon the rhyme) and redirects the user to the index page...

or even if you wanted to get fancy, redirect them to the unread posts page...

      

     

(I can give you all the files...)

I'm not that smart yet....

I do know there is a way to mute an error in PHP though. It's actually a security precaution to keep the riff raff out of MySQL. It won't display an error but redirect them back to the index or a 404 error page.

     I'm sure that that page come directly from the server and is not in the code of the site, so I should check for what is causing the error or I have no way to avoid the problem...

It's probably Posy surfing all the porn while you are sleeping....

    

Surfing porn is typical of males      

    

... Anyway, it's an Apache error, I'll ask the server log to the system admin...

Posy";p="14010 wrote: 

    

Surfing porn is typical of males      

Yea... OK...
you aren't fooling anyone here.....

Apache....
nuff said....
When you set up MySQL & PHP with an Apache web server there is a lot of special configuration that gets missed usually because people just don't know what they are doing.