Error Logging by means of the HTAccess record

To wrap things up, how about we take a gander at how to empower PHP mistake logging by means of HTAccess. This strategy works extraordinary if HTAccess documents are empowered on your site, and will empower you to log PHP mistakes on any site, not only those controlled by WordPress. The procedure is fundamentally the same as the past strategy, and requires the accompanying two stages:

Stage 1: Create a log document 

Make a vacant document called "php-errors.log". This record will fill in as your site's PHP blunder log. Your server will require compose access to this document, so make a point to set the proper consents. This document might be put in any index, yet putting it over the web-available root registry of your website is prudent for security reasons. When this document is made, writable, and set up, observe its supreme catalog way and proceed to the last advance.

Stage 2: Add the enchantment code 

Next, open your site's root .htaccess document and include the accompanying code:

# log php errors
php_flag display_startup_errors off
php_flag display_errors off
php_flag html_errors off
php_flag  log_errors on
php_value error_log /home/path/logs/php-errors.log

As some time recently, this code is arranged for ideal mistake dealing with for generation servers. The main thing that you have to alter is the outright index way for your log document. Amid site advancement, you might need to change a portion of the factors to empower blunder show, startup mistakes, rehash blunders, et cetera. For more data on these mandates, and for a more inside and out manual for logging PHP blunders by means of HTAccess, look at my article at Perishable Press, Advanced PHP Error Handling through htaccess.

Investigating Tips

To decide the outright way of your log document, transfer a PHP with the accompanying code to a similar catalog and open it in a program:

<h3><?php resound $_SERVER['DOCUMENT_ROOT']; ?></h3>

Contingent upon your server arrangement, you may need to utilize technique #1 or #2 on the off chance that you are running PHP5. Certain double PHP setups and different arrangements may require any php_value mandates to be put in a php.ini document rather than htaccess.

A simple approach to test that your blunder logging framework is working is to trigger a couple of fundamental PHP mistakes. To do as such, make a PHP record and include something that will trigger a blunder, for instance:

<?php resound "blunder" ?> 

In conclusion, in the event that you are activating blunders however nothing is being composed to your log document, triple-watch that the record is writable by the server. Contingent upon your specific server arrangement, you may need to expand the consents level of the document. In the event that you need to keep running with a setting of "777" (full consents), unquestionably ensure that the log document is set over the web-available root catalog of your webpage.