Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have the following setting at my php.ini located at D:\wamp\bin\apache\Apache2.4.4\bin:
error_reporting = E_ALL
I now have changed it to
error_reporting = E_ALL | E_STRICT
Then I restarted all services of Wamp.
It doesn't still show the the notices that the production server show.
At both states, in phpinfo() I can see error_reporting set to 32767.
I think there was a little bug that escaped in WampServer2.4 and that was that the php.ini file had the error_log parameter commented out.
So edit php.ini ( using the wampmanager -> PHP -> php.ini )
Look for
;error_log = "c:/wamp/logs/php_error.log"
and change it to
error_log = "c:/wamp/logs/php_error.log"
Assuming you are installed on the C: drive
Also check
log_errors = On
just to be sure.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
How to Install XCache in WAMP server XCache
I got XCache is not loaded
Download xcache curesponding to your PHP version from here
Open php.ini and comment APC, memcache, disable memcache service.
Add the extension = php_xcache.dll to php.ini
Copy php_xcache.dll to the php ext dirctory.
Open xcache.ini, copy & paste all to the end of php.ini (right before ; End:)
Edit the path to php_xcache.dll, example: zend_extension_ts = C:/xampp/php/ext/php_xcache.dll
Set the xcache admin username and password. Use any username. Generate a 32 digit md5 password.
Restart apache and check phpinfo.
php.ini section will look like
[xcache-common]
zend_extension_ts = C:/xampp/php/ext/php_xcache.dll
[xcache.admin]
xcache.admin.enable_auth = On
xcache.admin.user = "anyusername"
xcache.admin.pass = "32-digit-number"
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I follow this guide to install LAMP server on fedora 22 workstation
How To Install LAMP Stack (Apache, MariaDB And PHP) In Fedora 22
Everything working well except phpmyadmin.
When i need access it of the browser
i see nothing (blank page)
How i can fix this issue ?
Any Suggestions ?
Possibly you can get more info via 2 things
1- Enabling php display_errors in php.ini file which you can find by running
php --ini
changing display_errors to on and save it then restart apache web server and revisit phpmyadmin url which should show you the error
2- looking in apache error log which mostly located in /var/log/httpd/error.log
you can use tail -f for better tshooting
tail -f /var/log/httpd/error.log
Try running phpMyAdmin's index.php over the command line. This should give you more information about the error that causes the problem.
php index.php
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I want to hide server/PHP version details from hackers/spammers etc when they view an HTTP response etc.
X-Powered-By:PHP/5.2.6-1+Squeezy
I have read articles like > ducea.com/2006/06/15/apache-tips-tricks-hide-apache-software-version/
And others that say to add
ServerSignature Off
ServerTokens ProductOnly
To my Apache2.conf file, which I have done at the bottom of the file as well as turning off the expose_php option in php.ini etc
expose_php = Off
However even after reloads and restarts of Apache I still see this Response Header.
I am behind Cloudflare so don't know if they have the ability to override my settings or why they would want to.
Does the position of my directives in the Apache.conf file matter?
Are there other files I need to check?
What can I do to ensure this header is hidden from probers etc.
Thanks
I'll be honest in that you're fighting a losing battle here. You're using PHP 5.2.6, which is not only not the latest release of 5.2 (5.2.11), it's been EOL for 4+ years. It sounds like hackers are finding the header and attacking your machine. The problem is that even if you somehow remove the header this will not make your machine more secure. Any vulnerabilities in 5.2 are not being patched. All you're doing is making the problem less obvious.
Cloudflare does not add server headers, nor can they change your server settings.
As to turning it off, you probably did not edit the right file
settings from /etc/apache2/conf.d/security will overwrite ServerSignature / ServerTokens settings set in /etc/apache2/apache2.conf
I think you edited the wrong php.ini file. You have to edit /etc/php5/apache2/php.ini and then set expose_php to 'off' in order to make it work.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I was wondering why my system says it is running the php from the /etc/php5/apache2/php.ini
directory when in fact it was running it from the /etc/php5/cli/php.ini .
When I did a phpinfo() on a file in the directory of the folder, I received this however the changes to the configuration file wasn't impacting the server until I searched the whole system for a php.ini file and found the php.ini file under the cli/ directory:
Hopefully you can see it. I wasn't sure exactly how to put in onto SO.
it's intentional so you can easily have different configuration depending on your runtime environment.
In your environment when php runs in command line mode it uses /etc/php5/cli/php.ini.
When you access it from browser php is running from apache. So then /etc/php5/apache2/php.ini is used.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
i built my site on WAMP and now need to move everything over to LAMP. I understand that include paths are different in LAMP. What do I need to do for the site to work without having to change my code?
phpinfo();
include_path
.:/usr/share/php:/usr/share/pear
is there anything else to look out for when moving a website from WAMP to LAMP?
The biggest issue I have when porting sites from Windows to Linux is filenames and paths. See, Linux is case-sensitive, while Windows is not.
To help you debug those and other errors, you can turn PHP errors on, by searching for and changing two settings in /etc/php5/apache2/php.ini:
error_reporting = E_ALL | E_STRICT
display_errors = On
You can also read the error log in /var/log/apache2/error.log instead of displaying all the errors.
Also, in future I suggest that you develop on the platform you are going to deploy to.