✅ 🔥 Elementor Editor v4.1 Beta Release 🔥

[avivu]

===========

Beta Version Updates - Please Read Below!

===========

 

Hey Beta Testers, 👋

We’re excited to announce that Elementor 4.1 Beta is now live.

Following the public introduction of the Atomic Editor in version 4.0, this release focuses on improving and expanding the workflows that power scalable web creation inside the new architecture.

Version 4.1 introduces the first Angie capabilities designed specifically for Atomic Editor workflows, expands Atomic Forms with more advanced capabilities, and improves how creators manage reusable design systems at scale.

Make an impact by testing Elementor 4.1 Beta and sharing your feedback on the latest additions, including:

• Angie AI workflows for the Atomic Editor
• Unified Variables and Classes management
• New Atomic Form elements and workflow capabilities
• Class limit increased to 1k
• & more!

Looking forward to hearing your thoughts and feedback on this update!

 

Angie enters the Atomic workflow

Angie empowers web creators to build production-ready assets for WordPress with Agentic AI, designed to help creators achieve advanced website experiences and functionality that would previously require custom development, multiple plugins, or significant workflow compromises inside WordPress.

Because Angie is built specifically for Elementor and WordPress workflows, generated outputs remain connected to your existing editing environment and reusable site structure, so you remain in full control of structure, styling, and governance.

With version 4.1, Angie begins integrating into the Atomic architecture as well, helping creators accelerate the setup of reusable design systems, Components, and atomic layouts while staying aligned with the new atomic foundation.

Getting the best results with Angie

Like all AI tools, Angie works best when provided with clear and powerful direction, references, and context. The more specific and powerful your prompts, references, screenshots, and URLs are, the better and more reusable the results become.

You can add AI context by clicking the 3 lines on the top right of the Angie panel, then go to AI context. From there you can add info about your business/website, your voice and tone, and pick relevant keywords.

 

Generate reusable structures with Angie

You can now use Angie to generate structured compositions and reusable Components with exposed properties, helping accelerate scalable workflows while maintaining full control over structure and styling.

For example, while building a website for a wellness retreat, like in the images above, you may want to create reusable retreat cards, pricing cards, feature grids, or promotional banners that can be reused across multiple pages while still allowing controlled content editing.

 

  “Create a retreat card component. Include image on the top, title, description and book now CTA.”

  “Create a full-width Featured Retreat section with one retreat image, title, short description,

  and a ‘View Retreat’ button. Keep it calm, clean, and concise.”

 

Because these outputs are generated directly within the Atomic architecture, they continue following the same reusable workflows introduced in version 4, including Variables, Classes, Components, and reusable styling logic.

This allows you to move faster without sacrificing maintainability, consistency, or governance as projects grow in complexity.

Reusable Components are an Elementor Pro feature and therefore Angie will only be able to generate Components if you have an active Elementor Pro subscription.

 

Speed up Form and Tab creation with Angie

Angie can now help generate Forms and Tabs directly from prompts, creating structured starting points that remain fully editable inside the Editor.

For example, while building, you may need onboarding forms, pricing comparison tabs, or lead-capture flows.

 

  “Create a booking form for a retreat program with Name, Last Name, Email,

  a retreat dropdown, file upload, and Notes fields.”

 

These capabilities help creators move from setup to refinement faster while still preserving the flexibility and control of the Atomic Editor.

Forms are an Elementor Pro feature and therefore Angie will only be able to generate Forms if you have an active Elementor Pro subscription.

 

Create Classes and Variables faster with Angie

One of the biggest shifts introduced in version 4 is the move from page-level styling toward reusable design systems powered by Variables and Classes. Instead of styling every element individually, creators define reusable styling logic once and apply it consistently across the site.

Rather than manually creating every Variable and Class one by one, you can now use Angie to help implement reusable styling systems faster using prompts, references, screenshots, or existing design directions.

For example, when working on the retreat website, you may want to establish typography scales, spacing systems, color tokens, and reusable button styles before building layouts.

 

  “Create a new font variable for Roobert sans and apply it to all card headers.”

  “Create reusable Classes and Variables based on the image attached.”

  “Create this Class:”

