Server default php error log file quarantined

Home Forums BulletProof Security Free Server default php error log file quarantined

Viewing 6 posts - 16 through 21 (of 21 total)
  • Author
  • #10250

    For the issue mentioned above about… showing invalid white list rule. You had mentioned to  Download the zip file and install it using the BPS Pro upload zip installer. I haven’t done that yet but the latest version of bps pro 7.0 doesn’t already contain this code fix?


    I a getting this kind of errors.

    [27-Sep-2013 13:53:18 America/Chicago] PHP Warning:  Illegal offset type in unset in /home/missionw/public_html/wp-includes/class.wp-dependencies.php on line 174

    Is there any way in BPS to track what resource (theme/plugin files) were used that caused the error?

    AITpro Admin

    The use of the word “theme” cannot be changed in the Plugin Firewall whitelist error checking code, otherwise it would make the error check useless.

    To get around this issue you can use Regular Expressions code in your whitelist rule. (.*) means match anything.  The whitelist rule will work exactly the same and the Plugin Firewall whitelist rule error checking code will no longer display the Error:  Error: One or more of your Whitelist rules are not valid

    AITpro Admin

    That php error does not tell you which plugin or theme file is actually causing the php error and only displays the WordPress Core file that the plugin or theme code is calling.  You can try using the WordPress WP_DEBUG Constants in your wp-config.php file to track down the plugin or theme code that has the coding mistake in it.


    Add this WordPress DEBUG code to your wp-config.php file after this code:  define (‘WPLANG’, ”);

    define('WP_DEBUG', true);
    define('WP_DEBUG_LOG', true);
    define('WP_DEBUG_DISPLAY', true);
    AITpro Admin

    Actually there is an approach/method to finding out which plugin or theme coding has the problem by looking at the WordPress Core file/code shown in the php error message.  When I look at the code of /wp-includes/class.wp-dependencies.php on line 174 the plugin or theme that is calling this WordPress Class: WP_Dependencies and will have this Class used in the code of the plugin or theme.  You can use the BPS Pro Pro-Tools String Finder tool to search for this Class in the code of all of your plugins files.  If you do not find search results by searching your /plugins folder then you would next search your /themes folder.

    Search String:  WP_Dependencies

    Search Path:  Add your actual Website Root Path that is displayed to you on the String Finder page and add /wp-content/plugins/ to the Search Path to search the /plugins folder: /your actual website root path/wp-content/plugins/

    If you want to search your /themes folder then the Search Path is:  /your actual website root path/wp-content/themes/


    The String Finder tool didn’t return anything. The debug method returned these errors.

    Notice: wpdb::escape is deprecated since version 3.6! Use wpdb::prepare() or esc_sql() instead. in /home/missionw/public_html/wp-includes/functions.php on line 2905
    Deprecated: Assigning the return value of new by reference is deprecated in /home/missionw/public_html/wp-content/plugins/envato-wordpress-toolkit-master/index.php on line 207
    Deprecated: Assigning the return value of new by reference is deprecated in /home/missionw/public_html/wp-content/plugins/mass-mailer/mass-mailer.php on line 512
    Notice: get_theme_data is deprecated since version 3.4! Use wp_get_theme() instead. in /home/missionw/public_html/wp-includes/functions.php on line 2900
    Warning: Cannot modify header information – headers already sent by (output started at /home/missionw/public_html/wp-includes/functions.php:2905) in /home/missionw/public_html/wp-content/plugins/sitewide-privacy-options/sitewide-privacy-options.php on line 560
    Notice: Undefined variable: text in /home/missionw/public_html/wp-content/plugins/bulletproof-security/includes/functions.php on line 5188
    AITpro Admin

    Ok well it was worth a try.  I have no idea which plugin or theme is causing the original error.  I guess you can do the standard WordPress troubleshooting steps to find the plugin or theme that is causing the original error.  Deactivate plugins one by one and test to find the plugin.  Switch your theme to one of the WordPress Themes to see if it is the Theme.

Viewing 6 posts - 16 through 21 (of 21 total)
  • You must be logged in to reply to this topic.