draft2live

<p><strong>Draft2Live Connect</strong> is the official bridge between your WordPress site and <a href="https://draft2live.ai" rel="nofollow ugc">Draft2Live</a>, an AI content generation platform that helps you research, plan, write and publish long-form SEO articles at scale.</p>
<p>Once the plugin is installed and your site is paired with your Draft2Live account, you can:</p>
<ul>
<li>Publish articles generated in Draft2Live straight to WordPress without leaving the dashboard</li>
<li>Keep content in sync both ways — edits made in WordPress flow back to Draft2Live automatically</li>
<li>Assign categories, tags, featured images and authors at publish time</li>
<li>Schedule publications for a future date (handled by Draft2Live’s unified scheduler, so it works exactly the same for WordPress and Drupal)</li>
<li>Publish multilingual content and link translations automatically if your site uses <a href="https://wordpress.org/plugins/polylang/" rel="ugc">Polylang</a> or <a href="https://wpml.org/" rel="nofollow ugc">WPML</a></li>
<li>Write SEO meta title / meta description / focus keyword through <a href="https://wordpress.org/plugins/wordpress-seo/" rel="ugc">Yoast SEO</a> or <a href="https://wordpress.org/plugins/seo-by-rank-math/" rel="ugc">Rank Math</a> when one of them is active</li>
</ul>
<p><strong>One-click secure pairing.</strong> No copy-pasting site IDs or secrets. The plugin uses WordPress’s native <a href="https://make.wordpress.org/core/2020/11/05/application-passwords-integration-guide/" rel="nofollow ugc">Application Passwords</a> flow — click <strong>Connect to Draft2Live</strong> in the plugin settings, approve the Application Password in the standard WordPress prompt, and the pairing completes automatically.</p>
<p><strong>You stay in control.</strong> Draft2Live never receives your WordPress login password. You can revoke access at any time by deleting the Application Password under <strong>Users <span aria-hidden="true" class="wp-exclude-emoji">→</span> Profile <span aria-hidden="true" class="wp-exclude-emoji">→</span> Application Passwords</strong>, or by deactivating the plugin.</p>
<p><strong>Open source.</strong> The plugin source is available on our <a href="https://draft2live.ai" rel="nofollow ugc">website</a> under the GPL v2 license.</p>
<h3>External services</h3>
<p>This plugin connects to Draft2Live — the SaaS backend that generates and manages your articles — so that your site can receive published content and keep it in sync. No data is sent until you explicitly pair the site.</p>
<p><strong>Service:</strong> Draft2Live<br />
<strong>Homepage:</strong> https://draft2live.ai<br />
<strong>Terms of Service:</strong> https://draft2live.ai/en/terms<br />
<strong>Privacy Policy:</strong> https://draft2live.ai/en/privacy</p>
<p><strong>What is sent and when:</strong></p>
<ul>
<li><strong>During pairing (one time, user-initiated):</strong> the plugin generates a WordPress Application Password via the standard WordPress flow and sends it to Draft2Live’s <code>/api/v1/sites/wp-callback</code> endpoint so the SaaS can authenticate future publish requests against your site.</li>
<li><strong>When a post that originated from Draft2Live is updated, trashed, untrashed or permanently deleted:</strong> the plugin sends a signed webhook to <code>https://<your-draft2live-instance>/api/v1/sites/webhook/{site_id}</code> containing the post ID, the internal Draft2Live article ID, the post title, the new post status and the modification timestamp. The webhook body is signed with HMAC-SHA256 using the secret established during pairing.</li>
<li><strong>When Draft2Live publishes or updates an article on your site:</strong> Draft2Live calls the plugin’s REST endpoints (<code>/wp-json/draft2live/v1/publish</code>, <code>/wp-json/draft2live/v1/posts/{id}</code>, etc.) authenticated with the Application Password stored during pairing. Featured images and in-content images/videos referenced in the article payload are downloaded from the URL included in the payload into your WordPress media library — URLs are validated with <code>wp_http_validate_url()</code> before any fetch.</li>
</ul>
<p><strong>What is not sent:</strong></p>
<ul>
<li>Visitor information, analytics or tracking data</li>
<li>Your WordPress admin password (the plugin never receives it — Application Passwords are a one-way secret generated by WordPress itself)</li>
<li>Anything about posts that did not originate from Draft2Live</li>
</ul>
<p>You can stop all communication at any time by revoking the Application Password under <strong>Users <span aria-hidden="true" class="wp-exclude-emoji">→</span> Profile <span aria-hidden="true" class="wp-exclude-emoji">→</span> Application Passwords</strong>, or by deactivating / uninstalling the plugin.</p>


