+
+
+
+
+
+
+
+Extending functionality
+Examples
+Testing your application
+Antispam measures are all fine and great, until you start to write functional tests for your application and you
+discover after hours of debugging that all your form submissions are failing because your tests are actually behaving
+exactly like spambots on your own application, and being stopped by this bundle.
+It is recommended to disable the entire bundle when testing in the config:
+
| config/packages/antispam.yaml |
|---|
| when@test:
+ antispam:
+ enabled: false
+
|
| use Omines\AntiSpamBundle\AntiSpam;
+
+$antispam = static::getContainer()->get(AntiSpam::class);
+$antispam->enable();
+
|
“Fake pass”
+A spammer who sees success is a happy spammer. One of the problems we have to cope with these days is that some people
+actually consider it an effective strategy to pay people to randomly fill in forms on the internet. If actual people see
+their spam is rejected, they might actually want to try again. Let’s discourage that.
+To lure the spammer into believing their spam was accepted and is going to be read, we have to enable passive mode on
+the form profile:
+ | antispam:
+ profiles:
+ my_form:
+ passive: true
+
+ # Rest of your configuration
+
|
AntiSpam class!
+ | #[Route('/contact')]
+public function fakeSuccess(Request $request): Response
+{
+ $form = $this->createForm(ContactForm::class, options: [
+ 'antispam_profile' => 'my_form',
+ ]);
+ $form->handleRequest($request);
+ if ($form->isSubmitted() && $form->isValid()) {
+ if (!AntiSpam::isSpam()) {
+ // Only send an actual email if the form did not trigger
+ // spam detections!
+ $this->sendEmailTo('site-owner@example.org', $form->getData();
+ }
+ $this->addFlash('message', 'Form passed');
+ }
+
+ return $this->render('form.html.twig', [
+ 'form' => $form->createView(),
+ ]);
+}
+
|