Comment Errors [500], Protection Toggles, and Feature Request

  • Resolved ZicPL

    (@zicpl)


    4 months, 2 weeks ago

    Hello Marc Wagner,

    I’m happy to use Your plugin. Unfortunately, the plugin has some problems with the latest version of WordPress.

    1. Every comment ends up as spam (I use the WordPress comment system). In previous topics here, people reported server error 500 (Error: Spam) -> https://horbaczewski.info/wp-comments-post.php. I’ve the same problem. Additionally, I tried each of the methods: -Honeypot – Arithmetic -Image In your plugin, I only have “Captcha Protection” enabled and all other protection options disabled. I also tried toggling “Available Protection Services”, unfortunately it did not solve the problem. I even noticed another error in the Apache logs:
    2024-07-09 01:59:19.918436 [NOTICE] [3239290] [T0] [127.0.0.1:47350#APVH_www.horbaczewski.info:443] [STDERR] PHP Warning:  Undefined array key "protection_cf7_enable" in ../horbaczewski.info/public_html/wp-content/plugins/captcha-for-contact-form-7/ui/controller/UI_Dashboard.php on line 409\n
    2024-07-09 01:59:19.918506 [NOTICE] [3239290] [T0] [127.0.0.1:47350#APVH_www.horbaczewski.info:443] [STDERR] PHP Warning:  Undefined array key "protection_wordpress_comments_enable" in ../horbaczewski.info/public_html/wp-content/plugins/captcha-for-contact-form-7/ui/controller/UI_Dashboard.php on line 409\n
    2024-07-09 01:59:19.918588 [NOTICE] [3239290] [T0] [127.0.0.1:47350#APVH_www.horbaczewski.info:443] [STDERR] PHP Warning:  Undefined array key "protection_wordpress_enable" in ..s/horbaczewski.info/public_html/wp-content/plugins/captcha-for-contact-form-7/ui/controller/UI_Dashboard.php on line 409\n
    2024-07-09 01:59:19.918646 [NOTICE] [3239290] [T0] [127.0.0.1:47350#APVH_www.horbaczewski.info:443] [STDERR] PHP Warning:  Undefined array key "protection_wordpress_login_enable" in ../horbaczewski.info/public_html/wp-content/plugins/captcha-for-contact-form-7/ui/controller/UI_Dashboard.php on line 409\n
    2024-07-09 01:59:19.918691 [NOTICE] [3239290] [T0] [127.0.0.1:47350#APVH_www.horbaczewski.info:443] [STDERR] PHP Warning:  Undefined array key "protection_wordpress_registration_enable" in ../horbaczewski.info/public_html/wp-content/plugins/captcha-for-contact-form-7/ui/controller/UI_Dashboard.php on line 409\n

    I’ ha’ve the latest version of your plugin Version 2.0.5 and WordPress 6.5.5.
    I’ll be grateful for Your time and quick help.

    2. Could You add a new feature?
    Good practice dictates using the least amount of plugins. I use Your plugin and “Duplicate Killer” (https://www.ads-software.com/plugins/duplicate-killer/). Unfortunately, the author “Duplicate Killer” didn’t try to contact me. I created a request there: https://www.ads-software.com/support/topic/cloudflare-turnstile-and-greater-protection-enhancement/ Thanks to this, I found Your plugin and now I use both plugins. Your plugin is based on IP addresses, so I thought it would be easier for you to add a check for a designated field has unique data entered into it.
    To sum up, could You add a new protection feature such as Limit one submission per Email address, Phone or TextField (stop duplicate entries for Contact Form 7). Your plugin has the advantage that it doesn’t use cookies. This would allow me to disable the “Duplicate Killer” plugin, because from now on Your plugin would show “Customise error message for duplicate entries”. I hope I got the right person with my message. Please write me what you think about it ??

    Kind Regards,
    Luke

    • This topic was modified 4 months, 2 weeks ago by ZicPL.

    The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author forge12

    (@forge12)

    Hello Luke,

    Thanks for your message. We updated the plugin to 2.0.61 to resolve the issue with the comments. As for your feature, i’ve created a feature request in our board to discuss this further.

    Best Regards
    Marc

    Thread Starter ZicPL

    (@zicpl)

    @forge12
    Thank You for Your quick feedback.
    I tested it and the comments are added correctly (so far I’ve only tested with one Honeypot protection).

    Thank You for finding time for the feature I proposed. I’ve been wondering for a long time whether to write this request here because I didn’t want to be demanding. I’ve reviewed Your previous support topics and now I know that I wrote to the right person. Your plugin (is GDPR compliant) is based on linking the IP address to the user, which I consider more effective than a cookie (clearing browser data eliminates cookies). I decided that comparing the same fields based on the IP database (Your plugin already has this) would not require a large cost of Your work – otherwise I wouldn’t bother You with this feature. It’s possible that part of the code responsible for checking and comparing fields (if they are unique) from the “Duplicate Killer” plugin can be used in Your plugin.

    Do you agree with my opinion?
    I’ll allow myself to leave the topic open until the functionality is created or rejected, ok?

    @forge12 Has user ZicPL’s request for a new feature been accepted? It’s been a long time since the request was posted. Please respond and let us know if the feature will be implemented. I’d love to see a feature like that in your plugin.

    Plugin Author forge12

    (@forge12)

    Hello @jeroslawsk – thank you for your patience. We are currently updating several plugins by sprints.

    We’ve got a question about the feature: Are you talking about one submit per form, or a general limit for all forms on the website?

    Best Regards,
    Marc

    In this case I’ve a single cf7 (on one of my sites). I’m considering this for other sites as well. It would be nice to be able to specify forms to protect in the settings tab of your plugin. I’m surprised that this feature isn’t yet included in your bot protection plugin, but I’m pleased to see that it is in development. Through collaboration, we can achieve greater results. I’ll eagerly await your implementation announcement ??

    sorddel

    (@sorddel)

    @forge12 You received a feature request from @zicpl over 3 months ago. He provided an example of how this feature works in the “Duplicate Killer” link. I’m also interested in this feature. May I know why the request in this topic wasn’t implemented?

    Plugin Author forge12

    (@forge12)

    @sorddel We reviewed the feature request from @zicpl, but are unsure whether the implementation would be legally compliant with GDPR. For this reason, we decided not to implement it directly. However, we can integrate hooks to allow for a custom development solution if needed.

    Thread Starter ZicPL

    (@zicpl)

    @sorddel Thank You for Your private message and I’ll already comment on discussion.

    @forge12 I was reinvited to speak. 1st of all, thank You for finding time to discuss this feature. You’re right that recoding the “DuplicateKiller” plugin to Your “Captcha for WordPress” wouldn’t be legally compliant with GDPR. I didn’t mean identical create cookies (This already makes it non-GDPR compliant). My request to You was: Verify the field (subject, email, phone, etc. – depending on what the user selects) against its UNIQUE VALUE and TIME, but NOT based on cookies (as is done in DuplicateKiller), but based on the IP address (look at Your “Blacklisted Texts” function).
    Using “Blacklisted Texts” in Your plugin You can check whether a banned word has appeared.
    Why not check if the form subject checksum (we don’t need to know the subject if it’s against anything) isn’t the same one sent 2 minutes ago from the same IP address?

    I hope that now I’ve expressed myself precisely and I’ll be understood.
    ps. Writing to me about the feature doesn’t make sense because the deciding person is @forge12

    kind regards,

    • This reply was modified 1 month ago by ZicPL.
    • This reply was modified 1 month ago by ZicPL.
    • This reply was modified 1 month ago by ZicPL.
Viewing 8 replies - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.