Krzysztof Busłowicz

[This plugin is outdated and no longer maintained. Please use the much easier Honeypot for CF7 instead.]
Adds double opt-in functionality to CF7 forms submissions. Double opt-in means that form submitters have to confirm their identity by their email account. The plugin is ready for translation.
Double opt-in dependencies
This plugin is an add-on to <a href="https://wordpress.org/plugins/contact-form-7/" rel="ugc">Contact Form 7</a> plugin by Takayuki Miyoshi. 
Functionality of this plugin also depend on installing and activating one of the plugins, which saves Contact Form 7 submissions to WordPress database. At the time, compatible plugins are:
<ul>
<li><a href="https://wordpress.org/plugins/flamingo/" rel="ugc">Flamingo</a> by Takayuki Miyoshi</li>
<li><a href="https://wordpress.org/plugins/contact-form-cfdb7/" rel="ugc">Contact Form 7 Database Addon – CFDB7</a> by Arshid</li>
</ul>
Note that BOTH Contact Form 7 and one of the listed above plugins are required for double opt-in functionality to work.
Help and Docs
The first and most complete documentation is located on <a href="https://sirta.pl/double-opt-in-for-contact-form-7-documentation/" rel="nofollow ugc">plugin official page</a>. 
If you’re a developer, feel free to take a look at <a href="https://github.com/elkurczako/Double-Opt-in-for-CF7" rel="nofollow ugc">the plugin page on GitHub repository</a>. 
You can also seek for help on WordPress support forum.
Plugin features
<ul>
<li>One click conversion of existing CF7 forms into double opt-in enabled forms.</li>
<li>URL parameters encryption to make confirmation links safe.</li>
<li>HTML email templates with mail tags similar to used in CF7 plugin. If you know how to configure CF7 emails, double opt-in will be easy.</li>
<li>Automatic creation of the “opt-in” page to process confirmed submissions.</li>
<li>Adding a CSV file attachment to final submission email containing form data.</li>
<li>Adding file attachment to final confirmation email sent to the submitter.</li>
<li>Setting expiration time for submissions to be confirmed.</li>
<li>Ability to manually confirm forms. That can be useful if your submitter enters an invalid email address, and you are sure you want to send their submission anyway.</li>
</ul>
Additional enhancements
Apart from its main feature, Double Opt-in for CF7 adds some functions you may find nice and useful:
<ul>
<li>Custom, accessible file upload inputs for your forms which look better, can be CSS styled and allow easy selecting and deselecting files to upload. This works for every CF7 form, not only double opt-in enabled.</li>
<li>Custom, more specific validation errors for radio buttons and checkboxes for improved accessibility.</li>
<li>Option to change CSV separator when exporting submissions from Flamingo plugin. It also adds BOM to CSV exports, allowing them to be properly opened in MS Excel. </li>
<li>Additional column on Flamingo Inbound Messages screen indicating if submission is complete or still waiting for being confirmed by sender.</li>
</ul>
What is double opt-in and why use it:
Double opt-in is the safe way of receiving site visitor’s submitted input. Used with contact forms or online questionnaires or with user registration, it helps to reduce spam submissions. With GDPR laws, double opt-in is a strongly recommended way of getting user data. Because submitters have to confirm their identity from their email address, you can reduce risk of processing personal data without permission. Double – means here that user submitting the data has to give consent by checking checkbox option and additionally confirm their email-address. 
Do not forget to set acceptance field in your CF7 form if GDPR is in concern!
How Double opt-in form works:
When someone fills and submits a form with double opt-in functionality, the first CF7 email goes back to THEM. There is a confirmation link in that email, which the submitter has to click on or paste in their web browser. The link has two encrypted parameters: submission serial number and submitter email address. The page with “opt-in” slug validates the parameters with submission stored in WordPress database and initiates sending of final emails to recipient set in “All Opt-In Forms” settings. If validation fails or when submission has expired, no emails are sent. If there are no specified parameters in the URL, visitors of the “opt-in” page are redirected to “404” page.
Plugin translation
Double Opt-In can be easily translated. It is released with the translation to Polish language.

Double Opt-in for CF7

This plugin adds a double opt-in functionality to CF7 forms.

Marcin Kazmierski

