Title: Critical issue &nbpsa Last modified: September 17, 2023 --- # Critical issue &nbpsa * Resolved [Malae](https://wordpress.org/support/users/malae/) * (@malae) * [3 years, 1 month ago](https://wordpress.org/support/topic/critical-issue-nbpsa/) * Hello, Can you please explain the meaning of the following warning on the WP Tools dashboard page:Site HealthYour site has  a critical issue that should be addressed as soon as possible. Viewing 12 replies - 1 through 12 (of 12 total) * Plugin Author [sminozzi](https://wordpress.org/support/users/sminozzi/) * (@sminozzi) * [3 years, 1 month ago](https://wordpress.org/support/topic/critical-issue-nbpsa/#post-16650989) * Hi Malae, * Try this steps: 1. Go to Dashboard => Tools => Site Health and click over each title to open the boxes with details about issues. 2. Go to Dashboard => WP Tools => Show PHP Errors and look for error details. * Our blog has a lot of tips about how to fix errors: * [https://wptoolsplugin.com/blog/](https://wptoolsplugin.com/blog/) * Please, let me know if you have questions. * Cheers, * Bill * Thread Starter [Malae](https://wordpress.org/support/users/malae/) * (@malae) * [3 years, 1 month ago](https://wordpress.org/support/topic/critical-issue-nbpsa/#post-16651402) * ```wp-block-code Hello Bill, Thank you for your prompt reply. I will explain further: The message says: Your site has  a critical issue ... Here the  a threw me as I have never seen it before. I then wondered, if it was just a corrupted   and if just a space, it added nothing to the message, but confused the meaning. I went to Dashboard| Site Health, it is said: 1 critical issue Your site is set to log errors to a potentially public file I do have define ( 'WP_DEBUG_LOG', true ); set in the wp-config.php file, but I also have code in the .htaccess file to protect it. If I comment out the debug line and now go to Dashboard| Site Health, it is says: Good and to Dashboard | WP Tools I now see Looking good, but  some things can be improved.' So I now understand where it all came from and it was not a PHP error. I do think that the formatting of the error messages need to be checked to get rid of the&nbps`. As you suggested, I had checked the WP Tools PHP errors and found the following" Type: PHP Deprecated Message: Required parameter $title follows optional parameter $showServerName In: /wp-content/plugins/wptools/functions/functions_benchmark.php on line 250 Type: PHP Warning Message: Trying to access array offset on value of type null In: /wp-content/plugins/wptools/functions/functions.php on line 1664 Type: PHP Warning Message: strip_tags() expects parameter 1 to be string, array given In: /wp-admin/includes/widgets.php on line 238 Type: PHP Warning Message: strnatcasecmp() expects parameter 1 to be string, array given /wp-includes/class-wp-customize-widgets.php on line 1111 Note that 2 are in WP Tools plugin files and two in core files. Since Javascript errors are grouped with PHP, I also note scores of javascript errors, perhaps > 100, almost all of which are in core files. Are they all really errors? Can yo separate the Javascript and PHP errors? I hope the above will assist in improving your useful plugin.`Hello Bill, Thank you for your prompt reply. I will explain further: The message says: Your site has  a critical issue ... Here the  a threw me as I have never seen it before. I then wondered, if it was just a corrupted   and if just a space, it added nothing to the message, but confused the meaning. I went to Dashboard| Site Health, it is said: 1 critical issue Your site is set to log errors to a potentially public file I do have define ( 'WP_DEBUG_LOG', true ); set in the wp-config.php file, but I also have code in the .htaccess file to protect it. If I comment out the debug line and now go to Dashboard| Site Health, it is says: Good and to Dashboard | WP Tools I now see Looking good, but  some things can be improved.' So I now understand where it all came from and it was not a PHP error. I do think that the formatting of the error messages need to be checked to get rid of the&nbps`. As you suggested, I had checked the WP Tools PHP errors and found the following" Type: PHP Deprecated Message: Required parameter $title follows optional parameter $showServerName In: /wp-content/plugins/wptools/functions/functions_benchmark.php on line 250 Type: PHP Warning Message: Trying to access array offset on value of type null In: /wp-content/plugins/wptools/functions/functions.php on line 1664 Type: PHP Warning Message: strip_tags() expects parameter 1 to be string, array given In: /wp-admin/includes/widgets.php on line 238 Type: PHP Warning Message: strnatcasecmp() expects parameter 1 to be string, array given /wp-includes/class-wp-customize-widgets.php on line 1111 Note that 2 are in WP Tools plugin files and two in core files. Since Javascript errors are grouped with PHP, I also note scores of javascript errors, perhaps > 100, almost all of which are in core files. Are they all really errors? Can yo separate the Javascript and PHP errors? I hope the above will assist in improving your useful plugin. ``` * Plugin Author [sminozzi](https://wordpress.org/support/users/sminozzi/) * (@sminozzi) * [3 years, 1 month ago](https://wordpress.org/support/topic/critical-issue-nbpsa/#post-16651585) * Hi Malae, * I just test in our site and it is working. * Please, go to * Dashboard => WP Tools => Dashboard => Debug Info * Copy the Debug details and paste on this site * [https://BillMinozzi.com/support](https://BillMinozzi.com/support) * Cheers, * Bill * Thread Starter [Malae](https://wordpress.org/support/users/malae/) * (@malae) * [3 years, 1 month ago](https://wordpress.org/support/topic/critical-issue-nbpsa/#post-16652042) * Hello Bill, * The WP Tools plugin is working on my site too and I understand what was causing the critical error. In fact it was a false positive, because the wp-debug.log file is not accessible and is presently not being created, as there are no detected PHP errors at present. My issues are with the ` ` showing in the error messages. and the many javascript errors in WordPress core files that are showing in the PHP errors. I don’t understand why it is necessary to paste the  WP Tools | Dashboard | Debug Info. * Plugin Author [sminozzi](https://wordpress.org/support/users/sminozzi/) * (@sminozzi) * [3 years, 1 month ago](https://wordpress.org/support/topic/critical-issue-nbpsa/#post-16652184) * Hi, * I can’t make a diagnose without information. * ** _ _; **is a entity in HTML and means  non-breaking space. * Javascript errors can kill your site. * The Debug info give us a lot of information as: * Memory available * Operating System and other sofwares version * WordPress Version * WP Tools version * Plugins and theme installed * and more. * Please, take a look in our troubleshooting page: * [https://siterightaway.net/troubleshooting/](https://siterightaway.net/troubleshooting/) * Our blog has a lot of tips about how to fix errors: * [https://wptoolsplugin.com/blog/](https://wptoolsplugin.com/blog/) * Maybe that can help you. * Cheers, * Bill * Thread Starter [Malae](https://wordpress.org/support/users/malae/) * (@malae) * [3 years, 1 month ago](https://wordpress.org/support/topic/critical-issue-nbpsa/#post-16654248) * Hello Bill, * I think you misunderstood my questions and comments. I was having problems with the notifications shown in the WPTools plugin, not with my website, so I will explain further. * The first issue that confused me was the message _Your site has  a critical issue that should be addressed as soon as possible_. The inclusion of the ` a` was puzzling and that was the main reason I contacted you. When I checked further it was clear that the critical issue was not ` a`, but the `define ( 'WP_DEBUG_LOG', true );`  set in the wp-config.php file.  The issue was then why is _ a_ being displayed.  I then assumed it was an error in writing ` ` as ` ` in one of the plugin files.  Checking today, I found the culprits: In wptools/ functions/functions.php,  I found that this occurs in lines 2789, 2793, 2796 and 2799,e.g. line 2789:`$output .= esc_attr__('Your site has','wptools').'  < strong> '.esc_attr__('a critical issue','wptools').' '. esc_attr__('that should be addressed as soon as possible.','wptools');`After adding the missing `;` , the issue disappeared, * I am now more familiar with the plugin and see that you have a separate menu heading for **Javascript and jQuery**, in which opens to a list of **Javascript Errors. ** My question now is why are Javascript errors also showing with the** PHP Errors**. There are so many JS errors, which makes it more difficult to find the few PHP errors.  I ask again, are all the many Javascript errors detected in WordPress core files an issue? * I pointed to PHP errors in the plugin although they don’t, show in my debug.log file, are they an issue? * I hope this clarifies the issues. * Plugin Author [sminozzi](https://wordpress.org/support/users/sminozzi/) * (@sminozzi) * [3 years, 1 month ago](https://wordpress.org/support/topic/critical-issue-nbpsa/#post-16654796) * Hi Malae, * Thanks. I got it. In fact, is missing **;** in that lines and I just fixed that. * ** ** is used only to separate words but if is missing ; it doen’t work. * It is not considered PHP error by PHP system. It is just a sort of HTML error. * The message is only to alert you to take a look at Site Health page (managed by WordPress). It is up to you do that. * Our plugin catch javascript errors and add to error_log file. We don’t create a new error log class, we just use this PHP feature to record Javscript errors. error_log is a strong PHP feature and is not a good idea change it. * Anyway, error log file contain other kind of errors, as for example, mysql (database) errors. * You can find more about errors and warnings in our blog: * [https://wptoolsplugin.com/site-language-error-can-crash-your-site/](https://wptoolsplugin.com/site-language-error-can-crash-your-site/) * JavaScript errors in a WordPress site can occur for several reasons, including plugin or theme conflicts, outdated scripts, syntax errors in custom code, and more. These errors can cause unexpected behavior on your site, such as broken functionality, layout issues, or even preventing the site from loading altogether. * **It’s important to fix JavaScript errors because they can negatively impact the user experience of your site, potentially causing frustration or confusion for visitors. They can also harm your site’s search engine rankings if they prevent search engine crawlers from accessing and indexing your content.** * Cheers, * Bill - This reply was modified 3 years, 1 month ago by [sminozzi](https://wordpress.org/support/users/sminozzi/). * Thread Starter [Malae](https://wordpress.org/support/users/malae/) * (@malae) * [3 years, 1 month ago](https://wordpress.org/support/topic/critical-issue-nbpsa/#post-16658608) * Hello Bill, * I think you are still not understanding some of my questions and comments. You didn’t really answer my question about why are Javascript errors also showing under the **PHP Errors** heading  Why do you duplicate the display of Javascript errors?  If you cannot separate them from the PHP errors then why not change the title of **PHP Errors** **to PHP & Javascript Errors** and remove the separate** Javascript and jQuery **from the menu as it seems to just duplicate information also in the **PHP Errors**? * I ask again, are all the very large number of Javascript errors detected in WordPress core files an issue? * You also have not yet answered about the deprecated PHP in the WPTools plugin, which I posted in my first reply: `Type: PHP Deprecated Message: Required parameter $title follows optional parameter $showServerName In: /wp-content/plugins/wptools/functions/functions_benchmark.php on line 250``Type: PHP Warning Message: Trying to access array offset on value of type null In: /wp-content/ plugins/wptools/functions/functions.php on line 1664` * Plugin Author [sminozzi](https://wordpress.org/support/users/sminozzi/) * (@sminozzi) * [3 years, 1 month ago](https://wordpress.org/support/topic/critical-issue-nbpsa/#post-16658932) * Hi Malae, * I think it’s a **good idea** to change the menu voice from “PHP ERRORS” to “ERRORS LOG”. I will make this change in the next version soon. * I like the idea of keeping one separated voice for JavaScript errors because they are very serious and need to be addressed as soon as possible, and Usually not everyone pays attention to them. However, I use the error_log PHP function to record them, and I think they can also be included in the (new) “ERRORS LOG” voice. So, those who don’t thoroughly examine the various menu voices will at least examine the so-called ERROR LOG. * **As I said, JavaScript errors are very serious and should be removed immediately.** Obviously, PHP, MySQL, and even HTML errors should also be removed immediately. * O wrote before: “_JavaScript errors in a WordPress site can occur for several reasons, including plugin or theme conflicts, outdated scripts, syntax errors in custom code, and more. These errors can cause unexpected behavior on your site, such as broken functionality, layout issues, or even prevent the site from loading altogether._“ * Regarding the PHP Deprecated warning (not error): “_Required parameter $title follows optional parameter $showServerName_“, this is just a warning message meant to inform you that this code **may** cause issues in **future** versions of PHP and should be updated. **Although the code will still work as intended**, I just fixed it and will upload it to WordPress soon. * The other **warning** on line 1664 is just a warning, not error. Don’t worry, it means that there was a condition on your server where a variable was not defined( a variable that controls whether the letter should be in bold or normal). I have already made the correction and included it in the next version. * Thanks for yours suggestions to improve the plugin. * Cheers, * Bill * Thread Starter [Malae](https://wordpress.org/support/users/malae/) * (@malae) * [3 years, 1 month ago](https://wordpress.org/support/topic/critical-issue-nbpsa/#post-16660306) * Hello Bill, * Thank for you reply. The plugin is comprehensive and provides many ways to check what is happening on a site. I felt that it would help, if you can avoid duplication of what is reported. * On the subject of PHP errors, you said _The other warning on line 1664 is just a warning, not error_ Strictly speaking, notices and warnings are categorised as errors in PHP as well as the more serious errors that cause halting of the script. Your menu heading **PHP Errors** displays notices and warnings, which is correct. * Although notices and warnings may be ignored, if they flood the wp-debug log file, they make searching for other problems more difficult and I usually try to fix the problems that cause them. This is difficult when the problems are in a third-party theme, or plugin, because, if I fix them myself, they will be overwritten, if there is an update. PHP and Javascript errors in WordPress core files should be at a minimum and I am surprised at how many Javascript errors are displayed in core files by WPTools * Plugin Author [sminozzi](https://wordpress.org/support/users/sminozzi/) * (@sminozzi) * [3 years, 1 month ago](https://wordpress.org/support/topic/critical-issue-nbpsa/#post-16660716) * Hi Malae, * You are welcome. * Thanks for the suggestions, i included the fixes and I will upload a new version soon. * Good luck with your site. * Cheers, * Bill * Plugin Author [sminozzi](https://wordpress.org/support/users/sminozzi/) * (@sminozzi) * [2 years, 8 months ago](https://wordpress.org/support/topic/critical-issue-nbpsa/#post-17056962) * Hi jboy, * We have a very comprehensive article that explains the anatomy of an error message. Here is the link: * [https://wptoolsplugin.com/site-language-error-can-crash-your-site/](https://wptoolsplugin.com/site-language-error-can-crash-your-site/) * The error is a “PHP Fatal error,” which means it’s a serious error that halted the script’s execution. * The error occurred in the file /home/roomspac/public_html/wp-includes/PHPMailer/ PHPMailer.php at line 874. * The error is caused by the use of the mail() function in the PHPMailer library, but PHP cannot find this function. This may be due to incorrect or missing server configuration. * It appears that the error is happening in the context of a plugin called “essential- real-estate” that is trying to send an email using PHPMailer. * Try to get support from the developer of the essential-real-estate plugin. * You can also try our free plugin: * [https://wordpress.org/plugins/real-estate-right-now/](https://wordpress.org/plugins/real-estate-right-now/) * Cheers, * Bill Viewing 12 replies - 1 through 12 (of 12 total) The topic ‘Critical issue &nbpsa’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/wptools_f5b713.svg) * [WP Tools Debug Log, Repair, Javascript errors, Jquery errors, Increase Maximum Limits, File Permissions, Transients, Error Log](https://wordpress.org/plugins/wptools/) * [Frequently Asked Questions](https://wordpress.org/plugins/wptools/#faq) * [Support Threads](https://wordpress.org/support/plugin/wptools/) * [Active Topics](https://wordpress.org/support/plugin/wptools/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wptools/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wptools/reviews/) ## Tags * [critical issue](https://wordpress.org/support/topic-tag/critical-issue/) * [javascript errors](https://wordpress.org/support/topic-tag/javascript-errors/) * [PHP errors](https://wordpress.org/support/topic-tag/php-errors/) * 12 replies * 4 participants * Last reply from: [sminozzi](https://wordpress.org/support/users/sminozzi/) * Last activity: [2 years, 8 months ago](https://wordpress.org/support/topic/critical-issue-nbpsa/#post-17056962) * Status: resolved