Robert

No problem updating WC core from 8.8.2 to 8.9.1 on our test site this time. Previous problem appears to have disappeared.

Thanks for your help

Robert

Thanks very much Janis for explaining. That certainly sounds like what is happening here. At the moment it appears that I may have finally filtered out all of the error. I assume I could also filter out each trace that is appearing individually without the line number? I’ll try that if the problem recurs. It is an unusually long error and it occurs about 5 times a day in the php error log. Thanks again for all your help. Cheers Robert

Hi Janis
ELM is filtering the main error regardless of line numbers because I entered:

Uncaught ArgumentCountError: Too few arguments to function wp_get_footnotes_from_revision()

in ‘Ignored regular expressions’

That’s why they’re not appearing. Simply Ignoring the error didn’t work because the line numbers kept changing.

Does this help at all?

It’s part of another copy of the full error that is in the log file Janis. The full error is:

[04-Sep-2023 05:06:50 UTC] PHP Fatal error:  Uncaught ArgumentCountError: Too few arguments to function wp_get_footnotes_from_revision(), 2 passed in /home/onenameg/public_html/wp/wp-includes/class-wp-hook.php on line 310 and exactly 3 expected in /home/onenameg/public_html/wp/wp-includes/blocks/footnotes.php:210

Stack trace:

#0 /home/onenameg/public_html/wp/wp-includes/class-wp-hook.php(310): wp_get_footnotes_from_revision(”, ‘footnotes’)

#1 /home/onenameg/public_html/wp/wp-includes/plugin.php(205): WP_Hook->apply_filters(”, Array)

#2 /home/onenameg/public_html/wp/wp-content/plugins/wiki/wiki.php(1561): apply_filters(‘_wp_post_revisi…’, ”, ‘footnotes’)

#3 /home/onenameg/public_html/wp/wp-content/plugins/wiki/wiki.php(1207): Wiki->decider(‘<div class=”mem…’, ‘history’, 0, 0, 0)

#4 /home/onenameg/public_html/wp/wp-includes/class-wp-hook.php(310): Wiki->theme(‘<div class=”mem…’)

#5 /home/onenameg/public_html/wp/wp-includes/plugin.php(205): WP_Hook->apply_filters(‘<div class=”mem…’, Array)

#6 /home/onenameg/public_html/wp/wp-includes/post-templa in /home/onenameg/public_html/wp/wp-includes/blocks/footnotes.php on line 210

But only this part displays in ELM on the Dashboard:

#6 /home/onenameg/public_html/wp/wp-includes/post-templa in /home/onenameg/public_html/wp/wp-includes/blocks/footnotes.php on line 210

Hope that’s clearer.

Cheers

Robert

Hi again Janis
I don’t think I explained properly what the problem is. The single line from the earlier stack trace is appearing in the ELM in the Dashboard not in the php error log file. It’s still happening even though I’ve filtered out the full error so that it no longer appears in the ELM on the Dashboard. But the single line from the now filtered error is still appearing on the Dashboard.

Sorry if I’m not explaining properly Janis. The error on Aug 30 that repeated part of the original error message on Aug 26 was:
#0 /home/onenameg/public_html/wp/wp-includes/class-wp-hook.php(310): wp_get_footnotes_from_revision(”, ‘footnotes’)

The ‘echo’ of part of the original error does not appear in the actual log file. The errors appear correctly in the actual log file.

Hi Janis
Did final test and unignored error. No new similar errors in past 24 hours. So ignored again and assume everything ok. Huge thanks for all your help.
All the best

Robert

Thanks heaps Janis. Will do the final test as you suggest. A lot of the cron errors that we previously set to Ignore will probably reappear now as we deleted the ELM settings. So will just set to ignore again. So not a problem. Will let you know if we have any further problems. But looking good so far. Cheers – Robert

Found the options table and deleted ws_error_log_monitor_settings. And yes, it’s now saving “PHP Warning: array_merge(): Expected parameter 1 to be an array …” in Ignored Messages. So the PHP Error Log in Dashboard is now showing no entries. Do I need to do anything further at this stage?

Thanks Janis for helping with this one. Currently we don’t have anything entered in the “number of entries to show” field. So added ’10’ and saved. But when I went back to the config screen, it hadn’t saved anything! We’re not using a multi site network. Just a regular WP installation. Hope this helps, Robert

Have discussed with our Web Team [all volunteers] but no one can throw any more light on the issue. It may be connected to the upgrade to WP6 that produced a lot of PHP cron warning errors that we have never seen before – probably because the PHP upgrade made errors visible that previously weren’t reported. We generally now ignore these cron errors – without any noticeable impact on the website. Ignoring the error doesn’t always stop the error from appearing. In which case we add these errors to ignored regular expressions in the PHP Error Log.

However, I notice with this error:
Warning: array_merge(): Expected parameter 2 to be an array, string given in?/home/onenameg/public_html/wp/wp-content/plugins/error-log-monitor/Elm/Settings.php on line 8

that when I ignore it and go to Configure, it doesn’t appear in the list of Ignored errors. And when I click Cancel, the same error appears again in PHP Error Log. I tried this several times with the same result. If I Clear Log, the error remains. So I can’t delete it! Very odd behaviour. Hope you can help.
Cheers Robert

Thanks very much for getting back Janis. I confirm the plugin runs all the time. Let me discuss with others in our little Web Team and get back to you.

FYI we’re running WordPress 6.1.1 on Focus Pro Theme using Genesis 3.4.0 and Error Log Monitor 1.7.4

With much thanks

Robert

Hi Janis
I tried the fix you suggested and cleared the log. However, the same error appeared again the next day:
Warning: array_merge(): Expected parameter 2 to be an array, string given in?/home/onenameg/public_html/wp/wp-content/plugins/error-log-monitor/Elm/Settings.php on line 8

Should I try something else?
Many thanks
Robert

• This reply was modified 1 year, 9 months ago by Robert.

Thanks for your advice Janis. Have done as you suggested. Will let you know how that goes.

Many thanks
Robert