Title: Double Opt-In for Contact Form 7 & Avada – Secure, GDPR-Compliant Email Verification
Author: Forge12 Interactive GmbH
Published: 16, Avientu de 2022
Last modified: 14, Marzu de 2026
---
Guetar plugins
# Double Opt-In for Contact Form 7 & Avada – Secure, GDPR-Compliant Email Verification
By [Forge12 Interactive GmbH](https://profiles.wordpress.org/forge12/)
[Download](https://downloads.wordpress.org/plugin/double-opt-in.zip)
* [Details](https://ast.wordpress.org/plugins/double-opt-in/#description)
* [Reviews](https://ast.wordpress.org/plugins/double-opt-in/#reviews)
* [Installation](https://ast.wordpress.org/plugins/double-opt-in/#installation)
* [Development](https://ast.wordpress.org/plugins/double-opt-in/#developers)
[Support](https://wordpress.org/support/plugin/double-opt-in/)
## Description
**Double Opt-In** adds a mandatory email verification step to your Contact Form
7 and Avada forms.
When a visitor submits your form, the original mail is **not**
sent immediately. Instead, the plugin:
1. Stores the submission in a secure database table.
2. Sends a confirmation email with a unique, time-limited link.
3. Only after the visitor clicks that link is the original form mail delivered.
This ensures:
* Only **valid, verified email addresses** reach your inbox.
* **GDPR / DSGVO requirements** are met with proper consent tracking, IP logging,
and data retention.
* Your database stays **clean and reliable** — no fake or mistyped addresses.
Seamless integration with **Contact Form 7** and **Avada Forms**.
Enable Double
Opt-In per form, customize confirmation emails with a visual editor, and manage
data retention with ease.
#### How It Works
1. A visitor fills out your Contact Form 7 or Avada form and clicks submit.
2. The plugin intercepts the submission, stores the form data, and generates a unique
hash.
3. A confirmation email is sent to the visitor’s email address containing a verification
link.
4. The visitor clicks the link. The plugin verifies the hash, marks the opt-in as
confirmed, and sends the original form mail (as if the form was just submitted).
5. The confirmed opt-in is logged in the admin dashboard with timestamps and IP addresses
for full GDPR compliance.
#### Quick Start
[Read the Quick Guide](https://www.forge12.com/blog/so-verwendest-du-das-double-opt-in-fuer-contact-form-7/)
#### Free Features
* **Visual Email Editor** — drag & drop block-based email template editor with
live preview and mobile preview
* **Double Opt-In for Contact Form 7** — per-form activation with full CF7 integration
* **Double Opt-In for Avada Forms** — works with Avada’s built-in form builder _(
Note: Moving to Pro in version 3.8.0)_
* **Centralized Form Settings** — manage all form integrations from a single admin
panel
* **Email Template Presets** — choose from pre-built templates or create your own
* **Send Test Email** — preview your confirmation emails before going live
* **Custom Confirmation Pages** — redirect users to a specific page after confirmation
* **Dynamic Conditions** — enable opt-in based on user input (e.g. only when a
checkbox is checked)
* **Resend Confirmation** — resend the confirmation email from the admin dashboard
* **Delete Confirmation Modal** — safety dialog before deleting an opt-in record
to prevent accidental deletion
* **GDPR Consent Export** — export individual consent records as JSON or CSV directly
from the opt-in detail view
* **CAPTCHA Compatibility** — automatically bypasses Forge12 Captcha, Google reCAPTCHA,
and hCaptcha during opt-in confirmation to ensure mail delivery
* **Rate Limiting** — configurable IP and email rate limits to prevent abuse
* **Error Redirect Page** — redirect users to a custom page when an opt-in error
occurs (rate limit, invalid email)
* **Token Expiry** — confirmation links expire after a configurable time period
* **GDPR Data Storage** — tracks Form ID, Email, Registration/Confirmation Date&
IP, Consent Text
* **GDPR Anonymization** — anonymize personal data instead of deleting it
* **WordPress Privacy Tools** — integrates with WordPress personal data export
and erasure requests
* **Automatic Cleanup** — configurable auto-deletion of confirmed and unconfirmed
entries
* **Category System** — organize opt-ins into categories for better management
* **Pagination & Search** — search and filter opt-in records in the admin dashboard
* **Admin Tooltips** — contextual help tooltips throughout the admin interface
* **WordPress Multisite** — network-wide activation creates tables on all sites
automatically
* **Developer Hooks** — 18 action hooks, 23 filters, and 11 typed events for full
extensibility
#### Pro Features
Unlock the full potential of Double Opt-In with the [Pro version](https://www.forge12.com):
**Additional Form Integrations:**
* **Double Opt-In for Elementor Forms** — seamless integration with Elementor’s
form widget
* **Double Opt-In for WPForms** — full support for WPForms submissions
* **Double Opt-In for Gravity Forms** — complete Gravity Forms integration
**Email Validation & Spam Protection:**
* **Unique Email Validation** — prevent duplicate submissions per email address(
block, silent, or redirect mode)
* **MX Validation** — verify that the email domain has a valid mail server before
sending
* **Domain Blocklist** — block disposable and temporary email domains
**Email & Communication:**
* **Double Opt-Out System** — unique opt-out links per submission with confirmation
emails
* **Opt-In Reminder System** — automatic reminders for unconfirmed opt-ins via
cron
* **Conditional Email Templates** — dynamic content blocks based on form data
* **Multi-Column Layouts** — 2-column, 3-column, and sidebar layouts in the email
editor
* **Image & Social Blocks** — add images and social media icons to your emails
**Analytics & Export:**
* **Analytics Dashboard** — charts and statistics for opt-in/opt-out rates
* **CSV Export** — export all opt-in records for external processing
**User Management:**
* **Auto User Creation** — automatically create WordPress users after opt-in confirmation
with configurable role assignment
**Support:**
* **Premium Support** — priority email support
### Privacy & Telemetry
Starting with version **3.1.0**, the Double Opt-In plugin includes **optional anonymous
telemetry** (opt-out).
This helps us understand which features are used most, so
we can improve usability and remove unused complexity.
**We never sell or share data.**
Telemetry is used **only for product improvement
and maintenance**.
#### Telemetry data collected
* `plugin_slug`, `plugin_version`
* `snapshot_date`
* `settings_json` (anonymized plugin settings)
* `features_json` (enabled features)
* `created_at`, `first_seen`, `last_seen`
* `counters_json` (opt-in/opt-out event counts)
* `wp_version`, `php_version`, `locale`
#### GDPR / DSGVO Compliance
* No personal data, no cookies, no user tracking.
* Legal basis: _Art. 6 Abs. 1 lit. f DSGVO_ (legitimate interest — plugin optimization).
* Telemetry is fully optional and can be disabled anytime in **Double Opt-In >
Settings**.
## Screenshots
* [[
* **Opt-In Dashboard** — Overview of all opt-in records with status, email, form,
date, and actions.
* [[
* **Form Settings** — Per-form configuration with sender, subject, recipient field,
confirmation page, and conditions.
* [[
* **Email Template Editor** — Visual drag & drop editor with blocks, live preview,
and mobile preview.
* [[
* **Template Presets** — Choose from pre-built email template designs.
* [[
* **Single Opt-In View** — Detailed view of an opt-in record with form data, timestamps,
and IP addresses.
* [[
* **Global Settings** — Configure data retention, token expiry, telemetry, and
opt-out settings.
* [[
* **Category Management** — Organize opt-in records into categories.
* [[
## Installation
#### Automatic Installation
1. Go to **Plugins > Add New** in your WordPress admin.
2. Search for **“Double Opt-In”**.
3. Click **Install Now** and then **Activate**.
#### Manual Installation
1. Download the plugin ZIP file.
2. Upload it to `/wp-content/plugins/double-opt-in/` or use **Plugins > Add New >
Upload Plugin**.
3. Activate via the WordPress **Plugins** menu.
#### First-Time Setup
1. After activation, go to **Double Opt-In** in the WordPress admin menu.
2. Navigate to **Forms** to see all detected Contact Form 7 and Avada forms.
3. Click on a form to enable Double Opt-In and configure the confirmation email.
4. Set the **Recipient Field** to the form field that contains the visitor’s email
address (e.g. `your-email`).
5. Customize the **Subject** and **Body** of the confirmation email, or choose a template
preset.
6. Save the settings and test the form.
#### Requirements
* WordPress 5.0 or higher
* PHP 8.0 or higher
* Contact Form 7 5.0+ and/or Avada 7.0+
## FAQ
### How does Double Opt-In work?
When a visitor submits your form, the plugin stores the submission and sends a confirmation
email with a unique link. The original form mail is only delivered after the visitor
clicks that link. This verifies that the email address is valid and belongs to the
person who filled out the form.
### Is this plugin GDPR / DSGVO compliant?
Yes. The plugin tracks all data required for GDPR compliance: consent text, registration
and confirmation timestamps, IP addresses, and form data. It integrates with WordPress
Privacy Tools for personal data export and erasure requests. You can configure automatic
data retention and anonymization policies.
### Which form plugins are supported?
The free version supports **Contact Form 7** and **Avada Forms**. The Pro version
adds support for **Elementor Forms**, **WPForms**, and **Gravity Forms**.
### Can I customize the confirmation email?
Yes. The plugin includes a visual drag & drop email editor with block-based design.
You can choose from pre-built template presets or create your own. Placeholders
like `[doubleoptinlink]`, `[doubleoptin_form_date]`, and form field values are replaced
automatically.
### What happens if the user does not confirm?
Unconfirmed opt-ins are stored in the database and can be cleaned up automatically.
You can configure the retention period for unconfirmed entries in the settings (
e.g. delete after 30 days). In the Pro version, you can also send automatic reminder
emails.
### Can I redirect the user to a specific page after confirmation?
Yes. In the per-form settings, you can select a **Confirmation Page**. The user
will be redirected there after clicking the confirmation link.
### Does the plugin work with CAPTCHA plugins?
Yes. The plugin automatically disables CAPTCHA validation (Google reCAPTCHA, hCaptcha,
CF7 Captcha by Forge12) when re-sending the original form mail after confirmation.
This prevents false spam detections during the confirmation step. CAPTCHA is re-
enabled immediately after the mail has been sent.
### Can I enable Double Opt-In only when a checkbox is checked?
Yes. Use the **Conditions** setting in the per-form configuration. Enter the name
of a form field (e.g. a checkbox). Double Opt-In will only be triggered when that
field has a value.
### How do I access form data after confirmation?
**Legacy approach (WordPress hook):**
```
add_action( 'f12_cf7_doubleoptin_after_confirm', function( $hash, $optIn ) {
$data = maybe_unserialize( $optIn->get_content() );
}, 10, 2 );
```
**Modern approach (typed event, since 4.0):**
Use `OptInConfirmedEvent` via the EventDispatcher. The event provides `getFormData()`,`
getEmail()`, `getFormId()`, and more. See `docs/hooks-and-events.md` for the complete
reference.
### Does it work with WordPress Multisite?
Yes. When activated network-wide, the plugin creates database tables on all existing
sites. New sites added to the network automatically get their own tables via the`
wp_initialize_site` hook.
### Can I use this without Contact Form 7 or Avada?
The free version requires at least one supported form plugin. However, developers
can register custom form integrations using the `f12_cf7_doubleoptin_register_integrations`
action hook. See the developer documentation for details.
### Where can I find the developer documentation?
The complete hook, filter, and event reference is available at `docs/hooks-and-events.
md` inside the plugin directory. It covers all 18 action hooks, 23 filters, and
11 typed events with code examples.
### How do I report a bug or request a feature?
Please visit [forge12.com](https://www.forge12.com) or contact us via the WordPress
support forum.
## Reviews
### [Great plugin.](https://wordpress.org/support/topic/great-plugin-41312/)
[evoratec](https://profiles.wordpress.org/evoratec/) 23, Febreru de 2026
Perfect plugin to avoid multiples entries on mail db. Great work.
### [Einfach zu bedienen ohne viel Schnickschnack](https://wordpress.org/support/topic/einfach-zu-bedienen-ohne-viel-schnickschnack/)
[satler](https://profiles.wordpress.org/satler/) 3, Febreru de 2026
Endlich mal ein Tool, welches von der Funktionalität das macht, was es soll.
### [Funktioniert](https://wordpress.org/support/topic/funktioniert-30/)
[lucafriedrich](https://profiles.wordpress.org/lucafriedrich/) 3, Avientu de 2025
Funktioniert alles und Support ist super kompetent und sympathisch
### [Works as promised, outstanding support](https://wordpress.org/support/topic/works-as-promised-outstanding-support/)
[jbraucker](https://profiles.wordpress.org/jbraucker/) 10, Payares de 2024
I tried this plug-in as I needed a simple double opt-in form and was already using
wpcf7 for other forms.Configuration was easy and the plug-in packs everything I
needed and more. It did not work at first, so I contacted the customer support and
did not expect much.To my surprise, they replied within hours, checked my configuration,
confirmed everything was right, took a backup of my website to investigate the issue
and then sent me a fix (which had to do with a change in wpcf7’s checkbox validation
through an update). All of that within a day.This is customer support at its best!
The amount of effort that went into fixing my problem and the fast replies were
exceptional. Thank you Marc Wagner and Forge12!
### [Perfect for a simple email subscription form with double opt-in](https://wordpress.org/support/topic/perfect-for-a-simple-email-subscription-form-with-double-opt-in/)
[James C](https://profiles.wordpress.org/jamescaws/) 8, Xineru de 2024
After some trial and then error with other more sophisticated plug-ins, I was delighted
to find this simple one does exactly what it says. It’s not trying to be fancy and
it integrates perfectly with Contact Form 7. I now have a simple email newsletter
sign-up form with double opt-in. Once the user confirms their email address via
the opt-in email request, the Contact Form 7 plug-in sends me an email with their
address, and sends the subscriber a thank-you email.
### [Does it’s job well!](https://wordpress.org/support/topic/does-its-job-well-39/)
[michacassola](https://profiles.wordpress.org/michacassola/) 15, Agostu de 2023
The double opt-in for Contact Form 7 works as expected. Really happy about this
plugin!
[ Read all 8 reviews ](https://wordpress.org/support/plugin/double-opt-in/reviews/)
## Contributors & Developers
“Double Opt-In for Contact Form 7 & Avada – Secure, GDPR-Compliant Email Verification”
is open source software. The following people have contributed to this plugin.
Contributors
* [ Forge12 Interactive GmbH ](https://profiles.wordpress.org/forge12/)
[Translate “Double Opt-In for Contact Form 7 & Avada – Secure, GDPR-Compliant Email Verification” into your language.](https://translate.wordpress.org/projects/wp-plugins/double-opt-in)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/double-opt-in/), check
out the [SVN repository](https://plugins.svn.wordpress.org/double-opt-in/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/double-opt-in/)
by [RSS](https://plugins.trac.wordpress.org/log/double-opt-in/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 3.7.2
**Bug Fixes:**
* Fix: Fixed all form field placeholders (`[doi_email]`, `[doi_name]`, `[doi_phone]`,
etc.) not being replaced in confirmation emails for Avada forms. The Avada integration
stores opt-in content in a nested structure (`{data: {...}, field_labels: {...}}`),
but the placeholder replacement expected a flat field array. The nested `data`
key is now extracted correctly before replacement.
* Fix: Applied the same nested content handling to the legacy `OptInFrontend::addPlaceholders()`
code path.
* Fix: Added missing `[doubleoptin_privacy_url]` system placeholder to the new `
AbstractFormIntegration::addSystemPlaceholders()` method. This placeholder was
available in the legacy code but was not ported to the 4.0.0 integration architecture,
causing it to appear unreplaced in emails.
* Fix: Fixed the admin opt-in detail view displaying Avada metadata keys (`data`,`
field_labels`, `field_types`, etc.) instead of actual form field values. The
nested content structure is now unwrapped before rendering.
* Fix: Fixed the AJAX opt-in detail modal showing the same incorrect metadata for
Avada opt-ins.
#### 3.7.1
**Bug Fixes:**
* Fix: Fixed the toggle switch in the admin form list showing an incorrect state
for forms with custom conditions. The `getForms()` method used the runtime `isOptInEnabled()`
check (which evaluates `$_GET['optin']` and `$_POST` condition fields) instead
of reading the stored database value. This caused the toggle to display as “off”
even when DOI was enabled, and clicking “enable” would actually disable it.
* Fix: Fixed Avada forms ignoring Double Opt-In settings entirely. The conditions
check in `isOptInEnabled()` looked for form field values in `$_POST[$condition]`,
but Avada sends form data inside `$_POST['formData']` as a URL-encoded string.
The `AvadaIntegration` now overrides `isOptInEnabled()` to parse Avada’s POST
format correctly.
* Fix: Fixed Avada forms showing “No valid email address was found” error on submission.`
AvadaIntegration::resolveRecipient()` did not strip square brackets from the
recipient field name (e.g. `[email]` `email`), so the field was never matched
in the form data. Now uses the same bracket-stripping logic as `CF7Integration`.
**Announcements:**
* Notice: Starting with version 3.8.0, Avada Forms integration will move to the
Pro version. Contact Form 7 support remains free.
* New: Dismissible admin notice for sites with active Avada/Fusion Builder, informing
about the upcoming change.
* New: Yellow info banner on the Forms management page in the Avada section.
* New: Plugin update message warning when Avada is active.
#### 3.7.0
**Bug Fixes:**
* Fix: Fixed `.doi-table` not using full width on admin pages due to conflicting
CSS rules. Table width now uses `!important` to ensure consistent layout.
**Compatibility:**
* Updated: Full compatibility with Pro version 3.7.0 and its new license management
system.
#### 3.6.0
**Architecture:**
* Moved: Consent export (CSV/JSON) is now a Pro-only feature. The `ConsentExportController`
and `ConsentExportService` have been removed from the free plugin and moved to
the Pro plugin.
* Security: The `doi_export_consent` AJAX endpoint is no longer registered in the
free plugin, preventing unauthorized access without a Pro license.
* New: Added `f12_doi_database_page_after_forms` action hook on the Database admin
page, allowing extensions to render additional UI after the built-in database
management forms.
#### 3.5.0
**Bug Fixes:**
* Fix: Fixed confirmation mail not being sent after opt-in verification for forms
using Quiz fields (`[quiz]`), Acceptance checkboxes (`[acceptance]`), or other
validated field types. CF7 re-ran all form validations when creating a `WPCF7_Submission`
instance during confirmation, which failed because quiz answers and checkbox
states are not available in a GET request context. Validation is now bypassed
during confirmation mail delivery.
* Fix: Applied the same validation bypass to the legacy `CF7Frontend::sendDefaultMail()`
code path, which had the same issue.
**Improvements:**
* Improved: `beforeSendConfirmationMail()` now disables CF7 field validation (`
wpcf7_validate`), spam detection (`wpcf7_spam`), and spam check (`wpcf7_skip_spam_check`)
in addition to the existing CAPTCHA bypasses. All filters are properly restored
in `afterSendConfirmationMail()`.
#### 3.4.0
**Bug Fixes:**
* Fix: Fixed translation loading too early warning on WordPress 6.7+ (`_load_textdomain_just_in_time`
notice).
* Fix: Fixed review notice never displaying due to namespace resolution issue.
* Fix: Fixed Free and Pro plugin constant/function redeclaration conflicts when
both plugins are active simultaneously.
* Fix: Fixed TestEmailBlocker fatal error in distribution builds where test dependencies
are not included.
* Fix: Fixed Pro upgrade prompt (“Pro Feature”, “The ‘{block}’ block requires the
Pro version.”) displaying in English instead of the active language.
* Fix: Fixed database “table doesn’t exist” error for `f12_cf7_doubleoptin_categories`
when plugin files are uploaded manually or the database is restored without custom
tables.
**Improvements:**
* Improved: Added 133+ missing German translations covering the Email Editor, Placeholder
Mapping, Email Template Post Type, Email Presets, and Pro upgrade prompts.
* Improved: Added formal German (Sie) translations for all new strings.
* Improved: Database table existence safety net — both custom tables are now verified
and recreated on every update cycle, independent of the activation hook.
* Improved: Updated “Upgrade to Pro” links to point to the correct product page.
#### 3.3.0
**New Features:**
* New: Delete confirmation modal — clicking “Delete DOI” now opens a confirmation
dialog to prevent accidental deletion. Dismissible via Cancel, overlay click,
or Escape key.
* New: GDPR consent record export — export individual opt-in records as JSON or
CSV directly from the opt-in detail view.
* New: Admin tooltips — contextual help tooltips with descriptions throughout the
admin interface.
* New: Error redirect page — configure a per-form redirect page for opt-in errors(
rate limit, invalid email, etc.).
* New: hCaptcha compatibility — hCaptcha validation is now automatically bypassed
during opt-in confirmation mail delivery, alongside Forge12 Captcha and Google
reCAPTCHA.
**New Features (Pro):**
* New: Unique Email – Redirect behavior. When a duplicate email is detected, users
can now be redirected to a configurable WordPress page instead of just seeing
an error or silent rejection.
* New: Dedicated Redirect Page selector in the Unique Email settings (per-form).
Only visible when behavior is set to “Redirect to page”.
* New: `UNIQUE_EMAIL_DUPLICATE` error code for distinguishing duplicate email rejections
from other validation errors (e.g. MX check).
**Bug Fixes:**
* Fix: Success and error messages (e.g. “Opt-In deleted”) are now rendered as styled
alerts instead of plain text.
* Fix: Fixed a typo in `OptInFrontend::afterSendDefaultMail()` that prevented Google
reCAPTCHA from being re-enabled after opt-in confirmation mail delivery (`wpcf7_recaptcha_verifiy_response``
wpcf7_recaptcha_verify_response`).
* Fix: Silent mode for Unique Email no longer shows the raw string `unique_email_rejected`
in the toast notification. It now displays a properly translated message.
* Fix: CF7 no longer sends its default success mail when a duplicate email is detected.
The original mail is now correctly blocked via `wpcf7_skip_mail`.
* Fix: CF7 now shows an inline error message (instead of the success message) when
Unique Email rejects a submission in block or redirect mode.
* Fix: WPForms and Gravity Forms no longer display a contradictory success confirmation
when a validation error occurs. The confirmation message is automatically hidden
and replaced by the error toast or redirect.
* Fix: Elementor Forms now correctly validate unique emails. The `f12_cf7_doubleoptin_validate_recipient`
filter was not called in the legacy `OptInFrontend::maybeCreateOptIn()` path
used by Elementor, so duplicate emails were never detected.
* Fix: Elementor success messages are now hidden when a validation error (block/
redirect) occurs, preventing contradictory success and error messages.
* Fix: Error notification AJAX polling no longer loops infinitely. The internal`
doi_check_submission_error` request was intercepted by its own XHR hook, causing
a continuous polling cycle every ~800ms.
**Improvements:**
* Improved: Updated translations (German, German formal, French, English).
* Improved: CAPTCHA bypass now covers Forge12 Captcha, Google reCAPTCHA, and hCaptcha
across all three bypass layers (SpamMechanics, AbstractFormIntegration, OptInFrontend).
* Improved: ErrorNotification system now stores a `hide_confirmation` flag based
on the validation error behavior (block/redirect vs. silent). The frontend uses
this to hide form-plugin success messages when an error should be visible.
* Improved: Error handling in CF7 integration prevents mail sending for all rejection
modes (block, silent, redirect).
* Improved: `OptInFrontend::maybeCreateOptIn()` now calls the `f12_cf7_doubleoptin_validate_recipient`
filter, enabling MX validation, domain blocklist, and unique email checks for
all legacy form integrations (Elementor).
**Testing:**
* New: Unit tests for SpamMechanics (10 tests) — verifies CAPTCHA bypass for Forge12
Captcha, Google reCAPTCHA, and hCaptcha, including guard conditions (no hash,
invalid hash, already confirmed).
* New: E2E tests for delete confirmation modal (7 tests) — verifies modal open/
close behavior (Cancel, overlay click, Escape), re-open, correct delete URL,
and red button styling.
#### 3.2.4
**New Features:**
* New: Universal Error Notification System – displays a toast notification to the
user when an OptIn error occurs (rate limit, invalid email, etc.), independent
of the form plugin used.
* New: Error Redirect Page – configure a per-form redirect page for OptIn errors.
When set, users are redirected to the selected page instead of seeing a toast
notification. The error code is appended as a query parameter (`?doi_error=rate_limit_ip`)
for context-specific content.
* New: OptInError value object for typed, translatable error codes across all integrations.
**Improvements:**
* Improved: Error handling in all form integrations now uses the centralized OptInError
and ErrorNotification system.
* Improved: Frontend error detection covers Contact Form 7, WPForms, Gravity Forms,
Avada, Elementor, and generic AJAX/form submissions.
#### 3.2.3
**Bug Fixes:**
* Fix: Fixed broken toggle switches on the settings page. Clicking the toggle button
or its label text now correctly toggles the value.
* Fix: Removed stale `