frontelf

<p>FrontElf Fields Bridge for Contact Form 7 provides an ACF and SCF integration for Contact<br />
Form 7. It adds ACF field groups directly to each Contact Form 7 form editor.</p>
<p>The plugin adds the Contact Form 7 form post type to the ACF location rules.<br />
Field groups assigned to that post type are shown in a dedicated tab in the<br />
Contact Form 7 editor and saved together with the form. This allows developers<br />
to store editable metadata and settings for each form.</p>
<p>The plugin supports Advanced Custom Fields and Secure Custom Fields. Contact<br />
Form 7 and one of those field plugins must be installed and active.</p>
<h3>Documentation</h3>
<h4>Assign fields to Contact Form 7</h4>
<p>After activating the plugin, a new <code>Contact Form (CF7)</code> option appears in the<br />
ACF or SCF field group location rules under <code>Post Type</code>.</p>
<ol>
<li>Open the ACF or SCF field group editor.</li>
<li>Add the fields that should belong to each Contact Form 7 form.</li>
<li>In the location rules, select <code>Post Type</code> <code>is equal to</code> <code>Contact Form (CF7)</code>.</li>
<li>Save the field group.</li>
<li>Open a Contact Form 7 form and use the <code>Fields for form</code> tab.</li>
</ol>
<p>If no matching field groups exist, the <code>Fields for form</code> tab provides a button<br />
to create one.</p>
<h4>Retrieve field values in a theme or plugin</h4>
<p>Each saved Contact Form 7 form has a numeric WordPress post ID. The plugin shows<br />
this ID above the fields in the <code>Fields for form</code> tab.</p>
<p>Use the form ID as the second argument of <code>get_field()</code>:</p>
<pre><code>$value = get_field('field_name', 123);
</code></pre>
<p>Escape the returned value according to its output context:</p>
<pre><code>echo esc_html(get_field('field_name', 123));
</code></pre>


FrontElf Fields Bridge for Contact Form 7

Add ACF and SCF field groups to the Contact Form 7 form editor.

izzy goldman

<p><strong>List Column Required for Gravity Forms</strong> lets you mark individual columns as <strong>required</strong> in multi-column List fields — something Gravity Forms doesn’t support out of the box.</p>
<p>By default, Gravity Forms only allows you to make the entire List field required (meaning at least one row must be filled). This plugin goes further: you can choose <strong>which columns</strong> within each row must be filled in before the form can be submitted.</p>
<h4>The Problem</h4>
<p>When using the Gravity Forms <strong>List</strong> field with “Enable multiple columns” turned on, there’s no way to require specific columns. You can only require the entire field, which passes as long as <em>any</em> cell has a value — even if critical columns like “Email” or “Name” are left blank.</p>
<h4>The Solution</h4>
<p>This plugin adds a small <strong>“Required”</strong> checkbox next to each column in the form editor. Check it, and that column becomes required — with server-side validation, front-end asterisk indicators, and accessible <code>aria-required</code> attributes.</p>
<h4>Key Features</h4>
<ul>
<li><strong>Per-Column Required</strong> — Mark individual columns as required independently</li>
<li><strong>Server-Side Validation</strong> — Required columns are enforced on form submission</li>
<li><strong>Front-End Indicators</strong> — Red asterisks on required column headers, matching GF native styling</li>
<li><strong>Accessibility</strong> — Adds <code>aria-required="true"</code> to required column inputs</li>
<li><strong>Auto-Require All</strong> — Toggling the field-level “Required” rule ON automatically marks all columns required</li>
<li><strong>Smart Row Handling</strong> — Blank extra rows are skipped; partially filled rows enforce required columns</li>
<li><strong>Zero Configuration</strong> — No settings pages; works at the field level out of the box</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>Edit any form with a multi-column List field</li>
<li>Check the “Required” checkbox next to individual columns in the form editor</li>
<li>Save the form — required columns are enforced on submission</li>
</ol>
<h4>Validation Logic</h4>
<ul>
<li><strong>Row with some data</strong> <span aria-hidden="true" class="wp-exclude-emoji">→</span> all required columns in that row must be filled</li>
<li><strong>All rows empty</strong> <span aria-hidden="true" class="wp-exclude-emoji">→</span> the first row’s required columns are enforced</li>
<li><strong>Extra blank rows</strong> <span aria-hidden="true" class="wp-exclude-emoji">→</span> skipped (user added a row but didn’t start filling it)</li>
<li><strong>Non-column List fields</strong> <span aria-hidden="true" class="wp-exclude-emoji">→</span> completely unaffected</li>
</ul>


List Column Required for Gravity Forms

Per-column required validation for Gravity Forms List fields — mark individual columns as required right in the form editor.

FrontElf Fields Bridge for Contact Form 7 vs List Column Required for Gravity Forms