Draft2Live Connect

Publish AI-generated articles from Draft2Live to WordPress in one click, with two-way sync and multilingual support (Polylang, WPML).

Aurovrata Venet

<p><strong>NOTE</strong> v2 is now an extension of the <a href="https://wordpress.org/plugins/cf7-grid-layout/" rel="ugc">CF7 Smart Grid-layout</a> plugin.  You need to install it to use this plugin.  Why is this? You can read this <a href="https://wordpress.org/support/topic/not-compatible-with-cf7-v5/#post-9973288" rel="ugc">thread</a>, and this <a href="https://wordpress.org/support/topic/why-i-wrote-this-plugin-2/" rel="ugc">post</a>.<br />
This plugin allows multilingual contact form 7 management using the polylang plugin. As of version 2.0 of this plugin, it is now developed as an extension of the <a href="https://wordpress.org/plugins/cf7-grid-layout/" rel="ugc">CF7 Smart Grid-layout</a> plugin.  All 3 plugins, Polylang, CF7 Smart Grid-layout and Contact Form 7 need to be installed prior to installing this plugin.  Works with multisite installations too.</p>
<ul>
<li>Now you can use a single CF7 form shortcode for all your translations.</li>
<li><strong>WARNING</strong>: ensure you follow the installation instructions along with the PolyLang settings adjustments.</li>
</ul>
<h4>Make your CF7 Form more portable</h4>
<p>this plugin introduces form keys (which you can modify in the CF7 admin table).  Keys are unique for each form, allowing you identify a form my its key rather than an ID.  Why is this priceless?  IDs changes from one server to the next because they are the custom post ID attributed by the WordPress installation, and therefore you develop your form in a local machine only to find out that the IDs are different when you move your form to your production server.  To overcome this problem, we suggest you use a form key along with this plugin’s contact form shortcode, <code>[cf7-form key="contact-us"]</code>.  Don’t worry your old contact form 7 shortcodes will still work too, behind the scenes we simply map the key to the ID and call the regular contact form 7 shortcode.</p>
<p>Similarly you can use any translated form shortcode, and the plugin will make sure the right language is loaded.</p>
<p>Please follow the <a href="https://wordpress.org/plugins/cf7-polylang/installation/" rel="ugc">Installation</a> instructions carefully, especially the part about saving your Polylang settings after you have activated this plugin.</p>
<p>English subtitled video on youtube, <a href="https://www.youtube.com/embed/0IJsPGSpYog?cc_load_policy=1&rel=0&showinfo=0&hl=es" rel="nofollow ugc">Spanish</a> & <a href="https://www.youtube.com/embed/0IJsPGSpYog?cc_load_policy=1&rel=0&showinfo=0&hl=fr" rel="nofollow ugc">French</a> subtitles available in the caption settings.</p>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/0IJsPGSpYog?version=3&rel=0&showsearch=0&showinfo=0&iv_load_policy=1&fs=1&hl=en-US&autohide=2&start=83&cc_load_policy=1&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span>
<h4>Checkout our other CF7 plugin extensions</h4>
<ul>
<li>
<p><a href="https://wordpress.org/plugins/cf7-polylang/" rel="ugc">CF7 Polylang Module</a> – this plugin allows you to create forms in different languages for a multi-language website.  The plugin requires the <a href="https://wordpress.org/plugins/polylang/" rel="ugc">Polylang</a> plugin to be installed in order to manage translations.</p>
</li>
<li>
<p><a href="https://wordpress.org/plugins/cf7-multislide/" rel="ugc">CF7 Multi-slide Module</a> – this plugin allows you to build a multi-step form using a slider.  Each slide has cf7 form which are linked together and submitted as a single form.</p>
</li>
<li>
<p><a href="https://wordpress.org/plugins/post-my-contact-form-7/" rel="ugc">Post My CF7 Form</a> – this plugin allows you to save you cf7 form submissions to a custom post, map your fields to meta fields or taxonomy.  It also allows you to pre-fill fields before your form  is displayed.</p>
</li>
<li>
<p><a href="https://wordpress.org/plugins/cf7-google-map/" rel="ugc">CF7 Google Map</a> – allows google maps to be inserted into a Contact Form 7.  Unlike other plugins, this one allows map settings to be done at the form level, enabling diverse maps to be configured for each forms.</p>
</li>
<li>
<p><a href="https://wordpress.org/plugins/cf7-grid-layout/" rel="ugc">Smart Grid-Layout Design for CF7</a> – allows responsive grid layout Contact Form 7 form designs, enabling modular designs of complex forms, and rich inter-linking of your CMS data with taxonomy/posts populated dynamic dropdown fields.</p>
</li>
</ul>
<h4>Thanks to</h4>
<p>Gérard Mathiuet for providing a fix for PolylangPro.<br />
Peter J. Herrel for improving the language folder management.<br />
Didier (@swissspaceboy) for pointing out an <a href="https://wordpress.org/support/topic/mailtag-_site_url-is-not-returning-the-localized-homepage-url/" rel="ugc">issue</a> with the CF7 Special Mail tag <code>[_site_url]</code>.</p>
<h4>Privacy Notices</h4>
<p>This plugin, in itself, does not:</p>
<ul>
<li>track users by stealth;</li>
<li>write any user personal data to the database;</li>
<li>send any data to external servers;</li>
<li>use cookies.</li>
</ul>
<h3>2.5.0</h3>
<ul>
<li>introduce ‘cf7pll_sync_form_metakeys’ to filter the synchronised form metakeys between translations.</li>
<li>improve translation sync from original post.</li>
</ul>
<h4>2.4.1</h4>
<ul>
<li>fix language update.</li>
<li>add notice to post-new pages.</li>
</ul>
<h4>2.4.0</h4>
<ul>
<li>enable other plugins to add their translation files.</li>
<li>added ‘cf7pll_load_plugin_translation_resource’ filter.</li>
</ul>
<h4>2.3.4</h4>
<ul>
<li>fix broken translations of new form templates.</li>
</ul>
<h4>2.3.3</h4>
<ul>
<li>fix ZipArchive class missing Fatal error for PHP 7.3 onwards.</li>
</ul>
<h4>2.3.2</h4>
<ul>
<li>fix continue warning.</li>
</ul>
<h4>2.3.1</h4>
<ul>
<li>clean up deprecated delete posts code.</li>
</ul>
<h4>2.3.0</h4>
<ul>
<li>added hidden field _wpcf7_lang to front-end form.</li>
<li>instroduce special mail tag [_home_url].</li>
</ul>
<h4>2.2.0</h4>
<ul>
<li>fix for CF7 bug on special mail tag _site_url.</li>
</ul>
<h4>2.1.1</h4>
<ul>
<li>fix notices.</li>
<li>improved translations</li>
</ul>
<h4>2.1.0</h4>
<ul>
<li>allows plugin update without cf7 smart grid, but restricted functionality.</li>
</ul>
<h4>2.0.1</h4>
<ul>
<li>removed empty front-end css/js from script queue.</li>
</ul>
<h4>2.0.0</h4>
<ul>
<li>major update to plugin to integrate with WP std admin pages for cf7 offered by cf7 smart grid plugin.</li>
<li>code update to fix issue with polylang v2.3+ changes.</li>
</ul>


Contact Form 7 Polylang Module

Thankfully this Plugin is here to rescue CF7 Forms when using Polylang for translations.

Good to have

This plugin allows multilingual contact form 7 management using the polylang plugin.

Draft2Live Connect vs Contact Form 7 Polylang Module