✅ 🔥 Elementor v3.16 Beta Release 🔥

[avivu]

===========

Beta 4 UPDATED - PLEASE READ BELOW!

===========

 

Hey Beta testers, 👋

The beta version of Elementor 3.16 is now available and we're excited to hear your feedback on the new features. From this version onwards, containers will be activated by default on all new websites. In addition, there are various UX/UI improvements, performance and accessibility enhancements, and more.

Try out this beta version and let us know what you think about our newest additions, which include:

• Containers Activated on New Websites
• Performance Improvements
• Menu & Tab Widgets Update
• Accessibility Enhancements
• And more…

   

Containers Activated on New Websites For Maximum Design Flexibility

 

Containers are a powerful tool for building pixel-perfect, high-performing, and responsive websites. With more accurate positioning settings, you can efficiently align and distribute items in a container for more flexible layouts. Containers also give you nested capabilities, which mean you can place widgets inside the content area of widgets like the Carousel, Menu, Tabs, and Accordion Widgets for unlimited design possibilities. Starting from this version onwards, they will be activated by default on all new sites.

This update will not affect sites built with sections and columns, and you will be able to continue using them, but we recommend enabling Containers to enjoy new design capabilities. If you’re creating a new website and want to build with sections and columns, you can deactivate the Flexbox Container feature, though you won’t have access to features and widgets with nested capabilities.

Activating Flexbox Containers will also give you access to Container-based Kits and templates that include the most popular section-based Kits converted to Containers, alongside new designs. Disable the Flexbox Container feature to use section-based Kits and templates.

Updated Gap Control Between Elements

The "Gap between elements" control has been renamed to "Gap". Instead of a single range control for setting the gap between elements inside Containers, you can now control the horizontal and vertical gaps separately with a number input for each. This allows you to more accurately control the layout of a container.

Grid Container Widget

Grid containers and Flexbox containers now have their own widgets in the Widget Panel, allowing you to directly access the Grid Container without having to drag the Flexbox Container and change its type. If you drag a Flexbox Container into the editor, it will automatically create a Flexbox Container, and if you drag a Grid Container into the editor, it will start as a Grid Container. You can still change each container to the other type from the Container Layout dropdown menu in the Layout section.

To use Flexbox and Grid Containers, activate the Flexbox Container and Grid Container features by going to WordPress Dashboard → Elementor → Features.

 

Performance Improvements - Faster TTFB

 

Version 3.16 includes updates to Elementor's infrastructure, which further accelerate the loading speed of your site's frontend. These updates improve the TTFB (Time to First Byte), a key metric for measuring connection setup time and web server responsiveness.

By modifying the functions responsible for display conditions within the Editor, we were able to reduce loading time on your site's frontend by 5% to 20%, depending on the complexity of the page. Consequently, these improvements have a positive impact on front-end performance.

 

Menu & Tabs Widgets Update

 

These widgets have an upgraded infrastructure that produces a unified DOM output for the titles of Menus and Tabs in responsive settings. This removes duplication of code and streamlines the HTML structure allowing the implementation of advanced features in both widgets. For example, this version makes the Menu and Tabs Widgets fully accessible.

Note: This update will also apply to existing Menu and Tabs widgets, and may break designs of titles in this widget if custom CSS has been applied to them.

To use the Menu and Tabs widgets, activate the Flexbox Container, Menu, and Nested Elements feature by going to WordPress Dashboard → Elementor → Features.

 

Accessibility Enhancements

 

Elementor continues to empower you to create more accessible websites. This version includes important accessibility improvements to several widgets that will make it easier for visitors who rely on screen readers and other assistive technologies to enjoy your content.

For example, improvements have been made to widgets with multiple elements and links, such as the Icon Box or Image Box. Screen readers scanning these widgets will read the link assigned to each element in the widget once. This will prevent screen readers from repeating the same link multiple times and unnecessarily consuming their time.

Another example is the improvement made to the Posts Widget. Screen readers will focus exclusively on post titles and ignore irrelevant visual content such as “Read more” CTAs and the featured image alt texts. This will improve visitors' experience while browsing the post widget with assistive technologies. For more information on accessibility improvements, check out the developer blog which will be posted in the coming days.

 

Notes in Editor Top Bar

 

An icon for the Notes feature has been added to the Top Bar. This makes it easier for you to collaborate with team members and clients by allowing you to open the Notes mode right within the Editor.