.card-product {
  background: #ffffff;
  border: 1px solid #e5e7eb;
  border-radius: 12px;
  outline: 1px solid rgba(255, 255, 255, 0.6);
  padding: 24px;
}

Because the generated Variables and Classes become native parts of the Atomic system, they remain fully editable, reusable, and maintainable throughout the project lifecycle.

 

Angie becomes part of the Editor workflow

To support these new workflows, version 4.1 introduces the Angie entry point in the Editor Top Bar for all users, and those who have not yet installed Angie can now do so directly from this location.

To install Angie, simply click on the Angie icon on the left side of the Top Bar and follow the instructions.

This release is just the beginning of Angie’s integration into the Atomic Editor, with additional atomic AI capabilities planned for the next releases.

 

Manage scalable design systems more efficiently

As websites grow in complexity, managing reusable styling systems efficiently becomes increasingly important. Version 4.1 introduces several improvements that simplify how Variables and Classes are organized, reused, and maintained inside the Atomic Editor.

The unified Classes and Variables Manager

Version 4.1 introduces a unified management panel for Classes and Variables, consolidating reusable styling workflows into a single centralized interface accessible directly from a new icon in the Top Bar.

Until now, Variables and Classes were managed separately, creating additional context switching when building and maintaining larger systems. The new unified manager simplifies this workflow by bringing design tokens and reusable styling logic together into a more cohesive workspace.

On many of your projects, you may be managing typography Variables, spacing scales, color tokens, reusable button Classes, and section Classes across multiple pages and sections. The unified manager makes it easier to review, organize, and maintain these systems as the project grows.

This also creates a more natural workflow alongside Angie-powered system generation. After using Angie to help accelerate the setup of Variables or Classes, creators can immediately continue refining and organizing those systems from the same centralized workspace.

How to test it

1. Open the Editor and click the new Design System icon in the Top Bar.
2. Confirm that Variables and Classes are now available in the same panel.
3. Open the Variables tab and create a new Variable.
4. Open the Classes tab and create a new Class.
5. Click Save and confirm the changes are saved successfully.
6. Switch between the Variables and Classes tabs and confirm you can manage both from the same panel.
7. Edit an existing Variable and an existing Class.
8. Click Save and confirm the updated values are applied correctly where they are used.
9. Verify that existing Variables and Classes from the site appear correctly in the new unified panel.
10. Refresh the Editor and confirm the saved Variables and Classes remain available.
11. Validate the behavior in the editor canvas, preview mode, and on the frontend.

 

Share Variables and Classes across projects

Version 4.1 also introduces the ability to export and import entire Variables and Classes collections directly from the new Design System panel.

This allows creators to move reusable styling systems across websites more efficiently, helping agencies and professional creators standardize design systems across multiple projects.

For example, teams can now create a complete reusable styling foundation once, including typography Variables, color tokens, spacing systems, and reusable Classes - and reuse the same collection across multiple websites without rebuilding the system manually each time.

How to test it

1. Open the Editor and click the Design System icon in the Top Bar.
2. Create several Variables and Classes, then click Save.
3. Open the three dots menu in the Design System panel and select Export.
4. Confirm that a ZIP file containing the Variables and Classes is downloaded.
5. Open another website with Atomic Editor active.
6. Open the Design System panel and select Import.
7. Upload the exported ZIP file.
8. Confirm that the imported Variables and Classes appear in the Design System panel.
9. Apply an imported Variable and an imported Class to Atomic elements and confirm they work correctly.
10. Click Save, refresh the Editor, and confirm the imported Variables and Classes remain available.
11. Validate the behavior in the editor canvas, preview mode, and on the frontend.

 

Create up to 1k Classes

If you've been building large-scale design systems, you may have run up against the previous Class limit. Version 4.1 removes that ceiling, now supporting up to 1,000 Classes.

As projects grow in complexity and reuse increases across pages and Components, larger systems naturally require significantly more reusable styling structures. Increasing the Class limit removes existing scalability constraints and supports more advanced design-system workflows.

 

Duplicate Classes and Variables faster

To improve iteration speed while building reusable systems, version 4.1 also introduces the ability to duplicate both Classes and Variables directly inside the Atomic workflow.

