Version: 1.5
I've enabled output buffering with "output_buffering = 4096" in my php.ini file and this is confirmed when I run phpinfo().
However, admin/systeminfo.php (which also runs during install) shows that output_buffering is turned off (0).
The same thing goes for post_max_size which I have set to 10M (confirmed by phpinfo()) but not reflected in the system info dump.
So question is - is systeminfo.php reading the settings incorrectly or are my settings truly incorrect somehow?
Thanks,
S
[solved] PHP ini config values read incorrectly
[solved] PHP ini config values read incorrectly
Last edited by spcherub on Fri Dec 05, 2008 1:08 pm, edited 1 time in total.
Re: PHP ini config values read incorrectly
Is your phpinfo() in admin folder?spcherub wrote: So question is - is systeminfo.php reading the settings incorrectly or are my settings truly incorrect somehow?
And in install what report "Display php Information" in step 2?
I have set output_buffering to 4096 and systeminfo and install report right
Alby
Last edited by alby on Thu Dec 04, 2008 6:49 pm, edited 1 time in total.
Re: PHP ini config values read incorrectly
Hi Alby,
Thanks for asking the question about whether or not I was running phpinfo() from the admin directory - I was only running it from the main (root) directory.
I copied the php.ini into the admin directory and re-ran the systeminfo script and the desired config values magically showed up! So this leads me to make the following conclusions:
1. The php.in does not have a recursive "effect" (so have /home/php.ini does not imply that scripts in /home/admin will read those values). This is counter to my expectations - but it may be something to do with my hosting provider's setup.
2. The systeminfo script was reporting something that would not have affected the overall functioning of the site (since the "problem" was limited to the /admin directory).
If you have a moment, please validate my assumptions above - if true then I will add a SOLVED tag to the subject line. In either case the problem is fixed for me... for now.
Thanks for the advice.
S
Thanks for asking the question about whether or not I was running phpinfo() from the admin directory - I was only running it from the main (root) directory.
I copied the php.ini into the admin directory and re-ran the systeminfo script and the desired config values magically showed up! So this leads me to make the following conclusions:
1. The php.in does not have a recursive "effect" (so have /home/php.ini does not imply that scripts in /home/admin will read those values). This is counter to my expectations - but it may be something to do with my hosting provider's setup.
2. The systeminfo script was reporting something that would not have affected the overall functioning of the site (since the "problem" was limited to the /admin directory).
If you have a moment, please validate my assumptions above - if true then I will add a SOLVED tag to the subject line. In either case the problem is fixed for me... for now.
Thanks for the advice.
S
Re: PHP ini config values read incorrectly
php not cross the entire filesystem as apachespcherub wrote: 1. The php.in does not have a recursive "effect" (so have /home/php.ini does not imply that scripts in /home/admin will read those values). This is counter to my expectations - but it may be something to do with my hosting provider's setup.
php look in "working directory" of your script (admin folder in this case)
yes, but is impossible to check in "all" directories (must have probes in any folders)spcherub wrote: 2. The systeminfo script was reporting something that would not have affected the overall functioning of the site (since the "problem" was limited to the /admin directory).
I do not think that is the purpose of cmsms: systeminfo is one tool to help solve problems and not the tool for solving problems. Most important is: debug in config.php, error server logs and experience ....
A workaroud is set a "global" php.ini with a PHPRC environment variable but you must ask to your provider....
Alby
Re: PHP ini config values read incorrectly
Alby - Thanks for the reply and information.