Trying to use own php.ini file (rather than the one that the webserver
sees by default) for a web site (on a box that has many websites that
utilize the other) and used the following instructions, but it doesn't
seem to notice my own php.ini file.
When the PHP interpreter starts up, it
Robby Russell [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Trying to use own php.ini file (rather than the one that the webserver
sees by default) for a web site (on a box that has many websites that
utilize the other) and used the following instructions, but it doesn't
seem to
Hello pan,
Thursday, April 22, 2004, 8:19:39 PM, you wrote:
p rtfm on ini_set()
What on earth has ini_set() got to do with the web server not picking
up the alternative php.ini file located in the web root?
Sure it will allow you to change *some* of the ini variables, but that
wasn't even the
pan wrote:
Robby Russell [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Trying to use own php.ini file (rather than the one that the webserver
sees by default) for a web site (on a box that has many websites that
utilize the other) and used the following instructions, but it doesn't
Richard Davey [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Hello pan,
Thursday, April 22, 2004, 8:19:39 PM, you wrote:
p rtfm on ini_set()
What on earth has ini_set() got to do with the web server not picking
up the alternative php.ini file located in the web root?
Sure it
John Nichel [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
pan wrote:
Robby Russell [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Trying to use own php.ini file (rather than the one that the webserver
sees by default) for a web site (on a box that has many websites
Hello pan,
Thursday, April 22, 2004, 8:36:51 PM, you wrote:
p on most servers ini_set will be the best you can hope for
p security settings won't allow alternative php.ini file reads
p that's why
Perhaps it would have been more useful to state this in the original
post.
--
Best regards,
on most servers ini_set will be the best you can hope for
security settings won't allow alternative php.ini file reads
If we're talking about Apache, you can place php config commands in an
.htaccess or httpd.conf file. Those files can easily be associated with a
particular VirtualHost.
Rick Fletcher [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
on most servers ini_set will be the best you can hope for
security settings won't allow alternative php.ini file reads
If we're talking about Apache, you can place php config commands in an
.htaccess or httpd.conf
Richard Davey [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Hello pan,
Thursday, April 22, 2004, 8:36:51 PM, you wrote:
p on most servers ini_set will be the best you can hope for
p security settings won't allow alternative php.ini file reads
p that's why
Perhaps it would
10 matches
Mail list logo