[truebluefan]

I need to know. I know for the most part you have been doing it, but I need to know of any issue you are having.

I have reported all issues that I could not fix myself. I am changing the way I do it. I will, come back in here to this forum 'Cricket Forum Suggestions & Feedback'
to threads where posters posted issues. I will check every day for new issues as well. Then as I said every two days I will ask you if it is resolved. If it has not been resolved, I will inquire with Tech as to when we can expect it to be fixed. Hopefully by doing that a couple of times will help fix issues in a more timely manner.

Also remember to do this:

What browser are you using?
What were you trying to do when the problem occurred?
What page were you on when the problem occurred (supply a link if applicable)? Or even better, a screen shot!
Have you tried to do it again but received the same error?

For those of you using the beta FF3, remember is has bugs. Mine does, many users I have ran into say their browser has bugs. So an issue may not be site related when it comes to using FF#, however, we can talk about it! Maybe after discussion we agree it is a problem!

The four questions above, especially apply to database errors! The fourth question is really helpful.

When reporting site slowness. make note of the ad being displayed and the # total number of posters online at that time. In other words this may help give an answer as to why the forum is slower than usual.

I always have and always will tell you if it is a network issue, once I know about it.

[Sparky]

What browser are you using? Internet Explorer 7.
What were you trying to do when the problem occurred? View Thread.
What page were you on when the problem occurred (supply a link if applicable)? Or even better, a screen shot!
Have you tried to do it again but received the same error? Yes.

When I try viewing various pages on the forum I keep on getting a 'Page cannot be displayed error' I get this message when viewing threads and logging into the Mod CP.

Thanks,

Sparky.