Jane

I’m also seeing this error. We’re currently running WP Optimize version 3.6.0

Hi @darshanaw,

Thanks so much for your reply and the link to the guide to create an App Password. I followed these steps and everything is working perfectly!

Jane

We’re getting these warning messages, too. Following this thread.

I’m also seeing a similar warning:

PHP Warning: Trying to access array offset on value of type bool in /home2/collabdev14/thecollaborativecom/wp-content/mu-plugins/assets-manager.php on line 270

after updating to PHP 8.2.16

Line 270 is:

return strpos($current_url[‘path’], $rest_url[‘path’], 0) === 0;

Maybe we can figure out the necessary update? I don’t see where “path” is defined or necessary. Maybe we can update to:

return strpos($current_url, $rest_url, 0) === 0;

• This reply was modified 8 months, 2 weeks ago by Jane.

Would like to follow this thread. We’re seeing the following PHP warning several times a day:

PHP Warning: Undefined array key “path” in /oursite/wp-includes/canonical.php on line 728

WP 6.4.3
PHP 8.0.30

We’re also using WP-Optimize an we are seeing these warnings:

/home/mydomain/wp-includes/canonical.php on lines 714, 725, 728

We have many other sites with similar versions of WordPress and the same version of the theme that aren’t using WP-Optimize and we don’t see these errors.

Update: It looks like this message is appearing because it thinks my submission is spam.

Can you advise me how to adjust the reCaptcha v3 threshold so that it will be more forgiving? (reduce it from 0.5 to something lower)

We are seeing this error message as well. Want to reply so we can follow this thread:

Cron reschedule event error for hook: wf_scan_monitor, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”wf_scan_monitor_interval”,”args”:[],”interval”:60}

Hi vupdraft,
Thanks for your suggestion. I added the line you suggested to the capabilities.php file. And tested again with the WordPress 2021 active and all plugin directories renamed (to simulate deactivating) except for the All in One WP Security & Firewall plugin and I still see the same error. I also see many warning messages in the error_log file. I included the line of code exactly as you had suggested but I’m wondering if it’s not quite correct for my configuration possibly? If you’d like I can send you the text of the error messages in the error_log file or send the file itself somehow.

Hi mbrsolution – Good question. We are running PHP 7.4.27.

Hi vupdraft – I’m getting the same error as Jeff is. I still see the error when I’m using the default WordPress 2021 theme and when all plugins are deactivated except for the All in One WP Security and Firewall. Please advise any further troubleshooting techniques to narrow down. Our site was running perfectly before we updated this plugin to the latest version. Could there be an issue in the updated code of the plugin?

Marking this as resolved as there is a dupe of this ticket.

I’m not familiar with how to view the errors in the browser console. Would you tell me how? Also, it seems like ModSecurity is something that is better to have enabled. Is there any way that the Contact Form 7 styles can be enabled even if ModSecurity is enabled?

Since my last message, I rolled back to CF7 v5.3.2. Still no styles (red) in the “The field is required” error messages and no box around the error message at the bottom. On other sites, I see the class=”wpcf7-not-valid-tip” is referenced in the “styles.css” file when I inspect the “The field is required” but on my contact page at: https://www.achievekids.org/contact/ I don’t see the styles.css file. Is it possible when I rolled back that there is a path in the mySQL database to the CF7 style files is not correct somehow – i.e. it can’t find these files? (like the styles.css)

Hi Bel – Thanks so much for your reply and the instructions to troubleshoot the issue that I reported. Since I posted my query I have created 3 new popups and the issue is no longer occurring, so I am marking this ticket as Resolved. I’m not sure what was happening and what resolved the issue, but all is good now.