Joe C

Thank you for the fast response!

Yes, that does make sense. I guess WordPress err on the side of caution.

We’re still happily using Collect.Chat on our sites ??

Thank you for your quick reply, Phi!

Right now I don’t have an example URL for you, as I set it up to try out on a blank(ish) WordPress install on my localhost.

I’ll see if I have the same problem on a live site, and will let you know.

Okay another update, and a mea culpa!

When tested before, I’d disabled all plugins and switched to a WP theme — thereby also de-activating the PHP files with our filter function in it!

So that’s why the comment got through when I tested before.

So I tested again, but this time I created a functions.php file in the theme directory, and added the filter — now those comments are going to spam.

I also removed the filter again and added “binance” to the list of “Disallowed Comment Keys” in the Discussion settings — and now the comments end up in the trash, as expected.

So WP is behaving as expected, a plugin must be preventing the WP commenting system from acting on the “spam” result from the filter. (I’m fairly sure it’s not wpDiscuz causing this, because I did try disabling only that plugin and got no change — so another plugin must be getting in the way.)

But thank you, Robert, for pointing me in the right direction! Next time I’ll be sure to test on a plain WP install first.

[Edit: Please ignore this comment! I will write an update shortly…]

Okay I’m back with results! (Apologies for the delay.)

So I POSTed samples of the spam data to a test site, both as set up for testing (it’s a copy of the main site) and also with all plugins disabled and the theme set to TwentyTwentyThree.

Both times the log entries were made — so the pre_comment_approved filter is running as expected! And we therefore expect these comments will be set to “spam”.

However, both comments still ended up published, not flagged as spam.

So this sounds like something deeper is going on. As far as I know we’ve not got anything strange going on — it’s a normal version of WordPress, updated from the main site (so no custom adjustments to WP core files).

I guess the next step might be to see if the spam also gets through a fresh install of WordPress?

• This reply was modified 1 year, 6 months ago by Joe C. Reason: did some more testing
• This reply was modified 1 year, 6 months ago by Joe C.

Hi Robert,

Thanks for your reply! I’ll give that a try today and will let you know what transpires.

Thanks,
Joe

I just wanted to update this thread, as I also sent this question to the developers (Xootix) via email, and I received a speedy and helpful reply, which is welcome.

The plugin and add-ons do indeed work without WooCommerce, which is great.

I will continue to resolve my issue and will post here when complete, to help others in the future.

Thanks for the quick reply, that’s great to hear!

Just to add – I fixed it in the current version of wpDiscuz by copying the ‘placeholder’ attribute as an ‘aria-label’ attribute on line 858 of wpdiscuz/forms/wpdFormAttr/Form.php so it becomes:

<textarea id="wc-textarea-<?php echo esc_attr($uniqueId); ?>" placeholder="<?php echo esc_attr($textarea_placeholder); ?>" aria-label="<?php echo esc_attr($textarea_placeholder); ?>" required name="wc_comment" class="wc_comment wpd-field"></textarea>

I realise that this will be overwritten the next time wpDiscuz is updated! (Unless you are very fast at implementing this fix?)

• This reply was modified 3 years, 11 months ago by Joe C.