Mongrel,

You may be getting the 500 because you have a module that requires globals to be on.

You can try de-activating any 3rd party modules (de-activate, don't remove, and your data will all remain intact) and see. If you don't find anything, just re-activate the modules and your back where you started minus one potential culprit.

GL

Hey Dave and tripmon!

Thanks for responding!!!

The file does have other content. I have included:

Quote:

per your(?) suggestion in the documentation.

Where would:

Quote:

go in relation to the above? AND how many spaces should be between the phrases? As Protector lists this command, there are three spaces between "flag" and "register." Also three between "globals" and "off." Does it matter?

Also, tripmon—

I am running third-party modules. And I seem to remember reading somewhere that this could be an issue. Once Dave (or someone) can verify what the .htaccesss file should look like, I'll be able to determine whether the deactivation testing will reveal the problem module. Of course, at this point, I don't even know if I inserted the code properly, so I guess I'll start there and get more involved as needed.

Thank you both for your help. I really appreciate it.

mongrel

Put the register_globals directive outside the Files block, either before or after.

The number of spaces doesn't matter.