1
Just starting to shift an XOOPS site, to an Apache2 and php5 configured server. I have always used the 'php_flag' setings in .htaccess , as modules like protector, and other XOOPS security settings, need the php settings changed.
On the new server, getting a 500 error on .htaccess
Quote:
Invalid command 'php_flag', perhaps mis-spelled or defined by a module not included in the server configuration
I noticed a few posts on various sites stating the following:
Quote:
adding php_flag in .htaccess under apache 2 will cause internal server error. according to apache 2 manual, php_flag should go to <virtual> or <directory> section.
I will have to find out if the new server is running phpsuexec or not, as
This FAQ states that with phpsuexec, one cannot use .htaccess to modify php settings.
However, I think the reason for the problem is Apache2 somehow.
Has anyone else had this sort of problem, and if I currently have the following in .htaccess
# XOOPS security measures
php_flag session.use_trans_sid off
# Protector module
php_flag register_globals off
php_flag allow_url_fopen off
and phpsuexec is
not running on the new server, do I use the <virtual> or <directory> section, to modify the settings.
NO to the Microsoft Office format as an ISO standard. Sign the
petition