Instead of manually recreating similar styling structures from scratch, creators can now duplicate existing Variables or Classes and quickly create variations while preserving consistency across the system.

For example:

• Duplicate an existing button Class to create a secondary button variation
• Reuse spacing Variables while adjusting values for different layout densities
• Create alternate typography scales while maintaining consistent naming structures

These improvements help reduce repetitive setup work while making large-scale system management more efficient and predictable.

How to test it

Duplicate Variables

1. Open the Editor and click the Design System icon in the Top Bar.
2. Open the Variables tab and create a new Variable.
3. Click the three dots next to the Variable and select Duplicate.
4. Confirm that a duplicated Variable is created with the same value as the original.
5. Update the duplicated Variable and confirm the original Variable is not affected.
6. Click Save and confirm the duplicated Variable is saved successfully.
7. Apply the duplicated Variable to an Atomic element and confirm it works correctly.
8. Refresh the Editor and confirm the duplicated Variable remains available.

Duplicate Classes

1. Add an Atomic element to the canvas and apply a Class to it.
2. Open the Class control and select the option to duplicate the Class.
3. Confirm that a duplicated Class is created with the same properties as the original.
4. Update the duplicated Class and confirm the original Class is not affected.
5. Apply the duplicated Class to an element and confirm the styles are applied correctly.
6. Click Save and confirm that the duplicated Class is saved successfully.
7. Refresh the Editor and confirm the duplicated Class remains available.

 

Build more advanced layouts with Atomic Forms [Pro]

Introduced in version 4.0, Atomic Forms represent a shift away from monolithic form widgets toward composable form architecture built on Atomic principles. Each field acts as an independent element that participates in the broader design system through Variables, Classes, Components, and unified styling workflows.

Version 4.1 continues expanding Atomic Forms with new form elements and workflow capabilities that support more advanced business experiences:

• Select (dropdown) element - Enables dropdown-based selection experiences, helping create cleaner interfaces while improving handling of predefined options. Common scenarios include plan selection, department selection, location pickers, category filtering, and team routing flows.
• Radio Button element - Adds structured single-choice selection directly inside Atomic Forms. This improves clarity for guided experiences while ensuring cleaner and more consistent submission data. Useful for subscription preferences, service selection, qualification flows, delivery methods, and support request categorization.
• Date Picker and Time Picker elements - Introduce structured scheduling inputs for booking, reservation, and time-sensitive submission flows. Typical use cases include appointment booking, consultation scheduling, event registration, demo requests, and reservation systems.
• File Upload element - Allows visitors to upload files directly through Atomic Forms, expanding support for applications, onboarding flows, support requests, and document collection. This is especially useful for job applications, creative submissions, support attachments, client onboarding documents, and project request forms.
• Webhook URL control - Allows form submissions to trigger webhook-based workflows directly from Atomic Forms. Once Webhook is selected inside Actions After Submit, creators can define an external webhook endpoint for handling submission data.

How to test it

1. Add the Atomic Form element to the canvas.
2. Inside the Form Wrapper, add the new form elements: Select, Radio Button, Date Picker, Time Picker, and File Upload.
3. Configure the options for the Select and Radio Button elements and confirm they appear correctly in the form.
4. Preview the page and confirm the Date Picker and Time Picker allow visitors to select a date and time.
5. Configure the File Upload element and confirm a file can be uploaded successfully through the form.
6. In the Form Wrapper, open Actions After Submit and add Webhook.
7. Add a Webhook URL and submit the form.
8. Confirm that the submission is sent to the configured webhook endpoint.
9. Submit the form from the frontend and confirm all new field values are captured correctly in the submission.
10. Open the Submissions area in the WordPress Admin and confirm the submitted entries appear correctly.
11. Validate the form behavior in the editor canvas, preview mode, and on the frontend.

 

Additional updates

Interactions improvements

• Scroll start and end grid lines - While Scrolling effects now display Start and End grid lines on the canvas, making it easier to visualize trigger points and fine-tune scroll-based interactions.

Component workflow improvements

• Reorder exposed Component properties - Exposed Component content properties can now be reordered with drag-and-drop across groups, improving organization and flexibility when managing more complex reusable Components.

Atomic Form workflow improvements

