Please Register or Log in to view the hidden image! thats in comp with chrome firefox failed as well thread creation worked in sf obviously
the original title was Google - The State of Search amended to The State of Search and thread submitted successfully
I know that in the previous software(s), posting some words or phrases resulted in an error message. I don't know what those words or phrases are for this version of the forum software. I tried posting a thread with "Google" and "search" in the title, but it worked.
the above is a possible but unlikely correlation, signal i guess of course i could try again yeah lemme
same error Google - The State of Search = fail - The State of Search = pass Google The State of Search = pass Google = pass thats in comp i'll try here
Preview thread in Site Feedback: Firefox "Google - The State of Search" FAIL (blank page) "oogle - The State of Search" PASS Google Chrome "Google - The State of Search" FAIL (Internal Server Error) "oogle - The State of Search" PASS Opera "Google - The State of Search" FAIL (Internal Server Error) "oogle - The State of Search" PASS Internet Explorer "Google - The State of Search" FAIL (Internal Server Error) "oogle - The State of Search" PASS
lol Why? I seriously wouldn't mind actually. I mean, as long as I'm interested.. Please Register or Log in to view the hidden image!
Did you: Log out of sciforums clear your cookies then login through a different browser I ask as I know that some methods of authentication and anti-spam can check to see if you post using the same User-Agent within X number of minutes. Switching browser can cause errors, you'd have to try the test again but make sure you clear your cache's to make absolutely sure that it's serverside. As for actual faults.... Well The website has Urchin cookies embedded into each and every page, but they seem to be at the bottom of the BODY element, the fault you are pointing out appears to be occurring during the HEAD(er) phase. Plazma would be able to pull the logs of your access to the website to identify what the Server Status code was when it stopped, otherwise you'll have to get hold of a plugin to view it yourself or use Telnet on port 80 with the right requests.
