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.

Magazine3

VaLeXaR

WP Multilang is a multilingual plugin for WordPress.
Translations of post types, taxonomies, meta fields, options, text fields in miltimedia files, menus, titles and text fields in widgets.
<a href="https://wp-multilang.com/" rel="nofollow ugc">Home</a> | <a href="https://wp-multilang.com/contact-us/" rel="nofollow ugc">Help & Tech Support</a> | <a href="https://wp-multilang.com/docs/" rel="nofollow ugc">Documentation</a> | <a href="https://wp-multilang.com/#features" rel="nofollow ugc">Premium Features</a>
<h3>New Features of the plugin WP Multilang</h3>
<ul>
<li>Support full site editor for block based themes</li>
<li>Support block based widgets</li>
<li>Support different feature image for each language</li>
<li>Support Smart Custom Fields Plugin</li>
<li>Auto Translation ( <a href="https://wp-multilang.com/pricing/" rel="nofollow ugc">available in premium version</a> ) – <a href="https://wp-multilang.com/docs/knowledge-base/how-to-auto-translate-your-website-contents-using-wp-multilang/" rel="nofollow ugc">View Tutorial</a></li>
<li>Support URL Slug Translation ( <a href="https://wp-multilang.com/pricing/" rel="nofollow ugc">available in premium version</a> ) – <a href="https://wp-multilang.com/docs/knowledge-base/how-to-translate-url-slugs-with-selective-languages/" rel="nofollow ugc">View Tutorial</a></li>
<li>Support Base Translation ( <a href="https://wp-multilang.com/pricing/" rel="nofollow ugc">available in premium version</a> ) – <a href="https://wp-multilang.com/docs/knowledge-base/how-to-translate-taxonomy-bases-such-as-categories-and-tags-into-selective-languages-using-the-base-translation-option/" rel="nofollow ugc">View Tutorial</a></li>
<li>Export and import content in XLIFF or xml format to translate outside</li>
<li>Activate Multilingual Support for Post Types</li>
<li>Support Auto URL Slug Translation ( <a href="https://wp-multilang.com/pricing/" rel="nofollow ugc">available in premium version</a> ) – <a href="https://wp-multilang.com/docs/knowledge-base/how-to-translate-url-slugs-with-selective-languages/" rel="nofollow ugc">View Tutorial</a></li>
</ul>
<h3>Features of the plugin WP Multilang</h3>
<ul>
<li>100% free.</li>
<li>Translation at PHP.</li>
<li>Compatible with REST.</li>
<li>Support configuration for translate multidimensional arrays in options, meta fields, post content.</li>
<li>Support multisite.</li>
<li>Support WordPress in sub-folder.</li>
<li>Separate menu items, posts, terms, widgets, comments per language.</li>
<li>Many filters for dynamic applying translation settings.</li>
<li>No duplicate posts, terms, menus, widgets.</li>
<li>No sub-domain for each language version.</li>
<li>No additional tables in database.</li>
<li>Possibility set many languages with one localization. For example, for localization in the region.</li>
<li>Possibility to set custom locale for html(If installed locale is en_US, you can set locale like: en, en-UK, en-AU etc. Without installation another localization)</li>
<li>Possibility for add new languages for any user with capability <code>manage_options</code>.</li>
<li>Exist the role “Translator” for editing posts, terms. It can not publish or delete.</li>
<li>No limits by languages or by possibilities.</li>
</ul>
<h3>WP Multilang compatible with plugins</h3>
<ul>
<li>Elementor ( <a href="https://wp-multilang.com/pricing/" rel="nofollow ugc">available in premium version</a> ) – <a href="https://wp-multilang.com/docs/knowledge-base/how-to-build-a-multilingual-site-with-elementor-using-wp-multilang/" rel="nofollow ugc">View Tutorial</a></li>
<li>Divi Builder ( <a href="https://wp-multilang.com/pricing/" rel="nofollow ugc">available in premium version</a> ) – <a href="https://wp-multilang.com/docs/knowledge-base/how-to-build-a-multilingual-site-with-divi-builder-using-wp-multilang/" rel="nofollow ugc">View Tutorial</a></li>
<li>ACF, ACF Pro</li>
<li>WooCommerce</li>
<li>WooCommerce Customizer</li>
<li>Gutenberg</li>
<li>Yoast Seo</li>
<li>SEOPress </li>
<li>Contact Form 7 (added mail tag [_language] for send user language in mail)</li>
<li>WPBakery Visual Composer</li>
<li>Page Builder by SiteOrigin</li>
<li>NextGEN Gallery</li>
<li>All in One SEO Pack</li>
<li>MailChimp for WordPress</li>
<li>Newsletter</li>
<li>Maps Builder</li>
<li>Max Mega Menu</li>
<li>MasterSlider</li>
<li>WP-PageNavi</li>
<li>BuddyPress</li>
<li>Meta Slider</li>
<li>TablePress</li>
<li>Download Monitor (Redefine templates for links in your theme and translate link texts)</li>
<li>Better Search</li>
<li>Rank Math SEO (thanks for @pratikmts)</li>
<li>WPGraphQL (Add lang to the query parameters in URL. Eg: lang=en)</li>
<li>Smart Custom Fields</li>
<li>Team – Team Members Showcase Plugin</li>
<li>Schema & Structured Data for WP & AMP</li>
<li>Forminator Forms</li>
<li>Gravity Forms</li>
<li>Ultimate Member Form</li>
</ul>
<h3>Advance Woocommerce Support</h3>
<ul>
<li>Send emails in customer’s selected language</li>
<li>REST API Support</li>
<li>Import and export products in customer’s selected language</li>
<li>Translate products (simple products, variable products, grouped products), categories, tags, global attributes</li>
<li>Cart synchronization across multiple languages </li>
</ul>
Manage translation settings via json.
Add in the root of your theme or plugin file <code>wpm-config.json</code>.
Sample configurations can be viewed in config files in folder ‘configs’ in root the plugin.
Configuration is updated after switching theme, enable or update any plugins.
The plugin has filters for dynamic application configuration for translate.
For turn off translation, set <code>null</code> into the desired configuration. 
For example, you must turn off translation for a post type <code>post</code>. 
There are two ways:
<ol>
<li>
In json. 
Create in root of a theme or a plugin file <code>wpm-config.json</code> with: 
 { 
 “post_types”: { 
 “post”: null 
 } 
 }
