Undefined Index notice filling error log

Hi Sarah, sorry about the trouble you are experiencing. I think I might know what is causing the issue to persist (I had thought I killed this bug in my last update). Two questions:

1. Are you an Administrator-level user in WordPress?

2. Do the notices stop when you visit the Honeypot settings page (under the CF7-added “Contact” admin menu) and click “reset”? Or if you select some settings and click “save”?

Hi Ryan, thanks for the quick response!
1. Yes, I am the Admin.
2. Clicking “reset to defaults” on the settings page seems to have stopped the notice, so hooray!
I appreciate your help and glad it was such an easy fix. ??

-S

Glad to hear it solved the problem. Still troubled I can’t sort out what combination of things is triggering the notices though. I’ll keep poking at it. Will mark this as resolved though, as anyone else seeing this can replicate the “reset to default” fix for now.

hi there, i got the same message. i think since 1 or 2 days or so.

I also gut more messages to share, so you might find the issue which i think is related to the last WP updates (so you should look what have changed)

This shows in the backend:
Notice: Undefined index: honeypot_cf7_req_msg_dismissed in /wp-content/plugins/contact-form-7-honeypot/includes/admin.php on line 23

These are visible in the frontend:

Notice: Undefined index: placeholder in /wp-content/plugins/contact-form-7-honeypot/includes/honeypot4cf7.php on line 61

Notice: Undefined index: w3c_valid_autocomplete in /wp-content/plugins/contact-form-7-honeypot/includes/honeypot4cf7.php on line 65

Notice: Trying to access array offset on value of type null in /wp-content/plugins/contact-form-7-honeypot/includes/honeypot4cf7.php on line 76

maybe its also related to caching?

The settings page was also full of errors, screenshot:
https://office.netzgestaltung.at/index.php/s/C2zzSmS4CJc4XoL/preview

after resetting and saving its gone.

Hi @netzgestaltung – thanks for posting such a solid amount of detail. The reset should solve the problems (as you indicated). I’ve just released v2.0.4, which should address these issues at the outset and not lead to any PHP notices. Thanks again!

happy i could help (and get an update ?? )