Quick Answer
Check the capability a website needs against its actual Elementor plan and account. A form widget does not establish that submissions are stored, and dynamic WordPress content does not establish custom-field support. The 2023 Essential announcement is historical evidence, not a current feature matrix or proof of an existing subscription’s entitlement.
Keep the 2023 change in its original context
The WP Tavern report covered changes affecting new Essential customers. Elementor’s official announcement described a December 4, 2023 change and distinguished existing plans from new purchases.
Its historical table separated the Form Widget from Form Submissions and Form Integrations. It also distinguished native WordPress fields from custom-field integrations. Those distinctions explain the old news. They do not resolve a particular customer’s current plan, renewal or account history.
Translate the request into a specific capability
As reviewed on November 1, 2026, the current plan page lists Dynamic Content for Essential while excluding Custom Fields and Post Types. It lists Form Builder while excluding Form Submissions. Its present integration wording differs from the 2023 table, so the old exclusions should not be copied into a current recommendation.
Consider this hypothetical request for a small service website. It is an illustrative requirements record, not an account or installation we inspected:
- Request: show a contact form
- Identify the required fields and destination. The presence of a form-building widget answers only part of that request.
- Request: review entries inside WordPress
- Record saved submissions as a separate requirement. Check the actual plan and installed configuration rather than assuming the Form Builder label includes storage.
- Request: send a lead to another service
- Name the specific destination and supported integration. Verify its current requirements and the account’s entitlement separately from the form’s visual design.
- Request: display an approved custom field
- Record the field source and content type. Native WordPress dynamic content is not evidence that a particular custom-field workflow is included.
- Decision
- Leave each unresolved capability open with an owner. Compare plans only after the required behavior and account evidence are clear.
Confirm entitlement before changing the site
Have the authorized owner confirm the exact product, plan, purchase history and current account terms. Keep the public feature table and the account-specific evidence together. A similar plan name or an old screenshot is insufficient proof.
After an authorized implementation, verify the required behavior separately: whether the intended entry is stored, whether the approved destination receives it and whether the correct content field appears. This article records no purchase, installation or delivery test.
Our Divi field-validation guide concerns Divi and cannot establish Elementor capabilities. The WordPress block-conversion guide explains Classic-block conversion boundaries, while the Divi category-template guide covers archive queries rather than license entitlements.
Key Takeaways
- Read the Essential announcement as a dated 2023 change.
- Separate building a form, storing entries and integrating a destination.
- Distinguish native dynamic content from custom-field support.
- Resolve actual account entitlement before selecting or changing a plan.
Frequently Asked Questions
Does Form Builder mean submissions are saved in WordPress?
Check storage separately. The current Essential table distinguishes Form Builder from Form Submissions.
Can the 2023 table tell me what a new plan includes today?
No. Use the current official comparison and confirm the exact account and required capability.
Does the historical assurance prove my current renewal rights?
No. Ask the authorized account owner to establish the applicable purchase history and current terms.