</li>
<li>
Through the filter. 
Add in functions.php 
 add_filter( ‘wpm_post_post_config’, ‘__return_null’ );
</li>
</ol>
To enable translation pass an empty array in php <code>array()</code> or empty object in json <code>{}</code>.
Supports translation multidimensional array of options, meta fields and post_content. 
Supports the removal of established localizations. 
Supports translation via GET parameter. Add in the GET parameter <code>lang</code> code desired language. 
Supports clean database of translations when removing the plugin. Translations are only removed from the built-in tables. 
Supports import term translations from qTranslate(by Soft79). 
Supports automatically redirect to the user’s browser language, if he visits for the first time.
Ideal for developers.
For display language switcher in any place add the code to your template <code>if ( function_exists ( 'wpm_language_switcher' ) ) wpm_language_switcher ();</code> 
Function accepts two parameters: 
$type – ‘list’, ‘dropdown’, ‘select’. Default – ‘list’. 
$show – ‘flag’, ‘name’, ‘both’. Default – ‘both’.
Or using the shortcode <code>wpm_lang_switcher</code>. It accept two not necessary parameters ‘type’ and ‘show’.
Available features for translation: 
 wpm_translate_url( $url, $language = ” ); – translate url 
 wpm_translate_string( $string, $language = ” ); – translate multilingual string 
 wpm_translate_value( $value, $language = ” ); – translate multidimensional array with multilingual strings
Update translation occurs at PHP. Therefore plugin has high adaptability, compatibility and easily integrates with other plugins. This is what distinguishes it among similar.
Available translation html tags by JS for strings what do not have WP filters before output.
Add your tags in config:
<pre><code>"admin_html_tags": {
 "admin_screen_id": {
 "attribute": [
 "selector"
 ]
 }
}
</code></pre>
Where: 
 admin_screen_id – admin screen id. 
 attribute – attribute what need to translate. Available ‘text’ – for translate text node, ‘value’ – for translate form values. Or other tag attribute, like ‘title’, ‘alt’. 
 selector – css selector for search needed tag. Each selector is a new array item.
