PHP Error Log Path Does Not Match – Error Log Path Seen by Server: blank/none

Home Forums BulletProof Security Pro PHP Error Log Path Does Not Match – Error Log Path Seen by Server: blank/none

Tagged: 

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #40106
    AITpro Admin
    Keymaster

    As of BPS Pro 15.3 additional checks and help info have been added to the “PHP Error Log Path Does Not Match” error message.

    Error Messages/Causes:
    1. The wp-config.php file has been moved to another hosting account folder.
    2. The BPS ini_set Options code does not exist in the wp-config.php file.
    3. Web host PHP server configuration problem.

    Solutions:
    1. If you have moved the wp-config.php file from the default WordPress location (WordPress root installation folder) to another hosting account folder do the steps below to fix the problem.

    1. Temporarily move the wp-config.php file back to the default WordPress location/folder.
    2. Go to the BPS Pro Setup Wizard page > run the BPS Pro Pre-Installation Wizard and Setup Wizard.
    3. Move the wp-config.php file back to the hosting account folder where the wp-config.php file was.
    4. Turn Off the “PHP Error Log Path Does Not Match” error check/message on the BPS Pro > S-Monitor page > PHP Error Log: Check Folder Path Location Alert option > Turn Off Displayed Alerts.
    5. Or if you don’t want to log php errors then just turn Off the PHP Error Log: Check Folder Path Location Alert option on the S-Monitor page.

    2. If the BPS ini_set Options code does not exist in the wp-config.php file do the steps below to fix the problem.

    1. Use FTP or your web host control panel file manager.
    2. Download your wp-config.php file.
    3. Edit your wp-config.php file and copy the BPS ini_set Options placeholder text (shown below) directly below this wp-config.php file text comment: /* That’s all, stop editing! Happy publishing. */ or /* That’s all, stop editing! Happy blogging. */.
    4. Upload your edited wp-config.php file and overwrite your existing wp-config.php file.
    5. Your wp-config.php file will be quarantined. Restore your wp-config.php file from Quarantine after it is quarantined.
    6. Go to the P-Security > ini_set Options page > enter the recommended BPS Pro PHP Error log path displayed on the PHP Error log page in this text box: ini_set PHP Error Log Location Set To.
    7. Click the Save|Enable Options button.

    /* That's all, stop editing! Happy blogging. */
    or
    /* That's all, stop editing! Happy publishing. */
    
    /** BEGIN BPS Pro ini_set Settings **/
    /** END BPS Pro ini_set Settings **/

    3. Web host PHP server configuration problem.

    If your web host has disabled/turned Off PHP error logging you should check your web host control panel for any PHP option settings to turn On PHP error logging.  If you cannot find any PHP option settings then contact your web host support folks and ask them where you would find PHP option settings in your web host control panel.

    Or try this first and see if it works:
    1. Create 2 plain text files using a plain text editor such as:  Notepad or Notepad++ – Do not use Word or WordPad.
    2. Name the files:  .user.ini and php.ini.
    3. Add these 2 lines of directive code below in each file.

    log_errors = On
    error_log = "/copy-the-bps-recommended-php-error-log-path-here/"

    4. Upload the .user.in and php.ini files to your hosting account root folder. Note: .user.ini files can be used per site in each WordPress installation folder if the host server is configured for that.
    5. If/when the .user.ini and php.ini files are quarantined by AutoRestore|Quarantine, restore them from Quarantine.
    6. Check the P-Security > PHP Error Log page and see if your host server now sees the path to the BPS PHP Error log file.  Note: It could take up to 15 minutes for your host server to refresh/recheck for .user.ini or php.ini file changes.

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.