<h4>What is “Theme and plugin translation for Polylang”?</h4>
Extension for Polylang plugin (Polylang is an extension to make multilingual WordPress websites.). 
Plugin is needed to translate the WordPress themes and plugins by Polylang.
<h4>How to configure it?</h4>
Select themes and plugins to find texts for translation by Polylang. 
In admin dashboard:
<pre><code>Languages -> TTfP Settings
</code></pre>
<h4>How it is work?</h4>
“Theme and plugin translation for Polylang” automatically searches all files of WordPress themes and plugins. It chooses from this file only those files with extensions:
<ul>
<li>php</li>
<li>inc</li>
<li>twig</li>
</ul>
In addition, is implemented the integration with Timber library (read more: http://timber.upstatement.com) – which allows to translate twig’s skins in simple way. 
Plugin in searched skins or plugins chooses texts from Polylang functions, such as:
<ul>
<li>_e(string $text, string $domain = ‘default’);</li>
<li>__(string $text, string $domain = ‘default’);</li>
<li>_x(string $text, string $context, string $domain = ‘default’);</li>
<li>pll_e(string $text);</li>
<li>pll__(string $text);</li>
<li>esc_html(string $text);</li>
<li>esc_html_e(string $text, string $domain = ‘default’);</li>
<li>esc_html__(string $text, string $domain = ‘default’);</li>
<li>_n(string $single, string $plural, int $number, string $domain = ‘default’);</li>
<li>esc_attr_e(string $text, string $domain = ‘default’);</li>
<li>esc_attr__(string $text, string $domain = ‘default’);</li>
</ul>
In your function.php, themes or plugins.
For example:
<pre><code><?php pll_e('My text'); ?>

<?php _e('My another text', 'my_theme'); ?>
</code></pre>
On the timber context declare this functions like:
<pre><code>$context['pll_e'] = TimberHelper::function_wrapper('pll_e');

$context['pll_'] = TimberHelper::function_wrapper('pll_');
</code></pre>
See more on: <code>https://polylang.wordpress.com/documentation/documentation-for-developers/functions-reference/</code> 
These functions are defined by Polylang plugin for printing translations. 
Thanks “Theme and plugin translation for Polylang” you can find these strings to translate and add to Polylang register on very simple way. 
And then you can translate these texts from the admin dashboard. 
The scan result can be seen on the tab with translations:
<pre><code>Settings -> Languages -> String translation
</code></pre>
or
<pre><code>Languages -> String translation
</code></pre>
You don’t need programs like poedit – you don’t change files with extensions like: <code>.pot</code>, <code>.po</code>, <code>.mo</code>. 
“Theme and plugin translation for Polylang” is highly efficient because the scanner is worked only on admin dashboard in tab: 
In dashboard:
<pre><code>Settings -> Languages -> String translation
</code></pre>
or
<pre><code>Languages -> String translation
</code></pre>
<h4>Export and import string translation</h4>
In dashboard:
<pre><code>Languages -> TTfP Settings
</code></pre>
<h4>Filter reference</h4>
<pre><code>ttfp_domains
</code></pre>
Allows plugins and themes (in functions.php) to modify list of text domains (unique identifier for retrieving translated strings). 
List of text domains is displayed on “TTfP Settings” page to select them for translation by polylang engine.
Example:
<pre><code>add_filter('ttfp_domains', 'custom_ttfp_domains', 10, 1);
function custom_ttfp_domains(array $domains):array
 {
 $domains[] = "my-custom-domain";
 return $domains;
 }
</code></pre>
<h4>Filter reference</h4>
<pre><code>ttfp_translation_access
</code></pre>
Returns whether the user has capability to view and edit translations provided by TTfP.
Example:
<pre><code>add_filter('ttfp_translation_access', 'custom_ttfp_translation_access', 10, 1);
function custom_ttfp_translation_access(bool $hasAccess):bool
 {
 return current_user_can('edit_posts');
 }
</code></pre>

Theme and plugin translation for Polylang (TTfP)


Great plugin and DEV, nothing more to say.


Great plugin and DEV


Works perfectly and very simple to use!


Works perfectly!

Theme and plugin translation using Polylang for WordPress. Extension for Polylang plugin.

Double Opt-in for CF7 vs Theme and plugin translation for Polylang (TTfP)