Elementor v3.0

v3.0: Planned Deprecations

Hey all! We are getting ready to release version 3.0.

Elementor 3.0 will introduce many changes to the way our users build websites with Elementor, and the way Elementor operates.

If you are a developer who extends Elementor please review the below changes to keep your plugin up and running.

Elementor 3.0 is a major release. We took the opportunity to introduce substantial changes and improvements to the infrastructure of Elementor.

Here are the planned deprecations:

PHP

Functions & Methods

Soft Deprecation

When a function/method is in the soft deprecation phase, it means that the function/method will still work while it’s in this phase, but a comment will be placed in the code mentioning the upcoming deprecation.

Function / Method NameChanges Made
Controls_Stack::_register_controls()

Core Plugin
Replaced by: Controls_Stack::register_controls()

Located in: includes/base/controls-stack.php

Hard deprecation Version: 3.4.0

Deletion version: 3.8.0
(more…) Read More »

DOM Improvements Ahead! HTML Wrappers Removal from v3.0

We are always looking for new ways to improve the speed and performance of Elementor websites.

This has been a long time coming. Lately, we have been receiving feedback from our users about the large number of wrapper elements we include in the HTML output of the website builder. The feedback stated that many of the wrappers are not necessary, and they increase the size of web pages and harm performance.

The presence of these wrappers is due to the diverse use of Elementor, the ability to use these selectors in various ways to customize your site, and the omni-purpose of Elementor as a solution for creating advanced websites visually.

Removing wrapper elements from the DOM contributes to more simplified code output, better readability and less complexity. A smaller DOM contributes to increases in speed and performance.

** Warning: Breaking Changes **

We have wanted to address this issue for a while now, and Elementor 3.0 provided us with the perfect opportunity to do so. Elementor 3.0 will bring many changes to the way our users build websites with Elementor, and some of these changes, including the removal of several HTML wrappers from our code, are potentially breaking. This means that when you update the Elementor version in your website from 2.x (or even 1.x, for some very out of date sites) to Elementor 3.x, your website’s appearance and/or functionality could break.

Interested in the changes coming down the road? Read more here

The Wrappers Being Removed

Without further ado, here are the classes of the wrappers being removed from Elementor in Elementor 3.0:

(more…) Read More »

v3.0 Updated Convention: Creating New Widgets (For Improved Performance)

As part of our effort to simplify and minimize the markup created by Elementor, we have decided to truncate the prefix we use for any Elementor CSS classes, from .elementor- to just .e-.

This move is joined by another important step in our journey of performance enhancement – reducing the number of wrapper HTML elements used by our widgets and by the system in general.

What does it actually mean?

In all of our new widgets, controls, and all-in-all system markup, we will be prefixing all of our classes with .e-.

We will NOT be changing pre-existing widgets, controls, or any other system elements, in order to allow for backwards compatibility and avoid causing serious problems in existing Elementor websites.

As opposed to the wrapper removal step, this is not a breaking change, so it’s not a big deal – if you see a change in our conventions, we just wanted you to let you know that it’s legit and share with you the reasoning behind it.

How does this affect me as an Elementor user or extension developer?

First of all, there is no need for you to make any changes to pre-existing widgets or system elements. If you are developing extensions that manipulate existing system elements, controls or widgets, and used the .elementor- prefix before – we recommend you to follow this guideline and start using .e- instead in your new developments.

Read More »

Elementor is Officially Dropping Support for Internet Explorer in v3.0

Elementor officially supported Internet Explorer 11 for front-end display (excluding the Editor) up until version 3.0. Starting from Elementor 3.0.0, it will no longer officially support IE 11 at all, not even for front-end display.

Why are we doing it?

Web standards and technology are constantly evolving, providing web developers with more features and better technology for creating websites and web applications. Modern Browsers like Google Chrome, Firefox, and even Edge (now Chromium-based), are constantly evolving with it, constantly being updated and improved upon. Do you know what’s not evolving, at all? Internet Explorer. Internet Explorer browser is old and outdated, and even Microsoft themselves say that using Internet Explorer is highly unrecommended. In addition, less than 3% of web traffic comes from IE browsers.

Why now?

Elementor has been already gradually introducing new widgets and features that utilize Modern web technologies and tools such as CSS Grid and CSS variables. In order to provide our users with a better experience using Elementor, as well as the ability to build faster, better-performing websites with more advanced features, it was inevitable that we would have to drop IE support completely, in order to proceed in the right direction.

How does this affect me?

If you or your target audience don’t really use Internet Explorer, this should not affect you at all.

However, If your target audience includes a large portion of Internet Explorer users, it might be a good idea to consider holding off on upgrading Elementor and Elementor Pro to v3.0.0 until you’ve made sure you have solutions that enable your site visitors to use your website conveniently.

Users who already upgraded don’t need to worry, simply use Version Control tool to downgrade back to an earlier version and everything should work as it used to.

Read More »

Never miss an update
Subscribe to our developer’s newsletter for every latest update