Robert
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: PHP Error in Automatic Updater after upgrade to 8.2Thank you for your reply. Much appreciated.
Forum: Plugins
In reply to: [Simple Lightbox] Errors on Query Monitor after upgrading from PHP7.4 to 8.2Thanks you for getting back
Will this change be in a future update of the plugin? Or do we have to make this change manually ourselves after each update?
Many thanks
Robert
Forum: Plugins
In reply to: [Error Log Monitor] Deprecated error after upgrading to PHP 8.2Thanks for additional clarification Janis. And we know what to try if we want to get rid of the error message. Your support as always is greatly appreciated.
All the best
RobertForum: Plugins
In reply to: [Error Log Monitor] Deprecated error after upgrading to PHP 8.2Many thanks Janis. So I take it that it’s not something to worry about and is not related to the PHP upgrade from 7.4 to 8.2? So we can simply ignore it?
Forum: Plugins
In reply to: [Error Log Monitor] Deprecated error after upgrading to PHP 8.2Many thanks for your prompt reply Janis. 1.7.12 is definitely installed.
Forum: Plugins
In reply to: [WooCommerce] WooCommerce 8.9.1 update problemNo 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
Forum: Plugins
In reply to: [Error Log Monitor] PHP Error Log error filtered out partly recurs days laterThanks 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
Forum: Plugins
In reply to: [Error Log Monitor] PHP Error Log error filtered out partly recurs days laterHi 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?Forum: Plugins
In reply to: [Error Log Monitor] PHP Error Log error filtered out partly recurs days laterIt’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 210Hope that’s clearer.
CheersRobert
Forum: Plugins
In reply to: [Error Log Monitor] PHP Error Log error filtered out partly recurs days laterHi 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.Forum: Plugins
In reply to: [Error Log Monitor] PHP Error Log error filtered out partly recurs days laterSorry 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’)Forum: Plugins
In reply to: [Error Log Monitor] PHP Error Log error filtered out partly recurs days laterThe ‘echo’ of part of the original error does not appear in the actual log file. The errors appear correctly in the actual log file.
Forum: Plugins
In reply to: [Error Log Monitor] PHP Warning – Expected parameter 2 to be an arrayHi 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 bestRobert
Forum: Plugins
In reply to: [Error Log Monitor] PHP Warning – Expected parameter 2 to be an arrayThanks 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
Forum: Plugins
In reply to: [Error Log Monitor] PHP Warning – Expected parameter 2 to be an arrayFound 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?