| 开发者 | palpatel |
|---|---|
| 更新时间 | 2026年8月30日 13:51 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
?utm_source= query string or a browser cookie, not only from another fieldElementor Pro is required to use Elementor Forms. If you're on Elementor's free tier, install Hello Plus Form Lite to get Elementor-compatible forms.
Open the field in the Elementor editor, expand its Conditions tab, enable conditions, choose Show or Hide, and add a rule that references the controlling field's ID.
Yes. Enter url:param_name or cookie:cookie_name as the condition's Field ID instead of a form field ID.
Yes, using the Auto-Fill Value option on the Conditions tab. It's most often used to set a hidden field's value for lead routing or tagging.
They're automatically excluded from validation, so a hidden required field never blocks form submission.
Yes — hidden steps are automatically skipped, and the Next/Submit buttons adjust to match.
Equals, Not Equals, Greater Than, Less Than, Greater Than or Equal, Less Than or Equal, Contains, Does Not Contain, Starts With, Ends With, Empty, and Not Empty.
Yes, wherever Elementor Forms itself supports dynamic tags.
No. Scripts load only on pages that contain an Elementor form, and there's no measurable admin-side overhead.
Yes to both.
Confirm Conditional Logic is enabled under TNT Conditional Fields → Features, that Elementor Pro is up to date, and that the Field ID in your rule matches the controlling field exactly. Deactivating other plugins temporarily can help rule out a conflict.
Yes, with Pro's Form Field Groups. Instead of applying field-level conditional logic one field at a time, you bundle multiple fields into a group and control the whole group's visibility with a single condition — hide or show an entire section of the form at once, rather than bulk show/hide field-by-field. You can create unlimited field groups in one Elementor form, each with its own trigger condition.
Conditional Redirect after submission, Conditional Email routing, Conditional Submit Button visibility, and Advanced Form Field Groups for group-level (rather than field-level) conditional logic.
&, <, >, or a quote character could silently fail to match. Comparisons now use the correctly decoded value.register_setting() for the Features option now explicitly declares its data type.load_textdomain() on init hook for proper translation loading per WordPress i18n standards.rel="noopener noreferrer" to all external target="_blank" links for security best practice.CLFEF_VERSION constant across all enqueued files.rel="noopener noreferrer" per WordPress.org security guidelines.