To use the Top Bar, activate the Top Bar experiment by going to WordPress Dashboard → Elementor → Features.

 

---

More Improvements

Free version

• New: Grid widget is now accessible in the widgets panel, enhancing workflow and user experience
• Tweak: Enhanced TTFB metric by optimizing controls display condition functions in the Editor (props @MajorChump)
• Tweak: Enabled Flexbox Container feature by default for new installations
• Tweak: Upgraded HTML Structure for Tabs Widget
• Tweak: Implemented accessibility improvements in Nested Tabs (✅ ♿ 🐞 Bug Report: Nested Tabs use the wrong ARIA attributes - [ED-7339] #22935)
• Tweak: Implemented CSS logical properties for border-radius in Elementor Editor
• Tweak: Implemented CSS logical properties in Container, Accordion and Tabs widgets
• Tweak: Enhanced dropdown preview for Global Typography styles
• Tweak: Enabled Improved Asset Loading feature by default for all sites
• Tweak: Promoted Grid Container feature to Beta status
• Tweak: Replace CSS float with other layouts in the Editor
• Tweak: Concealed the 'Empty View' cell within the Grid Container to prevent distortion of the preview
• Tweak: Updated eicons library to v5.23.0
• Tweak: Added keyboard accessibility to a link in Icon Box widget
• Tweak: Added keyboard accessibility to a link in Image Box widget
• Tweak: Added 'Download System Info" button to the top of Elementor System Info screen
• Fix: "Add New Container" functionality not functioning correctly in Finder
• Fix: Justify Content and Align Items controls are not functioning as expected in responsive mode in Container widget (✅ 🐞 Bug report: bug in container - Justify Content and Align Items do not change on mobile and tablet mode - [ED-7526] #19363)
• Fix: Wrong structure of predefined Container layouts in RTL (✅ 🔣 🐞 Bug Report: RTL - Add Container Dialog shows inverted structure icons - [ED-9955] #20184)
• Fix: Editing a post or page created in Gutenberg with Elementor resulted in sections being displayed instead of containers (✅ 🐞 Bug Report: Editing content created with the default editor in Elementor, generates a Section with a Text Editor inside instead of a Container when the Flexbox Container experiment is active - [ED-9940] #20282)
• Fix: Translated blending mode options in heading.php for improved usability (props DAnn2012)
• Fix: Use default placeholder set in URL control (props @DAnn2012)
• Fix: Improved translation functionality in the Editor (props @DAnn2012)
• Fix: Spacer not functioning as intended in Container widget
• Fix: 'Full-width' container width units switch from % to PX in smaller breaking points in Container
• Fix: Styling from the parent Accordion was being inherited by an Accordion placed inside it in Accordion widget
• Fix: Title is not breaking in Recently Edited modal in Editor Top Bar

Pro version

• Tweak: Hide navigation arrows when there is only one slide in the Loop or Nested carousel (🐞 Bug Report: Loop carousel bug - If the number of posts is low, the arrows will still be displayed. #22056)
• Tweak: Used appropriate image alt in Testimonial Carousel widget (✅ ♿ 🐞 Bug report: Alt image -> testimonial-carousel - [ED-11551] #17680)
• Tweak: Optimized Scroll Snap functionality when using Container widget
• Tweak: Enhanced Elementor Role Manager functionality when using Containers
• Tweak: Implemented accessibility improvements in Menu widget
• Tweak: Added Notes feature to the Editor Top Bar
• Tweak: Replace CSS float with other layouts in the Editor
• Tweak: Upgraded HTML Structure for the Menu widget
• Tweak: Implemented CSS logical properties in Carousel and Menu widgets
• Tweak: Added keyboard accessibility to a link in Posts widget
• Tweak: Loop Builder feature merged to version
• Fix: Addressed inconsistency in hover effect durations between icon, dropdown indicator colors, and text colors in the Menu widget
• Fix: Slides break if the parent container is set to HTML A tag in Loop Carousel and Carousel widgets (✅ 🐞 Bug Report: Loop item container not respecting min-height if HTML tag is A - [ED-11293] #22678)
• Fix: The icon size setting is not affecting uploaded SVG icons in the Menu widget

---

Make An Impact: Share Feedback Before Features Are Released

We’re always looking to get to know Elementor customers on a deeper level. If you’re interested in meeting with our team and sharing your insights, feedback, and feature requests, you’re welcome to sign up for some quality time with us here.

How to Install the Beta Version

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

• Go to Elementor > Tools > Versions
• Enable the beta tester feature
• Go to Dashboard > Updates and update to the latest beta version.
• This will set you up to test the new Elementor Free and Pro 3.16 Beta.

---

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 beta versions - open a new Bug report
• For feature requests - open a new Feature request issue
• For other comments specifically about this beta version - comment here

Designated time for release: September 12, 2023 (Estimated)

Many thanks for your support and help!

Cheers,
Elementor Team

[Michaelgimii]

Although there are no special new features in this version, it is a good update. Because many annoying bugs have been fixed and two small but important new features have been added and most importantly, performance improvements have been considered in this version.
With these interpretations, I think 22 days is too much for the release of this version. what do you think?😉

I found only 3 simple bugs while reviewing this version.

1- In container width control, placeholder is displayed in desktop and mobile mode, but not in tablet.

2- In the situation we see in the video below, the Grid Outline is not displayed well.

Grid.outline.mp4

3- In the nested tabs widget, it is very difficult to access the structure panel close button if you click the + button. Because it is placed under the handle of the container.

[nicholaszein]

Hey @Michaelgimii!

Nice to see you back here! 👊 😉

Let me start by thanking you for your feedback! We know there are not many shiny things, but our objective for this quarter was to focus on fixing bugs and improving the overall structure of our new components. It's great to know that you guys are supporting these efforts. Thank you! 🙏

As for the designated time for release, for the time being, we hope it should be enough to really squash any bugs for this version, and it's always good to have some spare time if eventually, we need to sort out any unexpected problems. 😉

Found Bugs

1- In container width control, placeholder is displayed in desktop and mobile mode, but not in tablet.

Good catch! We are going to investigate this one and see if we can fix it in this version. This might need some deeper investigation though, so please bear in mind that we might not be able to fix this on this version. Rest assured we are aware of this, and will do our best to handle inherited values for all breakpoints! 💪

2- In the situation we see in the video below, the Grid Outline is not displayed well.

Yep, we are aware of this one. We made some changes to the whole grid rendering framework to improve performance, and we should be fixing these inconsistencies. Thanks for bringing that to our attention! 🤓

3- In the nested tabs widget, it is very difficult to access the structure panel close button if you click the + button. Because it is placed under the handle of the container.

We will definitely need to take a look at this one on all our Nested Elements. We have a task already to make some changes to how the close button appears on the preset panel. Hopefully, we can sort it out during this beta! ✔️

Thanks for the feedback! keep it coming! 😁

[nicholaszein]

Hi @Michaelgimii,

2- In the situation we see in the video below, the Grid Outline is not displayed well.

This issue was solved in beta2! 🙌

[datgausaigon]

Hi, thanks for next update.
Can you preview this for this update #18331

[nicholaszein]

Hey @datverse! How's it going?

You are in luck my friend, this release covers exactly that feature request! 🙌

I just forgot to include it on the 3.16 Milestone. Apologies for that! 😅

But as Aviv mentioned above, it is indeed now possible to set both Column and Row gaps! 😉

Paraphrasing @avivu:

Updated Gap Control Between Elements

The "Gap between elements" control has been renamed to "Gap". Instead of a single range control for setting the gap between elements inside Containers, you can now control the horizontal and vertical gaps separately with a number input for each. This allows you to more accurately control the layout of a container.

I'll be updating all issues related to this version soon to reflect the new changes! Thanks for bringing that to my attention! 🙏

[datgausaigon]

@nicholaszein ❤️❤️❤️

[79ho3ein]

1- If we turn off the Grid Outline, the Empty View will appear again in the Grid container.

2- As @Michaelgimii pointed out, the Grid Outline does not display well.

3- In the tabs widget, even if we don't select an icon for the tab, the icon span is still rendered in the front end. On the other hand, if we remove the text and only use the icon for the tab, the text span will still be rendered in the front end.

[nicholaszein]

Hello, there @79ho3ein!

Thanks for joining this beta! 🙏

1- If we turn off the Grid Outline, the Empty View will appear again in the Grid container.

Good catch! We've created a task to fix this one. Thanks for the feedback! 💪

2- As @Michaelgimii pointed out, the Grid Outline does not display well.

Yep, we are going to fix this one, I'll link my answer to him here just for the sake of completion. Thanks!

3- In the tabs widget, even if we don't select an icon for the tab, the icon span is still rendered in the front end. On the other hand, if we remove the text and only use the icon for the tab, the text span will still be rendered in the front end.

Hmm, that's interesting. We will definitely need to take a look at this one. See if we can make them conditional. I'll check with the team and will get back to you with an answer ok? Please allow us some time to investigate if it's possible to make them conditional without impacting on anything else.

Thanks for the feedback!

[nicholaszein]

Hey @79ho3ein!

2- (...) the Grid Outline does not display well.

This issue was solved in beta2!

[perks98]

I can see the grid experiment is going to be in beta status. From my understanding this means no more expected major breaking changes are expected. Does this mean we will not get child grid item span control or is this a later / next year addition?

[nicholaszein]

Hi, @perks98!

Thanks for joining this beta! 🙏

To answer your question:

We are changing the status of the Grid Container to Beta because we believe it is stable enough to gain that status. We have no current plans of introducing breaking changes, but we are still going to wait to gather more data, and feedback to improve its functionalities. We are still considering expanding its functionalities. For now, that's all I can say about it.

[perks98]

Could your team consider removing the placeholder min-height once the first item is placed in the grid on the same row? As seen in the video below the min-height is bigger than button size so you have to fill the row to get rid of placeholder space. Ideally once the first item is added to the grid the placeholder space should flex and stretch to be the same height

2023-08-21.09-26-08.mp4

[nicholaszein]

Thanks for the feedback @perks, we will discuss this internally and see if we will add this.

Remembering: not all widgets are the same, and some may be very slim, which would make it very difficult to add other widgets in other areas. But we will definitely discuss this.

Thanks. 🙏

[nicholaszein]

Hi @perks98,

after discussing this, we decided not to change this behavior. It would impact other functionalities. By default, the Grid Container will wait until the entire row is filled up to adapt the height of the row.

[Michaelgimii]

Grid outline ignores the default top and bottom padding of the container.

now :

What it should be

[nicholaszein]

Hey @Michaelgimii, thanks for catching those!

We will work on fixing them! 🙏

[nicholaszein]

Hi @Michaelgimii,

this issue was solved in beta2! 🥳

[mgperdomo]

Hello, after this beta I am more and more disappointed with Elementor.

1-. Flexbox Container will already be active by default but will it still be RC?

Here doubts:

Because you should never use RC in any production site.

Will they add Flex Basis now? still missing.

2-. Why CSS Grid is in beta if it still lacks important features to really be CSS Grid.

My Doubt is?

If they are going to leave it like now that it is not of much use, they could comment on something or why this change.

Thank you.

[nicholaszein]

Hello, @mgperdomo!

Welcome to the beta, and thanks for sharing your feedback! 🙏

1-. Flexbox Container will already be active by default but will it still be RC?

The Flexbox Container will be active by default only on new installations. We consider it a stable feature. The RC moniker will be used throughout this beta, but we plan to remove it once this release is published.

Will they add Flex Basis now? still missing.

Flex basis will not be added to containers for the time being. However, you can always use custom CSS if you really need to use flex-basis. For now, the default width option should be enough for most use cases.

2-. Why CSS Grid is in beta if it still lacks important features to really be CSS Grid.

As we did with the Container, we are making the Gird Container a beta feature because we believe it is stable enough to become one. This doesn't mean we stopped developing it, and we are going to continue to improve it as we gather more data and feedback.

[mgperdomo]

@nicholaszein Surely it takes years to collect data on Grid, just as it took more than a year with Flexbox, elementor disappoints me more and more, for now I will not make more sites with Elementor until they have a more robust CSS Grid to be doing everything with Custom CSS will remove time, and CSS Grid is required nowadays to make sites more flexible but Elementor grid to be in beta for a joke. Greetings!

[nicholaszein]

@mgperdomo this is not the place to complain about Elementor.

You can reach out to Elementor Support.

Please respect our guidelines:

https://github.com/orgs/elementor/discussions/23196

[Michaelgimii]

Team Elementor, since you have fixed important bugs in this version, can you not solve the problem of displaying the horizontal scroll bar in the editor in this version? This is really a very simple but extremely annoying problem. Please watch the video below. This bug occurs for widgets that are on the right side of the container.

scrollbar.mp4

[nicholaszein]

Hey @Michaelgimii, we have discussed this a few times.

This is not a bug per see, it's just a result of a combination of your browser window size being too small and the desktop breakpoint reaching its limit, with the fact that the widget overlay border changes to 2px when you select/hover it. We understand this might appear like a bug, and that this might be bothering you, however, this does not break any functionality.

We have forwarded this to the team responsible for the Editor UI, however changing this is not part of this beta.

Thanks for understanding! 🙏

[nicholaszein]

Hello, @tobias992!

Welcome to this beta! 🤓

We hope to see your feedback about the features introduced in this version.

Fontawesome 6 integration is not part of this beta though. As we mentioned in our last Q3 Roadmap, our goal in this quarter is to focus on fixing bugs related to the new features we introduced this year and improving them for a stable release.

Please, remember to keep the conversation about this beta. Your feedback about the features being discussed here is crucial for releasing a stable and reliable plugin. We are eager to know about your experience with these new features. Thanks 🙏

[asadkn]

I would suggest adding a way to enable both Containers and Rows / Columns together.

A hybrid approach is often necessary for the long transitory phase.

[nicholaszein]

Hello @asadkn!

Welcome to the discussion about the 3.16 beta!

I think you might have misunderstood our announcement. Let me clarify:

Flexbox Containers are going to be the default element starting from version 3.16, but only for new installations. All existing websites will maintain the use of Sections/Columns if they haven't activated the Flexbox Container feature. However, you can still in fact use both side-by-side once you activate the Flexbox Container feature.

What you are suggesting is already possible. You just won't be able to drag & drop new sections anymore. But you will be able to edit them, copy, duplicate them, and even import them from your library if you wish.

I hope this clarifies the confusion.

[asadkn]

@nicholaszein Thanks for the explanation. However, sometimes you just want to continue using your existing system but also build a few layouts using the new system that aren't possible with the older one. Different tool sometimes more suitable for different purpose.

Would have been nicer to have the option to drag/drop new sections alongside containers as well - even if it's via a filter or programmatically enabled.

[nicholaszein]

@asadkn.

You can still use Sections if you need to. All you have to do is:

1. With Containers disabled, create a new Section Template in your Template Library. Call it something like "Legacy Section";
2. Click or Drag & Drop an Inner Section in the Preview;
3. Save the Section template.
4. Enable Containers;
5. When needed just open the library and import your "Legacy Section" template and edit it as you wish.

But we strongly recommend you start to use Containers. Not only they do exactly the same thing as Sections, but in an easier way, they also help reduce the DOM size significantly, are more performant overall, and are 100% compatible with new features.

The sooner you start using them, the better, and quicker your workflow will be. There is really no use case that is exclusive to sections. Containers are more than capable of covering all Section scenarios and more.

😉

[perks98]

Just noticed this issue with grid containers, the unit selector displays an incorrect unit for padding e.g. you select EM but it presents as PX, but in the preview and frontend it uses the right CSS of EM. It sort of corrects itself when you click on another element that isn't a grid container and go back to the grid container then the right one will show, very odd, I can only replicate it at the moment with the grid container.

2023-08-23.09-07-02.mp4

[nicholaszein]

Hi @perks98!

Thanks for reporting this! I can confirm the issue, and it happens with any unit. Changing tabs or sections, or even opening and closing the Layout section fixes the issue.

I'll report it to the team. 😉

[nicholaszein]

This issue was solved in beta2! ✅ 💪

[perks98]

Another issue with grid is the preview. With 'Grid Outline' set to 'Show' when you hide the sidebar to preview the page it adds extra space to the bottom due to the outline div added to the bottom. It seems when editing the page that div for the outline has 'position: absolute;' but on preview this type of CSS is removed so it is in the fold so whatever gap value is added becomes present.

2023-08-23.09-19-54.mp4

[nicholaszein]

Hi @perks98,

thanks for your feedback! 🙏

[perks98]

Problem with grid layout presets. When you use a grid layout preset like two columns, when you go to change the columns or rows to a custom unit (from 'fr' unit) you can't the first try, then when you go back and forth again you can then add your own input. Video below might be more clearer. But if you drag in the grid container widget you can change to custom unit input right away.

2023-08-23.09-55-41.mp4

[nicholaszein]

Hi @perks98,

sounds like this one is similar to the padding one. We will check to see if there is an overall issue with unit switching and the UI not changing.

Thanks for reporting! 🙏

[nicholaszein]

Hi @perks98,

this issue was resolved in beta2! 🙌

[perks98]

While in the editor I keep getting the following error in the console:

Seems to appear if you use the Elementor Pro theme builder for the header or footer and used the grid container widget in either of them. Removing any grid containers or disabling the header or footer that contains the grid element seems to remove the error from the console. The error stacks up when you use the responsive view.

[nicholaszein]

Thanks @perks98! 🙏

We are going to take a look at this and see if we can squash these errors! 💪

[avivu]

Hi all,

We just released Elementor v3.16 Beta 2.

The versions include the following:

Free version

• Tweak: Ensured that the Container Gap remains backward compatible in Container widget
• Fix: Custom unit inheritance problem in mobile mode in Grid Container (✅ 🐞 Bug Report: Gird Container Column Custom Units are not inherited on mobile mode - [ED-10282] #22289)
• Fix: Incorrect left and right values in Container dimensions control when using RTL mode
• Fix: Website content changes and is not presented as expected after utilizing the Data Updater

Pro version

• Fix: Sticky container incorrectly adjusts its width when transitioning from a smaller breakpoint to a larger one within the Editor

–

Thank you!

[Daveden2]

@penum, I just noticed that I couldn't find any skip link on my test site. It seems it was omitted in this update. I'll do more testing later on to confirm.

[penum]

you can look here : https://nuvisions.de/

[Daveden2]

@penum I looked at the link. There is a skip link but the problem is that page's main content area doesn't have the CSS ID of #content. Ideally, it should be <main id="content">Your Page's Content</main>

Here's how your's looks:

As a result, the skip link is pointing to nowhere. That might be a problem with the theme. In your page settings, did you set the page layout to "default"?

This is how it should be:

In my case, I didn't even see any skiplinks at all in the Elementor 3.16 beta 3

[penum]

Thanks alot, now i find it. It was in the "HelloElementor" Theme. I disable it now by a function. Thank you for your great help.

[perks98]

There is a problem with grid alignment when using boxed content width. The e-con-inner class has a height of 100% so if on the main grid container you set a min-height of 500px the inner div box will be the same height if it can, the problem is with the grid if you need to align things to be more central in that height, you can't. Please remove the height 100% style and add align-self controls to the e-con-inner div and set the default self-align for it to stretched for backward compatibility.

Expected:

Actual result:

Had to use this CSS to correct:

selector > .e-con-inner {
    height: auto;
    align-self: center;
}

---

Video if this visually explains it better:

2023-09-05.15-54-29.mp4

[perks98]

In case anyone else has the same issue when setting a min-height, rather than use custom CSS you can use the following settings: Rows: Auto (custom input), Align Content: Center.
It isn't obvious that when you enable custom input for columns or rows you get an extra option each. I think this needs to be made to be more intuitive and easier to understand from a glance...

[nicholaszein]

Hey @perks98,

I'm sorry for the delay. I missed your comment. 😕

The 100% height class is necessary for compatibility with virtually any widget, especially when setting up equal heights. But I can see that this might cause undesired behaviors in some cases as you pointed out. We will investigate this further, and see if we can find a solution. But for now, we have no plans to change these styles.

Thanks for bringing this to our attention! 🙏

[perks98]

@nicholaszein could your team consider not having 'Rows' set to anything from first adding (so it is unset or on auto) and have the 'Align Content' option appear by default? When I have played with grid CSS multiple times in the past I almost never have to touch the rows template, but in this case the controls force you from the start to have 1 or 2 rows.

[nicholaszein]

@perks98,

Converting code (CSS) to no code (Elementor) to build CSS Grids is a tricky feat. Grids are kind of complex, and there is no easy way to translate them to an interface without making it complex or compromising on some aspects. I myself tried a lot of different tools, and I have yet to find one that is as feature-rich but also easy and intuitive to use. This is our goal with the Grid Container.

However, the Grid Container is still an experiment in its infancy, so there is definitely room to grow or improve. So we will definitely consider your suggestions! I can't promise they will be implemented, but we will make sure to consider it and see if we can fit it into all the other features as well (it has to work in many contexts).

Thanks for your feedback! We really appreciate it! 💪

[perks98]

The eicons are Elementor Icons used for the user interface of the builder I believe. You can see their Elementor Icon list here: https://elementor.github.io/elementor-icons/

I do agree that their Font Awesome library needs updating to include new social media icons like Twitter X and Threads.

[avivu]

Hi all,

We just released Elementor v3.16 Beta 4.

The versions include the following:

Free version

• Fix: Added missing units to the Gap control in the site settings
• Fix: Gap control negative value issues in Container

Pro version

• Fix: 'Fallback: Recent Posts' option malfunctions in the Query control (✅ 📚 🐞 Bug Report: Fallback for related posts not working in the Posts widget - [ED-10701] #21436, ✅ 🔗 📚 🐞 Bug Report: Query Control Fallback Query Bug (Duplicate of #21436) - [ED-10701] #23259)
• Fix: Dropdown color has incorrect color when Icon Experiment is active in Menu widget

–

Thank you!

[fabigrafo]

I think it looks good now! :)

[nicholaszein]

Thanks for the feedback @fabigrafo! 🙏

[shahjehan-wpbrigade]

Some custom widgets are not showing in elementor 3.16.0

[EXECdesign]

We just released Elementor v3.16 Beta 4.

* Fix: Dropdown color has incorrect color when Icon Experiment is active in Menu widget

^^That one had been around for ages! Really hope it won't come back again with another update...

[nicholaszein]

Thanks for the feedback @EXECdesign! 🙏

We hope it will as well. 🙂

[nicholaszein]

Hi, @EXECdesign.

Please keep in mind that the Taxonomy Filter is an Alpha experiment, and it does not have all the planned functionality yet. It's a work in progress, and we will be adding more functionality in future versions. Feedback like yours is essential for us to understand the needs of our users!

However, this feature is not part of the 3.16 release.

🔗 🚀 There is already a similar request submitted by someone here #23418

Feel free to continue the conversation and cast your ⬆️ Upvote there! 👉

---

Please, remember to keep the conversation about this beta. Your feedback about the features being discussed here is crucial for releasing a stable and reliable plugin. We are eager to know about your experience with these new features. Thanks 🙏

Kind regards

[nicholaszein]

Hello @creativeart,

See my answer to @EXECdesign above. 👆

Please, remember to keep the conversation about this beta. Your feedback about the features being discussed here is crucial for releasing a stable and reliable plugin. We are eager to know about your experience with these new features.

Thanks 🙏

[davidamarek]

Agree, I need to only show some categories in the filter.

…

On Mon, 11 Sept 2023, 14:53 creativeart, ***@***.***> wrote: Have a huge issue with the taxonomy filter because of a missing absolute basic functionality: I just can choose 'categories' or 'tags' - but I *can't filter* them further. So I have *all* categories in my taxonomy filter list in the frontend. *I absolutely have to include/exclude categories* to use that wonderful feature sensibly! JetFilters also offers the option to only show child categories which would also be great (and only 1 switch button), but configuring the categories is absolutely essential. Will thia also come with 3.16? Totally agree with you. It also would be great if we could use the Filters widget on archive page ^^ It's a must i think. — Reply to this email directly, view it on GitHub <#23486 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJEDBD3ARI6T7OSF2K6PRFDXZ4JUVANCNFSM6AAAAAA3XKB3ZE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.*** com>

[nicholaszein]

Hi @davidamarek,

please join the conversation at #23185 and cast your vote. 😉

[Michaelgimii]

Hi team, Will the release date be extended?

[fabigrafo]

Why should it?

[Michaelgimii]

I don't know, I just wanted to ask. Have all reported bugs been fixed?

[fabigrafo]

In my opinion, yes. I think a bug fix update like this should happen more quickly, but it's okay as it is. I hope for new features in the near future.

[nicholaszein]

Hi @Michaelgimii,

as you can see, we have released the final version of both Elementor and Elementor Pro 3.16.0.

[79ho3ein]

I just encountered a new bug that I hope will be fixed before the official release...

If we add the container through the structure panel, the Gaps control values ​​link is disabled by default.

Gpa.bug.mp4

[nicholaszein]

Hi @79ho3ein,

when you add a Preset Container by clicking on the plus ➕ icon inside the Editor Preview area, it will have its own Settings. This is not exactly a bug, it's only pre-set to be unlinked.

We have already released Elementor Core v3.16.0, and Elementor Pro v3.16.0 today. If you still think this is a bug, please submit a new 🐞 Bug Report, so we can help you better.

Kind regards

[perks98]

3.16 has been released. Encountered an issue. @nicholaszein how does Elementor define "new installations" as the company I work for uses a plugin called "Themesflat Addons For Elementor" for a handful of sites and it doesn't seem to work with containers. Updated an install today that has used sections for over a month and now it has containers feature enabled and widgets from "Themesflat Addons For Elementor" have disappeared. Just need to know how far back is a website considered "new" so I can check those installs for faults or third-party issues?

[nicholaszein]

Ok, thanks for the feedback @perks98!

This is really helpful information. I will relay this to the team for troubleshooting! 🙏

As soon as we have any further info I'll let you know. I'll level this discussion open until we have sorted this out.

[asadkn]

@nicholaszein The old hooks haven't been removed, but they have simply stopped working. They only work when WP_DEBUG is enabled (and the warnings are also shown then). Is there any open bug report for this that I can add to?

[nicholaszein]

Hi @asadkn,

Thanks for the feedback. We are investigating this.

🙏

[perks98]

@nicholaszein I can see 3.16.2 is out and mentioned fixes around third-party plugins and deprecation issues. From checking sites that were affected they seem to be fixed now 👍

[nicholaszein]

Hi @perks98,

yes, that's correct. We reverted some changes we've made to better handle deprecation messages. These changes inadvertently caused outdated 3rd-party add-ons that use deprecated code to not work correctly. We had to revert those changes to accommodate these add-ons.

While we do understand the complaints of users, and we don't want our users to experience any problems with updates, it's crucial that 3rd-party developers make their add-ons compatible with the current code. It would mean a lot if you reached out to the add-on developers and asked them to update their code. We are trying our best to get them onboard, but many won't make any changes unless they have users reporting issues.

Thank you for taking the time to report this to us, and for giving us the feedback needed to find a solution for this. We really appreciate it!

Kind regards

[alleninfotrust]

FYI, manually firing the action in functions.php fixed this issue for me:

if (!function_exists('elementor_widgets_init')) { function elementor_widgets_init() { if (!did_action('elementor/loaded')) { return; } do_action('elementor/widgets/widgets_registered', Elementor\Plugin::$instance->widgets_manager); } } add_action('init', 'elementor_widgets_init');

[datgausaigon]

Hi, I got a Issue after update, I created a Issue for this, please check
v3.16.0 Sticky Container Padding 0 when Sticky is "Active" #23758

Thanks ❤️

[shahjehan-wpbrigade]

Some custom widget are not showing in elementor 3.16.0

[nicholaszein]

Thank you @datverse!

We are on it! 😉 💪

[nicholaszein]

@shahjehan-wpbrigade,

Please update Elementor to the latest version. This has been fixed already. If you are the owner of the custom widgets, you should update your code to remove the usage of deprecated methods. The methods in question were deprecated in version 3.5, released 2 years ago.

Please follow the documentation to know how to use the current methods:

• Developers API - Getting Started: https://developers.elementor.com/docs/getting-started/
• Deprecation Process: https://developers.elementor.com/docs/deprecations/
• 3.5 Deprecations: https://developers.elementor.com/v3-5-planned-deprecations/

[nicholaszein]

Hey, beta testers!

📢 Elementor Core and Elementor Pro v3.16 have been released! 🥳

Thank you all so much for contributing to this beta, and for your feedback and efforts. Especially for reporting found bugs in this release. 🙏

Your contribution is priceless, and we are very grateful for having you on board with us! 💪

I'd like to especially thank our contributors who helped make this release possible:

• @Michaelgimii
• @datverse
• @79ho3ein
• @perks98
• @mgperdomo
• @asadkn
• @Daveden2
• @Joliamendi
• @webtechhardik
• @fabigrafo
• @Henzxon
• @m1ga
• @toineenzo
• @penum
• @EXECdesign

Thank you! See you on the next one! ❤️ 💪 🚀

✅ Feel free to check it out and update your plugins to the new version!

Cheers 🥂

Changelogs of Elementor Core and Pro
Elementor Core
Elementor Pro