If You need to add translation for multidimentional array for repeated elements You can use custom tag ‘wpm_each’ for set config to each element in array. 
Example, add config for each item ‘title’ in custom post field array:
<pre><code>"post_fields": {
 "custom_field": {
 "wpm_each": {
 "title": {}
 }
 }
}
</code></pre>
For set translation uses the syntax: 
 [:en]Donec vitae orci sed dolor[:de]Cras risus ipsum faucibus ut[:]
Added shortcode for translate text in any place: 
 [wpm_translate][:en]Donec vitae orci sed dolor[:de]Cras risus ipsum faucibus ut[:][wpm_translate]
If You translate text in established language, add lang parameter: 
 [wpm_translate lang=”de”][:en]Donec vitae orci sed dolor[:de]Cras risus ipsum faucibus ut[:][wpm_translate]
Support translating from syntax qTranslate, qTranslate-X, WPGlobus etc.
Compatible with REST-API. 
Support transfer the required translation through option <code>lang</code> in the GET request to REST. 
Has the ability to keep recording the target language through the transmission parameter <code>lang</code> in the request.
<h3>Migration from qTranslate-X</h3>
<ol>
<li>Before installing/uninstalling, make database backup.</li>
<li>Deactivate qTranslate-X.</li>
<li>Install and activate WP Multilang.</li>
<li>Create in root of your theme file ‘wpm-config.json’.</li>
<li>Add all needed post types, taxonomies, options, fields to ‘wpm-config.json’. Setting from qTranslate-X not importing.</li>
<li>Import term names from qTranslate.</li>
<li>Check that everything is okay.</li>
<li>If everything is okay, remove qTranslate-X. If not, make screenshots of errors, restore database from backup and add support issue with your screenshots and description of errors.</li>
</ol>
<h3>Warning</h3>
Not compatible with: 
– WP Maintenance
<h3>Known issues</h3>
Function ‘get_page_by_title’ not working, because in title field are stored titles for all languages. Use function ‘wpm_get_page_by_title( $title )’ as solution.
NOTE: Because plugins have different ways of storing data, WP Multilang is not compatible with every single plugin out-of-the-box (mostly page builders). This may result in texts not being translatable or translations not being saved. Most of these issues can be resolved using the integration options (wpm-config.json or filters) of WP Multilang.
Please try WP Multilang in a test-environment before activating it on an existing production site and always make a backup before activating!
<a href="https://wp-multilang.com/" rel="nofollow ugc">Home</a> | <a href="https://wp-multilang.com/contact-us/" rel="nofollow ugc">Help & Tech Support</a> | <a href="https://wp-multilang.com/docs/" rel="nofollow ugc">Documentation</a> | <a href="https://wp-multilang.com/" rel="nofollow ugc">Premium</a>
<h3>Support</h3>
We try our best to provide support on WordPress.org forums. However, We have a special <a href="https://wp-multilang.com/contact-us/" rel="nofollow ugc">community support</a> where you can ask us questions and get help about your WP Multilang related questions. Delivering a good user experience means a lot to us and so we try our best to reply each and every question that gets asked.
<h3>Bug Reports</h3>
Bug reports for WP Multilang are <a href="https://github.com/ahmedkaludi/wp-multilang/issues" rel="nofollow ugc">welcomed on GitHub</a>. Please note GitHub is not a support forum, and issues that aren’t properly qualified as bugs will be closed.

WP Multilang – Translation and Multilingual Plugin

This plugin works great, I tested it on Wordpress 5.5.3, with my custom developed theme and my custom Gutenberg blocks. It just does not give confidence, when you see when it was last updated. If it does not have major issues, you can just change plugin and readme file and declare it compatible with 5.5.3.

Great plugin

I have a page with cpt and cf and the customer decided to translate the page very lately. I tried polylang, wpml, and similir ones and most of them are - why? - very expensive to fit our needs or they are not able to just handle some cf. And then i saw WP Multilang - fuck, this is really exactly what i needed. it works with WP 5.8.3 - just tested it and it works like a charm.. everything is just as one would expect it to be. Thank you soooo much

Just amazin

Multilingual plugin for WordPress. Go Multilingual in minutes with full WordPress support. Translate your site easily with this localization plugin.

Double Opt-in for CF7 vs WP Multilang – Translation and Multilingual Plugin