AntiSpam by CleanTalk

AntiSpam by CleanTalk 2.9

No permission to download
Going forward, please make it clear in your update descriptions which bugs have been resolved.

“Bug fixes” is lacking in detail and not in compliance with point 4 of the Resource standards.

 
Going forward, please make it clear in your update descriptions which bugs have been resolved.

“Bug fixes” is lacking in detail and not in compliance with point 4 of the Resource standards.


We've fixed description.
 
My users report that they are not seeing the custom error, but are only getting this error:
Screenshot_2020-05-03 20200502_225350 jpg (JPEG Image, 564 × 1600 pixels).webp
Yet, we pay for the functionality of showing a custom message that lets the user know what the problem is.
This results in many support tickets per week asking us what the problem is and how to address it.

Please fix this issue.

We are using XF1.5
 
My users report that they are not seeing the custom error, but are only getting this error:
View attachment 224047
Yet, we pay for the functionality of showing a custom message that lets the user know what the problem is.
This results in many support tickets per week asking us what the problem is and how to address it.

Please fix this issue.

We are using XF1.5
Thank you for your feedback.
We will investigate this issue as soon as possible and contact you when we get any results.
It may take up to 1-2 business days. Please, wait.
 
Hello,

Cleantalk module for xenforo is using built-in spam container, like any other anti-spam extension. In the current implementation, there are no possibilities to show custom messages for users. If you wanna cancel "Extra package" which also contains:
1) 45 days log
2) Stop words
3) Country black lists
4) Website access delegation

You can contact us at welcome@cleantalk.org or create a ticket here
 
I don't think this is correct. You see: when a user opens a support ticket with us, the custom message from CleanTalk is still in the users header. The ticket helpdesk by @NixFifty fetches that header and inserts it in the ticket. Its an unexpected result which is quite handy, because it gives us the information we need to answer the ticket:

Screenshot_2020-05-06 [#2255] Account Creation Help.webp


However, the fact that its in the users header, means that its available to display to the user. All that is needed is to display it on the page. Then the user doesn't have to open a support ticket because they already know the answer.

Displaying the message to users is very important, because thsi way they know they need to fix it. Currently CleanTalk blocks valid users from registering if they use a VPN. As long as they get a message on how to fix it this is a good thing. But blocking valid users from registering without letting them know why they are blocked is a very bad situation.

Please address this.
 
Hello @Alfa1

But blocking valid users from registering without letting them know why they are blocked is a very bad situation.

Could you give more information, CleanTalk always shows blocking reason.

It would be great if you send us feedback and mark the wrong filtration request in your anti-spam log. So, we will be able to investigate them to reduce a false/positive rate.

Please, open a private ticket https://cleantalk.org/my/support/open

Thank you!
 
This is what the user sees:
20200502_225350.webp
It should display the text that CleanTalk has sent in the browser header and is fetched by @NixFifty 's helpdesk and printed out in the ticket. @NixFifty could you tell us more about whats happening with the CleanTalk error ending up in the ticket footer?
 
Cleantalk sets cookies site wide. This is not needed as we only use it for registrations. The cookies make use of the samesite attribute, but this labeled by all major browser as misuse:

Cookie “ct_pointer_data” will be soon rejected because it has the “sameSite” attribute set to “none” or an invalid value, without the “secure” attribute. To learn more about the “sameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Cookies
 
Cleantalk sets cookies site wide. This is not needed as we only use it for registrations. The cookies make use of the samesite attribute, but this labeled by all major browser as misuse:

Cookie “ct_pointer_data” will be soon rejected because it has the “sameSite” attribute set to “none” or an invalid value, without the “secure” attribute. To learn more about the “sameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Cookies
Hello.

Thank you for your notice.

We'll investigate the issue and fix it within 2 days.

Please, wait.
 
Top Bottom