One of my members gets a 404 Error when trying to preview a post:

"Forbidden
You don't have permission to access /XXXXX/ubbthreads.php on this server."

Now I don't have this person's IP in my .htaccess (which is uaually why one would get this error). Rick, any idea what might cause this when he tries to preview?

Basil

Does everything else work ok? To see if it's some sort of AJAX issue with the user, have him try to edit his profile and preview his signature and see if that works for him.

That is the exact error I get when the server I'm on rejects a keyword deemed dangerous, such as the word lynx (with a space after it). Perhaps your server has that same anti-hacking utility (or whatever it is) scanning your webforms, and it's rejecting a specific word being typed. Just a possibility. If you have them email the exact text to you, you could try it yourself to see if the server is rejecting something. You can also preview it here, as I don't think any utility like that is running (since I can use the work "lynx " here).

it's called mod_security; and it's quite millitant... You should ask your host to check your error_log to see what keyword is triggering it.

Thanks, I keep forgetting what it's called, and I think I've mentioned this at least 3 different times already on this bb

Yeah, this is one of the things that had me stumped when working on a board. It wouldn't allow anything with a @ and a : on the same line.

And I think I've said its name 3 differant times already lol ;)...

We used it at "the webhost" when i was there, took some getting used to, and a lot of configuration to get running right...

It is quite nice, but ships way too anal retentive...

Next time I'll just search for the word "lynx" here and find it.

now searching for "anal retentive...lynx" waiting waiting....

Hehe one hopes ;)...

I did a bunch of research on the module, it is really quite nice, but the rules themselves can toatally trash some scripts, not to mention leave the admin's of the sites going "what the hell?" when they're trying for legit use...

If you have access to your error logs you should be able to find it, in a section 509 error code i think; it's been a while since i've played with it.