Use django-contact-form's builtin AkismetContactForm

[bmispelon]

The BaseContactForm in contact/forms.py has a custom clean_body() method that checks the message against the anti-spam service akismet. The docstring on that method seems to indicate that this method was copy/pasted from an old version of django-contact-form because the functionality was removed at some point.

However, it seems the functionality is builtin to the current version of django-contact-form: https://django-contact-form.readthedocs.io/en/latest/forms.html#django_contact_form.forms.AkismetContactForm

So we should be able to remove and simplify our code by using it.

[Mayank-Raj-Nitp]

Sir, I would like to do this. Please assign the issue to me.

[bmispelon]

Hi,

I've assigned you, but for reference you don't need to be assigned to an issue to work on it. It's enough to write a comment, so that others know you're working on it.

[ANISH-SR]

Hello! I'm too working on this issue. Here's my current plan:

1. Replace the custom 'clean_body()' method with the built-in 'AkismetContactForm' from the latest django-contact-form.
2. Update the 'BaseContactForm' to inherit from 'AkismetContactForm'.
3. Ensure all existing functionality is maintained, including custom fields and methods.
4. Update the form initialization in views to pass the request object correctly.

I'll submit a pull request with these changes once I've implemented and tested them. If anyone has any suggestions or concerns, please let me know. I'm open to feedback and guidance, especially regarding maintaining compatibility with the rest of the project.

Is there anything else I should consider before proceeding?

[ANISH-SR]

#1584 Hi @bmispelon, Could you please review this PR when you have a moment.
Thanks.
Edit: Really Sorry! for making the PR without addressing @MayankRaj-tech who is already assigned.

[RajuShivarama]

If the issue is still open, i would like to take it

[bmispelon]

If the issue is still open, i would like to take it

Hi and thanks for your interest. The issue is still open yes, but you can see from the history of this issue that there's already two people working on it, and one open pull request (which has some broken automated tests that need fixing).

The best way forward would be to collaborate with the current contributors in order to fix the broken tests in the existing pull request.

[thibaudcolas]

I see we have #1584 and now #1865. @RajuShivarama would you be up for reviewing them both and helping us figure out which one to go with? We’d like contributors to work together to address issues, doing the same work 2-3 times isn’t super fruitful.