You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 28, 2019. It is now read-only.
Hi there,
I'm trying to create a blog with silverstripe-spamprotection and silverstripe-comments. The comments have 2 levels: comments and replies to comments. Since I want to protect the comments and their replies with recaptcha+spamprotection I'm using the CommentSpamProtection of silverstripe-spamprotection. But only the first captcha is rendered. I think it's due to the fact that multiple same HTML IDs are given to the containers and Google only renderes the captcha in the first container available.
Is there a way to get that working? Or can you confirm that multiple Recaptchas on one page are not supported by silverstripe-recaptcha + silverstripe-spamprotection + silverstripe-comments? Thanks for your reply
The text was updated successfully, but these errors were encountered:
I think multiple ReCaptcha on a single page won't work, unless they have the same fieldname. @chillu You have anything about this? I could check up with that as well while working on the SS4 version?
Hi there,
I'm trying to create a blog with silverstripe-spamprotection and silverstripe-comments. The comments have 2 levels: comments and replies to comments. Since I want to protect the comments and their replies with recaptcha+spamprotection I'm using the CommentSpamProtection of silverstripe-spamprotection. But only the first captcha is rendered. I think it's due to the fact that multiple same HTML IDs are given to the containers and Google only renderes the captcha in the first container available.
Is there a way to get that working? Or can you confirm that multiple Recaptchas on one page are not supported by silverstripe-recaptcha + silverstripe-spamprotection + silverstripe-comments? Thanks for your reply
The text was updated successfully, but these errors were encountered: