JK3 Files Error

[Zhaboka]

I am really getting annoyed at the "404 Document Does Not Exist" error that blocks you from seeing existing web pages on JK3 files. Can't FileFront do something about it?

Oh, and woot for my first post in a loooooooooooooong time.

[CalcProgrammer1]

Ya I'm getting the same thing. Its the stupid ad server that is causing the problem...banner ads are stupid and pointless anyways and it's good that they no longer exist but does it HAVE to come up with the annoying Error? I mean, It's like a race between Internet connection and you clicking the Stop button at the right time...and I'm losing .

[stikk]

If your searching google and find a JK3 files thing, You may click on it and it may come up with the 404. In most cases its when people are looking for things deleted of JK3 files, like there was some ported models there before.There gone now, along with all the nude stuff aswell.

[Mikouen]

Originally Posted by johnpp

If your searching google and find a JK3 files thing, You may click on it and it may come up with the 404. In most cases its when people are looking for things deleted of JK3 files, like there was some ported models there before.There gone now, along with all the nude stuff aswell.

Wrong. They'll simply get directed to JKFiles with a "what you're looking for cannot be found" page.

Like this, for example:
http://jediknight2.filefront.com/kouenrtehroxor

Originally Posted by CalcProgrammer1

Its the stupid ad server that is causing the problem...

Actually, you're also wrong. The Google AdSense server is causing no issues at all - if it is, I certainly haven't encountered them in either Firefox 2.0 or IE7.

Originally Posted by Zhaboka

I am really getting annoyed at the "404 Document Does Not Exist" error that blocks you from seeing existing web pages on JK3 files. Can't FileFront do something about it?

It probably doesn't need to go up the tree to FileFront, actually. The Network Managers can probably sort it out amongst themselves.

First, try clearing ALL private data from your browser - cookies, cache, temporary files, the works. Chances are it's something in there.

If that doesn't work, give me as much info about the problem as you can (i.e. browser, where you're being linked in from, if the URL changes when the page changes, and everything else you think may be helpful) and I'll forward it to Ronnie.

We can't do anything without information, which is why you should always provide as much information as you think is relevant when reporting errors.