• Connected Input ID as a Select control - Connected Input ID now uses a Select control that automatically surfaces available form fields from the current form structure, reducing manual setup work and configuration mistakes.

• Dynamic field mentions in email content - Email message workflows now support dynamic field mentions using @ mentions, making it easier to insert specific form values directly into email content.

• Reply-To improvements - Reply-To configuration now includes smarter field suggestions and improved handling for email-based form inputs.

• Improved email defaults - Email settings now provide improved defaults for To and From fields, simplifying setup while helping reduce configuration issues.

New Alpha experiment

• Generate website markdown - A new Alpha experiment that improves how Elementor content is structured and exposed, making it easier for AI systems to read, understand, and interact with it over time. This experiment is inactive by default for all users.

 

More Improvements

Free version

• New: Introducing the Design System panel for managing Variables and Classes in one place - Atomic Editor
• New: Introduced Angie in the Editor to help generate and modify Atomic layouts, Components, Forms, Classes, and Variables - Atomic Editor
• New: Added Markdown rendering as an Alpha experiment to improve how content is structured for AI systems
• Tweak: Added the ability to import and export Variables and Classes from the Design System panel - Atomic Editor
• Tweak: Increased the Class limit to 1000 - Atomic Editor
• Tweak: Added the ability to duplicate Variables in the Variables Manager - Atomic Editor
• Tweak: Added the ability to duplicate Classes in the Class field - Atomic Editor
• Tweak: Added support for Variables in additional style controls, including Effects, Filters, and Box Shadow - Atomic Editor
• Tweak: Added multi-select support to Direction control in Interactions - Atomic Editor
• Tweak: Added Interaction actions to the History panel - Atomic Editor
• Tweak: Added support for negative Box Shadow values - Atomic Editor
• Tweak: Improved reordering of Component properties with full drag-and-drop support - Atomic Editor
• Tweak: Updated Position and Z-Index control visibility and behavior - Atomic Editor
• Tweak: Updated the minimum required WordPress version to 6.8
• Tweak: Added the External URL option to Image - Atomic Editor
• Fix: Slide Interactions can be applied without selecting a direction - Atomic Editor
• Fix: Undo does not work as expected for individual Class properties - Atomic Editor
• Fix: Font family values persist on Global Classes after deletion - Atomic Editor

Pro version

• Tweak: Added Radio Button element to Atomic Form - Atomic Editor
• Tweak: Added Select element to Atomic Form - Atomic Editor
• Tweak: Added Date Picker element to Atomic Form - Atomic Editor
• Tweak: Added Time Picker element to Atomic Form - Atomic Editor
• Tweak: Added File Upload element to Atomic Form - Atomic Editor
• Tweak: Added a Webhook URL support to Atomic Form - Atomic Editor
• Tweak: Improved the default To and From field settings in Atomic Form - Atomic Editor
• Tweak: Updated the Connected Input ID control to a Select control in Atomic Form - Atomic Editor
• Tweak: Added the Atomic Elements section when editing Loop Grid templates - Atomic Editor
• Tweak: Added support for dynamic field mentions in email content in Atomic Form - Atomic Editor
• Tweak: Added Start and End grid lines for the While Scrolling effect in Interactions - Atomic Editor
• Tweak: Updated the minimum required WordPress version to 6.8
• Fix: Custom styles are lost for Atomic elements used in loops - Atomic Editor
• Fix: Action Log and Page Title are not recorded in Atomic Form submissions - Atomic Editor
• Fix: Inline editing does not work for Buttons inside Atomic Form - Atomic Editor
• Fix: Atomic Form cannot be dragged into containers or child containers - Atomic Editor

---

 

How to install the Beta version and activate atomic features

If you still haven't enabled beta testing in Elementor and activated atomic features, please follow these steps:

1. Go to Elementor > Editor > Tools > Version Control
2. Enable the beta tester feature
3. Go to Dashboard > Updates, and update to the latest beta version
4. Go to Elementor > Editor > Settings > Atomic Editor
5. Activate

 

Notes

As we make changes to our GitHub in an effort to keep it organized, improve the way we deliver information to you, and our ability to review your feedback, please follow the instructions below when reporting bugs, or making feature requests:

