|
|
.htaccess is another option
Another option is to put commands in .htaccess files. You have to ensure they are activated for the server but it does make it easy to seperate areas of your server. For example to run an old program where Register Globals must be on while developing your killer app in a seperate area with Register Globals turned off.
.htaccess is another option
in the .htaccess file the entry would look like this:
There is yet a better way
Better yet, if you have access to edit the php.ini file, you probably have access to edit your site's .conf file.
There is yet a better way
I agree that apache .conf files are the easiest way to do this. Also, the php configuration directives are not restricted to Directory containers, they can be used in a VirtualHost container. This is a great way to change settings for one php driven website without affecting all of your php driven websites.
There is yet a better way
In general, I agree with wallyfoo, but you might want to stick it in .htaccess if it is a short-term solution, while hunting down and clobbering your globals. That way, you can quickly turn it off an on for debugging, but you have to restart Apache every time you change http.conf. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.29 seconds |
|