Malae

Hi Nebu John,

Regarding the cache, only one site had the WP OPcache plugin installed and active, so I don’t thing it was a cache issue with the others.

In my first attempt to update the 7 sites, I used the “nuclear option after seeing no change in the message: Nobroken links found. No URLs in the work queue. Searching your blog for links..., for some time and then used the Nuclear Option button, which had no effect.

Regarding “After clicking the Nuclear Option all started.“, this was in cases where version 2.1 of the plugin had been uninstalled and reinstalled, but still hadn’t started.

The above warning was in the wp-debug file, but nothing is showing in the panel. Assuming that this may be thrown by another plugin, I have gone through the site and the only issue I found is that if I try to open Customise, I get a fatal error:

Fatal error: Uncaught Error: strnatcasecmp(): Argument #1 ($string1) must be of type string, array given
in /home/u675030324/domains/chronographia.eu/public_html/wp-includes/class-wp-customize-widgets.php on line 1

Call stack:

strnatcasecmp()
wp-includes/class-wp-customize-widgets.php:1131

WP_Customize_Widgets::_sort_name_callback()

usort()
wp-includes/class-wp-customize-widgets.php:1050

WP_Customize_Widgets::get_available_widgets()
wp-includes/class-wp-customize-widgets.php:714

WP_Customize_Widgets::enqueue_scripts()
wp-includes/class-wp-hook.php:308

WP_Hook::apply_filters()
wp-includes/class-wp-hook.php:332`

WP_Hook::do_action()
wp-includes/plugin.php:517

do_action()
wp-admin/customize.php:1

Query Monitor

• This reply was modified 1 year, 10 months ago by Malae.

Another try with this plugin now using PHP 8.0 and I am receiving the following message in debug:

PHP Notice: MemcachePool::set(): Server 127.0.0.1 (tcp 11211, udp 0) failed with: Connection failed: Connection refused (111) in /wp-content/plugins/cache-master/vendor/shieldon/simple-cache/src/SimpleCache/Driver/Memcache.php on line 145

Can you give me any pointers to get the plugin working?

After seaching the use of the constant “T_COMMENT”, I found that it was a parser token that requires the PHP Tokenizer extension to run, but not installed on my LAMP server. After building the php80-tokenizer package, which took a considerable time, installing it and restarting the server the fatal error was gone. Linux is amazing.

Please! If I fix myself and there is an future update without these the necessary changes, my changes will be lost.

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

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/<strong>wptools/</strong>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/<strong>wptools</strong>/functions/functions.php on line 1664

Hello Demis,
Installed the latest version of the plugin and I am now on PHP 8.0 and WordPress 6.2. I have no trouble scrolling on the desktop , but still not working on mobiles.

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 &nbspa critical issue that should be addressed as soon as possible. The inclusion of the &nbspa was puzzling and that was the main reason I contacted you. When I checked further it was clear that the critical issue was not &nbspa, but the define ( 'WP_DEBUG_LOG', true ); ?set in the wp-config.php file.? The issue was then why is &nbspa being displayed. ?I then assumed it was an error in writing   as &nbsp ?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').'&nbsp;<a href="' . esc_url( admin_url( 'site-health.php' ) ) . '" target="_blank"><strong>&nbsp'</strong>.esc_attr__('a critical issue','wptools').'</a>&nbsp;'.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.

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 &nbsp 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.

Hello Bill,

Thank you for your prompt reply. I will explain further:

The message says: Your site has &nbspa critical issue ... Here the &nbspa 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 &nbspsome 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"
<code>Type: PHP Deprecated Message: Required parameter $title follows optional parameter $showServerName In: /wp-content/plugins/wptools/functions/functions_benchmark.php on line 250</code>

<code>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</code>

<code>Type: PHP Warning Message: strip_tags() expects parameter 1 to be string, array given In: /wp-admin/includes/widgets.php on line 238</code>

<code>Type: PHP Warning Message: strnatcasecmp() expects parameter 1 to be string, array given /wp-includes/class-wp-customize-widgets.php on line 1111</code>

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 &nbspa critical issue ... Here the &nbspa threw me as I have never seen it before. I then wondered, if it was just a corrupted &nbsp; 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 &nbspsome 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.

Problem solved. I had recently changed this site from a domain to a subdomain using WordPress 6.1 and because the latest back-up had problems, I had used an older backup from my LAMP server. This had been made when WordPress had just released Version 5.0, which was not compatible, and I had added some code to the theme functions.php file to prevent core updates > version 4.9.9 from appearing, so as to avoid accidental updating. This code was still in the functions file and removing it has fixed the problem.

Hello Adam,

Thanks for the suggestion. I had already tried that, but it results in a blank page, which if refreshed results in the same message as shown above from Query Monitor.

Still crashing the site using PHP ver. 8.0.28,

Fatal error: Uncaught Error: Attempt to modify property "updates" on /wp-content/plugins/wp-downgrade/wp-downgrade.php:195

Hi Bill,

Thanks for your fast response. Looks good – no more warnings