FOT Forum
The Best Show on WFMU => Show Discussion => Topic started by: JimmyKustes on April 01, 2007, 07:59:38 AM
-
The link to the boards on friendsoftom.com is broken.
-
I know what you mean. I always get an error message the first time I click on "Message Board", but it always works the second time.
I kind of like it that way. It rewards my patience and makes me feel special, like the server is saying, "Sorry, David. I didn't recognize you at first."
-
Hmm, I never had that problem before.
-
I know what you mean. I always get an error message the first time I click on "Message Board", but it always works the second time.
I kind of like it that way. It rewards my patience and makes me feel special, like the server is saying, "Sorry, David. I didn't recognize you at first."
You won't be feeling so special when you're begging the message board to open the pod bay doors.
-
I think the problem is that friendsoftom.com/forum doesn't work, only www.friendsoftom.com/forum. So if you come in through friendsoftom.com rather than www.friendsoftom.com, you get sent to a page that says "Service Temporarily Unavailable. The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."
At least that's the problem I'm getting.
-
I think the problem is that friendsoftom.com/forum doesn't work, only www.friendsoftom.com/forum. So if you come in through friendsoftom.com rather than www.friendsoftom.com, you get sent to a page that says "Service Temporarily Unavailable. The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."
At least that's the problem I'm getting.
That's what used to happen to me also, but it hasn't done that in the last few weeks. I've changed the link anyway to include the www. Let's see if that fixes it.
-
When I cleaned up the FOT home page, I rewrote the form link as a directory index (i.e. a URL that doesn't end with a filename). I think that's the problem ... but let's see what happens. If you can reproduce the behavior again, please let us know (and include you browser/version).