• To report a bug related to atomic (version 4) features: open a new 🐛 Editor V4 Bug Report
• To report a bug related to version 3 features: open a new 🐞 Bug Report
• For feature requests: open a new 🚀 Feature Request
• For other comments specifically about this beta version: Comment here

Designated time for release: May 26th, 2026 (estimated).

Many thanks for your support and help!

Cheers,
The Elementor Team

[m1ga]

Two things:

"Custom Widget" area looks broken and since I have disabled "AI functionality" in my user settings, I shouldn't see the Angie button in the top-bar in my opinion.

And please don't push a dev1 version as a public version next time 😉 Have three client sites that made the update and I don't think I can send you a bill to go in by hand and downgrade it again :-)

[doronwolf]

hi @m1ga, thank you for surfacing this custom widget bug - we are checking it
Also, we are, obviously, looking into the beta incident; it wasn't supposed to be exposed for non-beta subscribers - this is super serious. We are searching to understand how and why it happened, so it will never happen again, and we are not taking it lightly 🙏

[aksellno]

Also mentioned the Angie functionality in https://github.com/orgs/elementor/discussions/35856

[Flickimp]

Two things I've noticed about the radio button;

1. There is no style option for the radio selected colour (even when I changed the state and messed around with typography colours).
   I used this inside Custom CSS to apply a colour when the radio is selected:
   &::before {
   background-color: #0000FF;}

2. When a radio is selected, we can't unselect it.

If I've made a mistake or overlooked anything, please do let me know.

[nicholaszein]

Hi @Flickimp! 🙂

There is no style option for the radio selected colour (even when I changed the state and messed around with typography colours).
I used this inside Custom CSS to apply a colour when the radio is selected:
&::before {
background-color: #0000FF;}

Indeed we need to verify this. Thank you for raising this!

When a radio is selected, we can't unselect it.

That's the intended/expected native browser behavior. There is no native "toggle off" for radio inputs.

Native HTML radio inputs cannot be unselected by clicking them again once one option in the group is selected. Differently from checkboxes, only one option in a radio group can be selected at a time. Clicking another radio in the same group switches the selection. Clicking the already selected radio does nothing.

In this case, we recommend using the checkbox input field.

[Flickimp]

Spot on, you were right about having another radio in the same group to allow you to switch selection. Crisis avoided!

[nicholaszein]

Hi @Flickimp,

we're working on fixing the background issue. We might make some changes to the whole display of the radio button.

Thank you for sharing your feedback! 🙏

[alexanderpankart]

Feedback on Webhooks & Form Functionality

It’s great to see that webhooks are now available! It makes starting automated flows after a lead form submission much more convenient.

I’ve been testing the feature, but I noticed that the form only sends successfully when it is placed outside of a component:

• Form A as a component: Error, does not send.
• Form A directly in a container: Success, sends as expected.

I also have a few "Quality of Life" questions:

Label IDs: Is it possible to include the ID of the label sent via the webhook in the payload?

Dynamic Subjects: Can the email subject line be made dynamic using the newly introduced "@" linking (similar to how it works in the message field)?

Redirects: Are redirects after a successful form submission planned? If not, is there a workaround? I would like to track thank-you pages in my analytics tools and provide users with further information on the next steps after their submission.

[nicholaszein]

Hey @alexanderpankart! Welcome back! 🙌

I’ve been testing the feature, but I noticed that the form only sends successfully when it is placed outside of a component

Yes, we are aware of this, and we are working on a solution. 😉

Is it possible to include the ID of the label sent via the webhook in the payload?

Not at the moment, but we will consider it for a future release.

Can the email subject line be made dynamic using the newly introduced "@" linking (similar to how it works in the message field)?

That's an interesting idea. We'll add to our nice-to-have list! Thanks for the suggestion! 🙂

Are redirects after a successful form submission planned?

We have the "Redirect After Submit" action in V3 Forms, so yes, this is planned! 😉

Thank you for sharing your feedback! 🙏 😊

[nicholaszein]

Hi. Elementor has its own MCP server used by Angie.

[rahulv3a]

Hi @nicholaszein, is this MCP server built specifically for Angie? Curious why you didn't go with the WordPress standard instead.

[nicholaszein]

Hi @rahulv3a

Angie comes pre-installed with its own bespoke MCP servers and Workflows (and soon Agents too), and it uses several LLMs to execute different tasks (whichever is more appropriate), all completely integrated without requiring any setup, API connection, or complex installation, but most importantly without needing to leave WordPress to work on another app. It's completely seamless.

We also just released a Cloud Library functionality, so you can save your code snippets and reuse them, not to mention the possibility to restore revisions. It's not just content and site management, but a whole suite of capabilities, including extending and managing both WordPress, Elementor, and several other plugins, generating images, and building content, and much more to come.

Angie is also older than the newly released WordPress MCP and Abilities API. We are following WordPress development closely, but for the time being we have no plans to integrate with the Core implementation. Let's give it some time to mature.

We will revisit this decision in the future.

[Flickimp]

If the Date Picker could have a setting to prevent dates in the past that would be great, so it should always be >= today().

[nicholaszein]

Thanks for the suggestion @Flickimp.

Well add it to our list! 🙏

[pumadog]

For the form? What if it's used for birth dates and such?

[welmartins]

Thanks for the updates, they’re amazing! 🔥

The increase to 1,000 variables is a huge improvement and will help a lot.

That said, I’d like to suggest a few improvements:

Variable Management

With up to 1,000 variables, it may become difficult to manage everything by just scrolling through the list.

It would be great to have a way to group variables into virtual folders, even if they’re only visual. This could also optionally affect the variable naming.

For example:

Font
├─ sans
├─ mono
└─ serif

Which could generate variables like:

"--font-sans"
"--font-mono"
"--font-serif"

Another helpful improvement would be an icon or visual indicator showing which color variables are synced with Global Styles, without having to open the options menu for each one.

Batch actions for variables would also be really useful, such as:

• Delete
• Duplicate
• Sync with Global Styles

Variable batch Edit mode

Another important improvement for variable management would be an Edit Mode.

A mode where multiple variables can be edited at once, instead of needing several clicks just to edit a single value. Simply turning all fields into editable inputs would already speed up the workflow a lot.

Another interesting approach could be a list-based editor with one variable per line, something like:

"font;custom-name;Inter;"
"color;my-color;#ffffff;"

Select Input

Are there plans to allow select options to be populated dynamically?

For example, using a query from:

• Posts
• Custom post types
• Taxonomies
• Custom taxonomies

Will there be a hook to populate options dynamically from the backend?

Forms

Will there be support for conditional logic, such as showing or hiding fields based on previous field answers?

Allowing Certain HTML Tags

For elements filled dynamically through queries, shortcodes, and similar sources, are you planning to allow HTML tags again in the Before, After, and Fallback fields?

A small safe list of tags would already help a lot, such as:

"span", "strong", "small", "big", "br"

[nicholaszein]

Hi @welmartins, welcome to the discussion!

Thanks fro the detailed feedback! 🙏

Variables management suggestions

Variables management with more functionality is something we are planning to do. It may not be at the same level as you are suggesting, but things like groups, and bulk actions (duplicate, delete, move) are concepts we've been researching.

Dynamic Content for Forms

In general, if there is a feature in V3 Forms, we will apply something similar to Atomic Forms. Things like setting a Dynamic Sylubject like requested in other comments, or allowing to select dynamic data for other fields. However, when it comes to arrays (multiple values, like in the Select field), things are a little more complicated, and require really intricate and "prone-to-error" logic that are not the goal right now. We have no plans to include such complex implementation for the time being. Maybe in a future release. The goal is to deliver a complete form with functionality comparable with V3 Forms.

That being said, there will be hooks you can use for customization.

Sanitization and whitelisting HTML tags

We learned a lot with previous versions regarding security, and if you look around you'll see a boom in security exploits across the industry. With the Atomic Editor we had the chance to build a more robust system from the ground up to ensure security remains preserved from the get go. This means, unfortunately for some edge cases, not being able to use most html tags on places that you were used to use. It's too much of a risk we are not comfortable with. Sure, we allow a more flexible usage on V3 widgets, however, we only do it to ensure backward compatibility.

So it's unlikely we will allow the use of Shortcodes or html tags in special places such as some dynamic tags with before and after fields. We understand this is not optimal. It's a hard decision to make.

But we will take note and reconsider it if there is enough demand for it.

Thank you again for joining the discussion, and sharing your feedback! 🙏

[alexanderpankart]

[nicholaszein]

Would you be so kind to share a screen recording of the problem @alexanderpankart?

There is some logic going on with Atomic Forms, and it's likely a problem in that logic, but I've got to be honest with you, I'm not sure if I understood this specific case.

[alexanderpankart]

I think it's solved. Can't replicate it today. Maybe server caching.

[jlemonz]

I still think the new system is just way too complicated for regular use of building a website. This system is really made for big design companies. There is a lot of feedback/criticism. But zero response from elementor. Like what is your stand of v3 elements? Is this going to fased out? If yes i really am going to look for another builder. Just making a simple website takes 10 times longer with the new system. Just try making a nice tab layout and design the buttons etc. I is just not doable and lots of frustrations. I think the new ai is just a way to try to fix the new system because its so much more work to build something. https://github.com/orgs/elementor/discussions/35109 https://github.com/orgs/elementor/discussions/35759 The best example is building a button with an icon. In the past 10second work. Not i have to create divs style etc takes minutes work. And elementor doesnt provide any premade stuff. THis just defeats the entire purpose of elementor and easy building. Same for sticky header yes add javascript again this defeats the idea of elementor. Elementor should have this build in. Now months of nothing and v4.1 and what happened? Another AI that probably will be payware later.

edit: i jsut tried the new ai. and ask an button with icon using atomic. It just creates an button with new icon next to it. So completely useless.

[doronwolf]

Hi @jlemonz, V3 is not going away, and we are not forcing users to move to v4. Users can choose to keep building with v3 or both v3 and V4 together. I do agree that V4 is more scalable and therefore more complicated. I also must agree we should have (and it is in our to-do list to create and supply for our users) ready-made components and presets (such as a simple icon with icon and later on more complicated stuff like v4 look grid cards, etc.) but those things take time and this is again, why v4 is supplementary to v3 and they can live together in the same page and no one is forced to use just one of them, we are aware of those thigns you pointed out and trying our best to close the gap 🙏

[m1ga]

and we are not forcing users to move to v4

kind of. You make it enabled by default for new pages and you have to opt-out if you want to not see v4 stuff. The other way round would solve so many issues people have: thinking it is complete and ready to use. But as you say "but those things take time" so it should still live under "opt-in if you know what you are doing".

[doronwolf]

It's hard to please everybody at the same time, while some would rather v4 to be opt-in, others think it's been that way for quite a long time and love the freedom to explore it already, especially on new sites.
And again, the fact that it's on only adds widgets and capabilities; it doesn't take down anything from v3, it doesn't hold you back from keeping using v3, also, we are getting more valuable feedback we wouldn't get without it
we can't make everybody happy at the same time so we have to choose :)

[m1ga]

others think it's been that way for quite a long time and love the freedom to explore it already

The big Elementor/WP Youtubers, reddit and most of the people in the discussion here don't think that 😉 I know I can use v3 but I don't want my clients to start using v4 elements at the moment so opt-out is the way to go for every new setup until it's a bit mature. The people that want to use it are the pro users, they are able to opt-in and then understand it's still in progress and you wouldn't get that much hate for v4 because you wouldn't market it as "production ready" that way. But enough off-topic now, sorry for using this post but the "we are not forcing users to move to v4" just sounded not correct.

[nicholaszein]

@m1ga,

We understand not everyone is comfortable with having the Atomic Editor active at the moment, that's why we planned to make it seamless and optional exactly to give people the flexibility to choose their own path. At this point in time we think activating the Atomic Editor on new sites is important to give people time to adjust to the new workflow. We don't mind negative feedback, we welcome it, because now (and as it has been since we started working on V4) is still the best time to adapt and make corrections.

We haven't used the term "production ready" for quite some time now. We received the feedback, and changed our communication to reflect it.

Don't worry about being off-topic (you aren't, really). You are always welcome to share your feedback with us, we appreciate your contributions very much, and we like to hear your opinion.

[avivu]

Hi all,

We just released Elementor Editor v4.0 Beta 2.

The versions include the following:

Free version

• Fix: Improved Angie integration with Atomic Editor
• Fix: Arrow navigation doesn’t work in Carousel widgets when device Reduced Motion is enabled
• Fix: Atomic Forms don’t work inside Components - Atomic Editor
• Fix: Global Classes search returns incomplete or inaccurate results - Atomic Editor
• Fix: Design system import may not apply or preserve Global Classes as expected - Atomic Editor

Pro version

• Fix: Pasting content from another site may cause a fatal error with Loop Item Templates

---

Thank you!

[yehiel-nachmani]

One more piece of feedback on Components: not all properties can currently be exposed as per-instance customizable. It would be very valuable to also allow data attributes to be set as overridable per instance — not just text and media. On dynamic CPT-driven templates this would make Components far more powerful, since per-instance data attributes are often needed to wire each record to dynamic logic. Would love to see the customizable-property scope expanded. Thanks!

[nicholaszein]

Hi @yehiel-nachmani! Welcome to the discussion! 😊

Sorry about the delay in answering you. I remember seeing two comments, did you remove the other one or am I just tripping? 😅

Regarding Component properties, we have plans to add more functionality to them, including expanding the customizable property scope. 😉

thank you for sharing your feedback!

[kimspillnerwebdesign]

Importing variables and classes is only working half way. The variables are imported correctly but the classes don't appear after importing.

[nicholaszein]

Hi @kimspillnerwebdesign, welcome to the discussion! 🙌

Thanks for sharing this, we're investigating! 🙏 🧐

[nicholaszein]

Hi @kimspillnerwebdesign,

can you share the exported file with us?

[kimspillnerwebdesign]

Hi, yes – this is the file
Ziencz-IT-Systeme-elementor-export.zip

[nicholaszein]

Thank you for sharing the file @kimspillnerwebdesign! 🙏

We identified the problem and already patched it, to be fixed in the final release! 🙌

[kimspillnerwebdesign]

Thanks so much!

[avivu]

Hi all,

We just released new Beta versions.

The versions include the following:

Free version - V4.1 Beta 3

• Fix: Improved Angie integration with Atomic Editor

–

Thank you!

[EldritchAdam]

is there any forthcoming support for lists within the Atomic Paragraph Element? The first use case I have for creating a component gets dashed by this omission - I cannot hand off to my client a component built around a text editor that can't handle simple list items.

[nicholaszein]

Hi @EldritchAdam,

There will be support for lists, but not inside the Paragraph. The Paragraph element is not a text block. It's a literal Paragraph (<p> tag). Lists are not supposed to be inside paragraphs.

[welmartins]

Hey @nicholaszein , Another problem I encountered is that when you delete some variables, they are still added to the CSS, but they lose their name and become something default to Elementor.

[nicholaszein]

Hi @welmartins, thank you for raising this issue! 🙏

We are aware that deleted variables remain saved in the Default Kit stylesheet. This is something we will be addressing in a future release.

[kimspillnerwebdesign]

One other problem (even with the final 4.1 release) is that class overrides are not correctly reflected in the frontend.

This is the screenshot from the elementor editor. But the frontend renders the .btn-primary as the dominating background color. This is not only for background colors ... but everything with multiple classes now doesn't respect the expected class hirarchy.

[Tygovanommen]

The markdown article does not exist yet, so it is difficult to figure out what exactly it does:
'%1$s <a href="https://go.elementor.com/wp-dash-generate-website-markdown-article/" target="_blank">%2$s</a>',

I think it is supposed to be this article:
https://elementor.com/help/how-do-i-make-my-site-more-accessible-to-ai-agents/

[doronwolf]

Fixed - thanks for letting us know 🙏

[nicholaszein]

Alright folks,

Thank you all for sharing your feedback and participating on this beta! 🙏

Your contribution helps shape the future of 21M+ websites built with Elementor! You guys rock! 💪

Special thanks to:

• @m1ga
• @Flickimp
• @alexanderpankart
• @rahulv3a (we are working on something you'll probably like! 😉)
• @pumadog
• @welmartins
• @jlemonz
• @yehiel-nachmani
• @kimspillnerwebdesign (we're investigating your last report)
• @EldritchAdam
• @Tygovanommen

See you in the next one! 🤝

Take care