[MGNLFORM-210] Pluggable Spam detection mechanism for all form technologies (form, PUR, forum, commenting) Created: 05/Dec/13  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia Form Module
Component/s: field, hidden field, validation
Affects Version/s: 2.2
Fix Version/s: None

Type: Story Priority: Major
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLFORM-178 Form's Honeypot anti-spam - needed im... Closed
relates to MGNLCMNT-27 Akismet spam filtering Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

Form currently implements a "Honey Pot" technique to block spam. But some clients, may require another technique (such as akismet).
The form technogies should support a pluggable mechanism to implement custom spam handling logic.

Some pluggable technologies might be:

  • custom captcha
  • recaptcha
  • akismet

See Concept:http://wiki.magnolia-cms.com/display/DEV/Spam+handling



 Comments   
Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

Generated at Mon Feb 12 05:37:57 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.