Search by

hybridinteractive / craft-contact-form-extensions

hybridinteractive

Adds extensions to the Craft CMS contact form plugin.

Package info

github.com/hybridinteractive/craft-contact-form-extensions

Documentation

Type:craft-plugin

pkg:composer/hybridinteractive/craft-contact-form-extensions

Statistics

Installs: 104 056

Dependents: 1

Suggesters: 0

Stars: 42

Open Issues: 6

5.1.2 2026-11-13 22:58 UTC

README

Icon

Latest Version Total Downloads

Adds extensions to the Craft CMS Contact Form plugin.

  • Save submissions to the database and view them in the Control Panel
  • Filter submissions by spam status
  • Send a confirmation email to the submitting address
  • Overwrite the default notification email template
  • Export submissions as a flat CSV
  • Add invisible reCAPTCHA (v2 or v3)
  • Clear submissions by form from a Tools page

Screenshot

Support Open Source

This plugin is licensed under the MIT license.

Requirements

This plugin requires Craft CMS 5 and the Contact Form plugin (craftcms/contact-form ^3.0).

Installation

Install this plugin through the Plugin Store or follow these instructions.

  1. Open your terminal and go to your Craft project:

     cd /path/to/project
    
  2. Then tell Composer to load the plugin:

     composer require hybridinteractive/craft-contact-form-extensions
    
  3. In the Control Panel, go to Settings → Plugins and click the “Install” button for Craft Contact Form Extensions.

Overwriting the email templates

When you overwrite the email templates, your Twig view will receive a submission variable which contains all the information that a default Contact Form submission contains:

  • fromName
  • fromEmail
  • subject
  • message
  • attachment

submission.message still contains the hidden override and per-form fields described below (toEmail, confirmationTemplate, confirmationSubject, notificationTemplate, disableRecaptcha, disableConfirmation, disableSaveSubmission), so the overrides keep working. If your template loops over submission.message, skip those keys so their values don't end up in the email:

{% set hiddenKeys = ['toEmail', 'confirmationTemplate', 'confirmationSubject', 'notificationTemplate', 'disableRecaptcha', 'disableConfirmation', 'disableSaveSubmission'] %}
{% for key, value in submission.message|filter((v, k) => k not in hiddenKeys) %}
    <p><strong>{{ key }}:</strong> {{ value is iterable ? value|join(', ') : value }}</p>
{% endfor %}

When you don't overwrite the notification template, the plugin removes these fields from Contact Form's default email body. If another plugin or module replaces or edits the HTML body of that email, the HTML is left as it is, and that code should skip these keys too.

Overriding the form name

When saving submissions to the database the default form name will be "Contact". If you add a message[formName] hidden field you can override the form name. This can also used to create multiple form indexes in the Control Panel.

<input type="hidden" name="message[formName]" value="myFormName">

Overriding the confirmation template

When the confirmation option is enabled and custom templates per form are needed, override the template with a hashed hidden field. The template needs to be placed under templates/_emails. The same data is passed as in the default overridden template.

<input type="hidden" name="message[confirmationTemplate]" value="{{ 'contact'|hash }}">

Overriding the confirmation subject

When the confirmation option is enabled and custom subjects per form are needed, override the subject with a hashed hidden field.

<input type="hidden" name="message[confirmationSubject]" value="{{ 'confirmationSubject'|hash }}">

Overriding the notification template

When template overwrite is enabled and custom notification templates per form are needed, override the template with a hashed hidden field. The template needs to be placed under templates/_emails.

<input type="hidden" name="message[notificationTemplate]" value="{{ 'contact'|hash }}">

Overriding where the message is sent

<input type="hidden" name="message[toEmail]" value="{{ 'hello@rias.be'|hash }}">

Disable recaptcha on a per form basis

<input type="hidden" name="message[disableRecaptcha]" value="true">

Disable saving to database on a per form basis

<input type="hidden" name="message[disableSaveSubmission]" value="true">

Disable confirmation email on a per form basis

<input type="hidden" name="message[disableConfirmation]" value="true">

Adding invisible reCAPTCHA

Before you set your config, choose invisible reCAPTCHA while applying for keys (for v2).

Screenshot

Enable reCAPTCHA in the Contact Form Extensions settings and fill in your siteKey and secretKey.

Then use the following code in your forms inside of the <form> element:

{{ craft.contactFormExtensions.recaptcha | raw }}

ReCaptcha V3

To use ReCaptcha V3, choose the V3 option in the settings, make sure to enter a correct siteKey and secretKey and enter a threshold. Learn more about ReCaptcha V3

Then include the following code in your forms inside of the <form> element, for example for the homepage action (actions help separate out reCaptcha submissions within the reCaptcha console):

{{ craft.contactFormExtensions.recaptcha('homepage') | raw }}

Display form submissions in your template files

{% for submission in craft.contactFormExtensions.submissions %}
   {{ submission.dateCreated|date('d-m-Y H:i') }} - {{ submission.fromEmail }} - {{ submission.fromName }}
{% endfor %}

Brought to you by Hybrid Interactive