If you read back a ways you'll see it can be difficult to test this mod. Or at least not as easy as it would seem. I know in one of my posts I had figured it out and posted how.

Whats difficult ? Its very easy to test it.

Arg. Terribly sorry! I was thinking of the Multiple login detector. So many mods they sometimes blur together.

I'll test it tomorrow because my server goes offline -.-

I get lots of database error message reporting back to me, with the nick of the "miserable user" ive set? is this a real error, or just one that they see from the server busy setting?

This does not generate database errors, so they must be real.

Thanks Paul, only got them when I enabled this and added a user. Not sure what it could be then, but i was getting loads of error emails, mostly containing different results. I've disabled for now, and the errors have stopped.

Will have a closer look when i get some more time, pity though, i could have found a use for this :)

Most likely they are mysql gone away errors, because your server has a very low mysql timeout value - meaning it is lower than the delay setting you have set in the mod.

I'm getting the same error but the only plugin I have installed that RedFoxy has other than the stock blog and CMS is the multiple login detector. So I disabled it and the error remains. I then went through the other pulgins that I have and disabling all of those didn't help. I changed the timeout options to 1 and 2 seconds for min and max but that didn't help either.

I also have two other strange issues.

(1) When miserable users get the busy server message other than that message itself the rest of the site is completely blank. There are no words in the tabs, and the login box appears again as if the user isn't logged in. When on the CMS section everything appears normally but when on the forum pages that's when the words disappear.

(2) Instead of a blank page they get a blank page that says "Error - Please try again"

Any advice? I know you said it is working fine on your site but perhaps something I wrote would trigger an idea for me to try?

Thanks,

Mike

The blank page option does actually put out the message "Error - Please try again", thats by design, the rest of the page is blank. Currently that message is fixed, but it will be optional in the next release.

The server busy message problem is due to the way it currently calls that standard message. vB4 completely changed the way the busy message works and when I ported this, that seemed the best way - however I have since re-designed that way this generates the message, and it should be ok in the next release.