Ive got a small number of users (2 or 3) who cannot send PMs. They get an "Error in Page" displayed and the PM isn't sent.

Of course, when I login to their accts I can send PMs just fine. This indicates to me that its a browser settings issue.

What are the basic browser settings that are required for the board features to work properly?

You should ask them about there own browsers?

Normally i read, users can not post due to
firewall issues, but can send pm's and that
was due to the http referrer being enabled in the
control pannel.

Disable it (Tick the option) while chatting to them and see if
it corrects the problem?

Its not that important if spam isnt an issue.

Disable header referrer is checked. I changed that awhile ago. I'm wondering if there is a list of specific browser settings that MUST be enabled for the board to function optimally.

For example, I would expect users would have problems with avatars and embedded images being displayed if they were to uncheck the "Load Images Automatically" checkbox in Firefox. Or in IE, if they had "Show Pictures" and "Show animations" unchecked.

What I don't want to have to do is walk them through each of their settings and have them attempt to tell me what the state is for each setting. These folks are great guys, but they're not tech savvy at all.

Need to let us know some of those users details?

Browser? Version?

Version of Threads your running?

Ive had no problems from members except for 1
and there is always one and that was down to
a corrupt fire wall.. (Image not showing)

This behavior sounds very familiar to this thread on here:

http://www.ubbcentral.com/forums/ubbthreads.php/ubb/showflat/Number/175500/page/0/fpart/1

The only problem is that the users who can't send PMs aren't marked as underage and have normal birthdays. The only user I can pin down on browser settings is using IE6 (I guess) on Win98. (Yes...I said Win98). That should tell y'all all you need to know about how why I can't give you more info.

I'm running Threads 7.0.2

It seems to be fixed.

After the move Allen had set the "Full URL to main directory" to use our new server's IP address instead of the domain name. I changed it back, emptied the cache and had the users log out and back in via a link using the domain and they're working happily.

Just hope this works for all of them.

Those cross domain cookie issues can be a killer