search

elementor / elementor

The most advanced frontend drag & drop page builder. Create high-end, pixel perfect websites at record speeds. Any theme, any page, any design.
https://elementor.com/
GNU General Public License v3.0
6.61k stars 1.42k forks source link

✅ 🚀 Elementor v3.6.0 Beta 5 Release 🚀 #18063

Closed shilo-ey closed 2 years ago

shilo-ey commented 2 years ago

Beta 5 UPDATED - PLEASE READ BELOW!

Cover for Hub

Hi Elementor Beta Testers 👋,

We are incredibly excited to introduce our new beta version, Elementor 3.6, which includes new features that will transform the way you build websites with Elementor.

This version includes the long awaited Flexbox Containers, which enables you to build more complex and lightweight layouts with improved performance, as well as additional features that accelerate the way you set up new websites. Elementor 3.6 includes:

Before testing this version, please make sure you are using:

Introducing Flexbox Containers - Harness the Power of CSS Flexbox in Elementor [Experiment]

FlexBox Containers

Flexbox Containers are a new lean layout structure in Elementor, that allows you to achieve pixel-perfect responsive designs, and highly advanced layouts, quickly and with a much slimmer markup, which reduces the DOM output and improves performance significantly.

With Flexbox Containers, you can place widgets directly inside a Container, as well as nest Containers. Additionally, you can improve the user experience by making the entire Container clickable by adding a link to it. Then, you can control the layout and distribution of elements within the Container, and adjust your content to every screen size, resulting in greater responsiveness, without compromising on speed.

Following several months in the Dev Edition, and implementing a lot of feedback from the community, Flexbox Containers are introduced as an alpha experiment, and should be used with caution, and not on a live website. When the experiment is turned on, you will be able to add new Containers to a page, instead of Sections, Columns and Inner Sections. You’ll also be able to add Containers to an existing page that was previously built with the section-column layout.

Please Note: If you deactivate the experiment, every Container you created will be removed from your website, you will be able to return them if you reactivate the experiment and restore a previous revision.

Below you will find the controls that adjust the Container’s layout, and their behavior:

Container:

Items:

Individual element (widgets and inner containers):

On the individual widget within the Container, users will able to determine the following from the Advanced tab on the individual widget

In addition, the Width and Position controls have been made more accessible, and are located in the layout section in the advanced tab of a widget, as a result, the positioning section has been removed and the inline position will not function inside containers.

Convert your Legacy Layout (Section-Column) to the New Container Layout

To ease your transition from the Section-Column to the Flexbox Container layout in existing pages, you can use the converter to save valuable time, and avoid the redundant task of dragging in all your widgets and content.

The converter can be found under the layout tab when you click on a section, or in the page settings (cogwheel icon) to convert an entire page. Clicking 'Apply' will create a new duplicated container beneath the chosen section, with all the original content inside in its appropriate position.

To enjoy the full benefits of Flexbox Containers, we recommend reviewing the resultant Container, and exploring how the layout can be further improved. Once you’re satisfied that all the content has been optimally converted from the Section to your new Container, simply delete the Section.

Here’s how to test it:

  1. Go to Elementor > Settings > Experiments and activate the “Container” experiment
  2. Create a new page and start building your design.
  3. Add a new Container with the plus button in the Editor and choose your desired structure, or drag the Container widget to the Editor.
  4. Drag in a few widgets, and adjust their layout and direction within the Container using the controls in the Container’s layout tab.
  5. Adjust the order of the widgets within the Container and adapt it to each device.
  6. Create a Container with three
  7. Try using the HTML Tag: a to wrap a container as a link
  8. Try using Overflow: auto option to add scroll when explicit width is set to a container (horizontal scrolling)
  9. Try out the different items ordering capabilities
  10. Try positioning a single widget, by clicking the widget and in the advanced tab, align self.
  11. Make sure your design is consistent both on the front end and in preview
  12. Make sure your design is responsive and looks as you would expect it to on various devices

New Capabilities in the Import/Export Feature

Import export plugins

The Import Export Template Kit feature accelerates the process of creating a website significantly. This feature allows you to export the Content, Site Settings, and Elementor Templates (Theme Parts for Pro users) from one website and import it to another, and also allows you to import a full website kit to your website.

To improve your process further, the Import / Export process now includes:

Here’s how to test it:

  1. Go to a site that you wish to Export and access its WordPress dashboard
  2. Go to Elementor > Settings > Experiments and make sure the Import / Export Kit experiment is active
  3. Make sure this site uses publicly available plugins (non-premium ones, only WordPress repository hosted plugins) other than Elementor and Elementor Pro
  4. Go to Elementor > Tools > Import / Export Kit and click Export
  5. Step 1- Go through the first phase and select which components to export
  6. Step 2- Make sure to include all relevant plugins
  7. Once the export process is done make sure that the summary screen is presented correctly
  8. Create a new site and install Elementor (and Elementor Pro if available) only
  9. Go to Elementor > Settings > Experiments and make sure the Import / Export Kit experiment is active
  10. Go to Elementor > Tools > Import / Export Kit and click Import
  11. Upload the zip file you downloaded and start the import process
  12. Select the relevant required plugins and proceed with the process as instructed in the interface
  13. Once the process has been completed please make sure the summary screen introduces the relevant content and every link from the summary screen link to the correct place
  14. Redo this process for various situations and states of plugins

New Onboarding Wizard - Get Started With Your Website Efficiently

Onboarding wizard

The new onboarding wizard will enable you to set up your next website in a truly friendly and efficient manner, allowing you to get started quicker. Throughout the wizard, you will be able to configure the basic configurations of your website including setting up the ‘Hello’ theme, adding your site name, and uploading your logo. Then, you will complete the wizard by choosing whether you want to start with a blank canvas, or import one of Elementor’s full website kits.

Here’s how to test it:

  1. Create a fresh WordPress installation and install Elementor 3.6 Beta
  2. Once activated you will be directed to the Onboarding wizard screen that will guide you through the basic settings needed when creating a new site
  3. Make sure you complete this flow and try creating a site from scratch with the blank canvas, or using one of the website kits.
  4. Make sure the settings are presented correctly in your site (logo, site name, etc...), in Site Settings > Site Identity menu, and on the WordPress dashboard Settings screen

Rearrange your Global Colors and Fonts

Global Colors and Fonts

One of the first steps you take when building a website is setting up your design system, choosing the colors and fonts the website is going to have. With Global Colors and Fonts, in the Site Settings, you are able to easily set up your 4 system colors and fonts (Primary, Secondary, Text, and Accent) and add your custom ones.

Up until now, there was no clear distinction between system colors and fonts and custom ones, and any time you would add another custom color or font, it would take the last place on the list. But sometimes, you want to change the order of your fonts and colors. With this update, the separation between system colors and fonts and custom ones will be clearer, and you will be able to rearrange their order. For example, if your website’s custom colors include various shades of pink and blue, you can arrange all your pinks in a row, and all your blues in a row in the Global Colors under Site Settings. Additionally, you will also be able to change the position of your system fonts and colors, for example, you can position your Secondary font on top of your Primary one in the Global Fonts under Site Settings.

Here’s how to test it:

  1. Go to Elementor Site Settings and click on the Global Colors section
  2. Make sure all of your global colors are visible and work as expected
  3. In system colors, hover over the #hex (color box) and to expose the dragging button
  4. Drag the color up or down to the desired position within the system colors
  5. Follow the same directions in Custom Colors
  6. Please create a new global color, and after that, try to delete it
  7. Try to drag a color from the custom section to the system section, and validate that you can’t drag it from one section to another
  8. Follow the same instructions with the Global Fonts section
  9. Make sure everything works as expected in the Editor and in the front end

Performance Improvements

Pereformance (Lazy load carusel)

Lazy Load Added to Carousels

Lazy load empowers you to improve performance on your website by only loading the content that is immediately visible and necessary and loading the rest as users scroll and the content becomes visible. With the new Lazy Load control in the Image Carousel widget and Background Slideshow feature in every section, your website will load faster.

Optimized DOM Output

The Optimized DOM Output Experiment has been extended, to remove the elementor-section-wrap

More Improvements

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. Or download Elementor’s Dev Edition. Talk soon!

How to Install the Beta Version

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

Notes

For bugs and remarks, please reply with a comment on this issue here on GitHub. Please keep this related to the Current beta Only! any other issue or feature request, feel free to open a new issue.

Designated time for release: March 23, 2022 (Estimated)

Many thanks for your support and help! Cheers, Elementor Team

pauserratgutierrez commented 2 years ago

First of all, you did an amazing work with the container! 🚀

I want to suggest something. We have the ability to set the direction that the elements inside a container will follow. This is great, but obligates anyone to add multiple containers to create stacked rows and columns. Here's an example: image

To avoid this multiple container need, I suggest to have a new option on the main conteiner that triggers a break when a number of elements is reached. In my example I would use "Break when elements reach: 2", so when the container automaticly detects 2 elements (Monday, 13:00 - 16:00) a break will happen and the next 2 elements will be displayed in the next line, and so on.

pauserratgutierrez commented 2 years ago

What will happen if the Exported Kit has Premium or Paid plugins? Will them be installed too? I would also know if this new Importing process also imports configurations such as all Woocommerce products, with it's thumbnails and variations.

pauserratgutierrez commented 2 years ago

I find the rearranging of colors and fonts very useful!

But I don't understand why there needs to be a difference between system and custom fonts or colors. In my opinion Elementor needs to get rid of that System thing. A website shure needs default things to display dummy content or being a fallback utility in technical cases like if the user erases something. But I personally don't like having there System colors that I can't get rid of but change.

I suggest making this dafault System things automaticly apply if no other custom color or font is found. When the user goes to custom colors and fonts for the first time, it should be empty and encourage him to add some. As soon as the user adds some, get don't use the default System ones but the defined ones by the user.

I thing the same about the System Default Kit automaticly created on any Elementor site. We can't get rid of it. The system should have it internally, but encourage the user using an amazing Wizard with steps to customize his kit, with a custom name. Would also bee cool to be able to have multiple kits and let us choose which one we want to have active.

I personally don't like having System things showing. I want any of my websites to be as easy as possible, sometimes clients don't know what they are doing and mess it up.

fabigrafo commented 2 years ago

Finally the Containers are here!!

The first thing I noticed in the 3.6 beta (also since Dev-Edition) when testing the container and old structure is that the page loads very slowly since the container experiment was activated. It seems like the CSS is loading very slowly. no other experiment is active and no other plugin except the correct Elementor Pro version. It doesn't matter whether it's sections and columns or the new containers. The video shows a freshly created page with Elementor templates.

https://user-images.githubusercontent.com/57997262/156634316-83792ebb-4f32-4df8-9ea1-0a137dba1387.mov

Import/Export keeps getting better and more useful. But I agree with the question of the previous speaker, whether the content and settings are also taken over from the plugins?

And finally you can change the order of global colors and fonts. This has been requested since the introduction of 3.0 and now Elementor has finally implemented it - thank you very much!

New Onboarding Wizard is sure nice to have for new website. I not the biggest fan of Plugin setup pages, but Elementor looks good and efficient.

Otherwise, the new responsive options for stroke and icons should be emphasized. Good work, keep it up. Another tip from my side, the expected releases have now been postponed several times in all the last betas, maybe you can just plan a longer time right at the beginning.

But if it's so quick, that's great!

ghost commented 2 years ago

Great job guys! 👏

At the moment the only problem I found is that the width control of the containers does not work on breakpoints, it only works on the mobile (normal) breakpoint.

Also another detail would be to be able to have all the sides of the margins active, it is useful in some designs and that would be a limitation.

I will keep trying. Thanks

pauserratgutierrez commented 2 years ago

A quick question: Will all the Elementor premade sections, blocks, popups, entire websites and kits be automatically re-designed to use this new container?

fabigrafo commented 2 years ago

A quick question: Will all the Elementor premade sections, blocks, popups, entire websites and kits be automatically re-designed to use this new container?

Lots to do for the Elementor designers.. 😅

MichaelDarko commented 2 years ago

The container feature is great. I'm glad you didn't decide to make something half-baked and you're giving us the full power of flexbox. This is what I need as a professional designer and this is where Gutenberg is not going to go, because it needs to stay simple. Gutenberg for layman users, Elementor for power users and professionals.

Two suggestions:

1. User interface

Functionality-wise, the container seems to do the job. But UI/UX is a mess. Using flexbox in Webflow is way more intuitive. Same functions, much better UI. Elementor's UI is getting old and is not working for these more advanced options.

In Webflow, everything is perfectly unified, much more compact and sensibly divided.

In Elementor, there is so much scrolling, jumping between tabs, looking for things, opening sub-tabs, then opening typography popups and so on. The styling options are inconsistent. Sometimes there is a responsive control, hover control and sometimes not. You never know what you're gonna get.

Why is margin and padding in the Advanced tab? What's advanced about that?

Now, when you're introducing more complex styling features, the old UI is really ruining the experience.

I know you're working on a new UI, I've seen the prototype screenshot. But that just seems like more modern graphics for the old interface, but not much difference in terms of UX.

The user interface is the core of the experience and it deserves big improvements.

Have a look at Webflow's UI. I'm using both and Webflow is on a completely different level in terms of styling power and ease of use.

webflow

1. Flexbox needs auto margins

In frontend development, when we use flexbox, the capability to use "margin: auto" is fundamental. These things go hand in hand so I think it should be mentioned.

I already started a feature request: #17886

79ho3ein commented 2 years ago

First of all, thank you for this great update. I played with the container a lot, and there are a few that seem to not work well. Of course, I had previously reported all these cases in GitHub, but ...

1- If we have a container with two columns, it is not possible to access one of the containers and the handle of the main container prevents it from being displayed. https://prnt.sc/Lpw-trKmyFAO

2- If we put the containers inside each other, they are completely inside each other. https://prnt.sc/9auuDE_9D0Uj While nested containers should look like this : https://prnt.sc/MqUen6IYZYoa Even if we add a widget, it sticks perfectly to the container and has no space : https://prnt.sc/qXltXBmyptJT Shouldn't containers have 20px of space by default? Like sections and columns in previous versions : https://prnt.sc/zPUzNKoVEGG3 Am I wrong? It also causes bug number 4 to occur.

3- We cannot use left and right margins in containers : https://prnt.sc/W0JIiqAC71en This is a very big limitation. It is strange why it does not exist.

4- When we add the first widget, it is not possible to access the container handle :

https://user-images.githubusercontent.com/77163248/156678124-e4cd5d9c-1709-432b-8a0a-8dc0189704a9.mp4

5- If we have two containers and give the upper container more z-index, the lower section handles will disappear.

https://user-images.githubusercontent.com/77163248/156678987-c78a813d-fa98-4cae-9bf1-bd2d320046cf.mp4

This does not seem logical. Handles should not be affected by the z-index. They must be available under any circumstances.

6- In containers, the inheritance value is displayed for padding, but not for margin : https://prnt.sc/r_qpwWDIVF8_

Three suggestions

1- As mentioned in bug # 3, in containers, we can not margin left and right. But this is a weakness and could be better. It is better to have this restriction only for the first container. If we put another container in the first container, this restriction will no longer apply to the second container. So we can give the margin to the container from left and right. In general, it is better to have this limitation only for the first containers. Not for indoor containers This was exactly the case in previous versions. When we added a section, we could not margin it left and right. But when we put an inner section inside it, this limitation for the internal part no longer existed.

2- It would be great if the Align Content option was also displayed visually. It had a much better user experience. https://prnt.sc/u_VgBDSV7cpy

3- To fix bug number 2, isn't it better to add the container gap option to the container section? So, this will work as before (https://prnt.sc/fKBBEh-YxGcs). With better performance. By adding this option, we have both Elements Gap and container gap. Therefore, we can have complete control over both the distance between the elements and the distance between the containers.

Isn't this better? https://prnt.sc/RhnpjEJPKlwu

elasticeye commented 2 years ago

Hey. Two things with the Container element:

  1. Can't drag and drop widgets from the screen (not from the widgets panel) to a new container. See video here
  2. Why is right and left margins on container disabled? On the columns, I could set the left and right margins so that I could create a "gap" between the columns. That is not possible with the container? Let's say I have three containers in a row, and I want the middle container to have some gap/space on left and right side. Not possible? I know you could set the "elements gap" to a value, but that would set a gap between ALL containers in the row.
perks98 commented 2 years ago

Hi Elementor Team, Like everyone says the flex container feature is a great addition. But please review #17983 issue I submitted since dev version but still an issue in this beta as when the container content width is set to boxed and you add padding on responsive option the padding is ignored, while in full width mode it works. If this is a problem with how boxed and flex css works then please disable left and right padding as options for the container when boxed is selected to remove any confusion.

Padding on container for tablet: Screenshot_191

Boxed width: Screenshot_189

Full width: Screenshot_190

79ho3ein commented 2 years ago

In Site Settings > Buttons, the background color for the button does not work. https://prnt.sc/V1Jw_wCO6miY In the site settings, change the background color of the button, then add the button widget. The desired color has not been applied.

Finder still does not work properly. Please review this issue : #17569

DavidGMiles commented 2 years ago

Upgrade to beta on our dev site - https://development.natureslens.co.uk/

Now cannot edit any page in safe mode or normal mode - just get the grey screen of death - no pallete, no page, no spinner, nada

== Server Environment == Operating System: Linux Software: LiteSpeed MySQL version: MariaDB Server v10.5.13 PHP Version: 7.4.26 PHP Memory Limit: 512M PHP Max Input Vars: 1000 PHP Max Post Size: 68M GD Installed: Yes ZIP Installed: Yes Write Permissions: All right Elementor Library: Connected == WordPress Environment == Version: 5.9.1 Site URL: https://development.natureslens.co.uk Home URL: https://development.natureslens.co.uk WP Multisite: No Max Upload Size: 2 MB Memory limit: 40M Max Memory limit: 512M Permalink Structure: /%year%/%monthnum%/%postname%/ Language: en-GB Timezone: 0 Admin Email: davidgmiles@me.com Debug Mode: Inactive == Theme == Name: Hello Elementor Version: 2.5.0 Author: Elementor Team Child Theme: No == User == Role: administrator WP Profile lang: en_GB User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.82 Safari/537.36 Edg/98.0.1108.51 == Active Plugins == Add Alt and Title to Elementor Image Version: 1.0.0 Author: Admin Columns Pro Version: 5.6.4 Author: AdminColumns.com Admin Columns Pro - Advanced Custom Fields (ACF) Version: 2.7 Author: AdminColumns.com Advanced Custom Fields: Extended PRO Version: 0.8.8.7 Author: ACF Extended Advanced Custom Fields: Image Aspect Ratio Crop Version: 6.0.1 Author: Johannes Siipola Advanced Custom Fields PRO Version: 5.12 Author: Delicious Brains Code Snippets Version: 2.14.3 Author: Code Snippets Pro Dynamic.ooo - Dynamic Content for Elementor Version: 2.4.0 Author: Dynamic.ooo e-addons EXTENDED Version: 2.2.2 Author: Nerds Farm e-addons for Elementor Version: 3.0.8 Author: Nerds Farm e-addons TEMPLATE Version: 2.0 Author: Nerds Farm Elementor Version: 3.6.0-beta1 Author: Elementor.com Elementor Pro Version: 3.6.3 Author: Elementor.com F4 Post Tree Version: 1.1.9 Author: FAKTOR VIER Gallery Custom Links Version: 2.0.6 Author: Jordy Meow iThemes Security Pro Version: 7.0.3 Author: iThemes LiteSpeed Cache Version: 4.5.0.1 Author: LiteSpeed Technologies MailerSend - Official SMTP Integration Version: 1.0.0 Author: MailerSend ManageWP - Worker Version: 4.9.13 Author: GoDaddy Max Mega Menu Version: 2.9.5 Author: megamenu.com Meow Gallery Version: 4.2.4 Author: Jordy Meow, Thomas Kim Meow Lightbox Version: 3.1.6 Author: Jordy Meow, Thomas KIM NaturesLens Site-Specific Functionality Version: 2019.03.04 Author: David Miles OoohBoi Steroids for Elementor Version: 1.9.0 Author: OoohBoi Perfmatters Version: 1.8.6 Author: forgemedia Popup Maker Version: 1.16.4 Author: Popup Maker PublishPress Future Version: 2.7.3 Author: PublishPress Rank Math SEO Version: 1.0.83 Author: Rank Math Rank Math SEO PRO Version: 3.0.7 Author: Rank Math User Menus Version: 1.2.9 Author: Code Atlantic WP Grid Builder Version: 1.6.4 Author: Loïc Blascos WP Grid Builder - Caching Version: 1.0.7 Author: Loïc Blascos WP Grid Builder - Elementor Version: 1.1.0 Author: Loïc Blascos Yoast Duplicate Post Version: 4.4 Author: Enrico Battocchi & Team Yoast == Must-Use Plugins == prime-mover-cli-plugin-manager.php Version: Author: == Elementor Experiments == Optimised DOM Output: Active Improved asset loading: Active Improved CSS Loading: Active Inline Font Icons: Active Accessibility improvements: Active Import Export Template Kit: Inactive Additional Custom Breakpoints: Inactive Hide native WordPress widgets from search results: Active by default : Inactive by default Flex Container: Inactive by default Default to New Theme Builder: Active Hello Theme Header & Footer: Inactive Landing pages: Inactive Color Sampler: Inactive Favorite Widgets: Active by default Admin Top Bar: Inactive Page Transitions: Inactive Form Submissions: Active by default Scroll Snap: Inactive == Log == JS: showing 18 of 18JS: 2022-02-21 12:16:29 [error X 10][https://development.natureslens.co.uk/wp-content/plugins/elementor/assets/lib/backbone/backbone.marionette.min.js?ver=2.4.5.e1:24:19952] View (cid: \"view295\") has already been destroyed and cannot be used. JS: 2022-02-22 12:54:31 [error X 173][https://development.natureslens.co.uk/wp-includes/js/jquery/jquery.min.js?ver=3.6.0:2:31703] field is not defined JS: 2022-02-22 16:07:17 [error X 1][https://development.natureslens.co.uk/wp-content/plugins/elementor/assets/lib/backbone/backbone.marionette.min.js?ver=2.4.5.e1:24:19952] View (cid: \"view95\") has already been destroyed and cannot be used. JS: 2022-02-22 17:17:34 [error X 3][https://development.natureslens.co.uk/wp-admin/post.php?post=228&action=elementor#:1:1] Identifier \'$dcWidgetIdInput\' has already been declared JS: 2022-02-23 08:42:13 [error X 2][https://development.natureslens.co.uk/wp-content/plugins/elementor/assets/lib/backbone/backbone.marionette.min.js?ver=2.4.5.e1:24:19952] View (cid: \"view240\") has already been destroyed and cannot be used. JS: 2022-02-23 10:53:15 [error X 159][https://development.natureslens.co.uk/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.5.5:2:326316] Cannot read properties of undefined (reading \'get\') JS: 2022-02-23 11:00:40 [error X 1][https://development.natureslens.co.uk/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.5.5:2:453832] Cannot read properties of null (reading \'getBoundingClientRect\') JS: 2022-02-23 14:57:23 [error X 3][https://development.natureslens.co.uk/wp-content/plugins/elementor/assets/lib/backbone/backbone.marionette.min.js?ver=2.4.5.e1:24:19952] View (cid: \"view262\") has already been destroyed and cannot be used. JS: 2022-02-23 15:45:09 [error X 2][https://development.natureslens.co.uk/wp-content/plugins/elementor/assets/lib/backbone/backbone.marionette.min.js?ver=2.4.5.e1:24:19952] View (cid: \"view260\") has already been destroyed and cannot be used. JS: 2022-02-24 16:29:44 [error X 4][https://development.natureslens.co.uk/wp-content/plugins/elementor/assets/lib/backbone/backbone.marionette.min.js?ver=2.4.5.e1:24:19952] View (cid: \"view100\") has already been destroyed and cannot be used. JS: 2022-02-24 18:48:11 [error X 3][https://development.natureslens.co.uk/wp-content/plugins/elementor/assets/lib/backbone/backbone.marionette.min.js?ver=2.4.5.e1:24:19952] View (cid: \"view225\") has already been destroyed and cannot be used. JS: 2022-02-25 14:02:46 [error X 4][https://development.natureslens.co.uk/wp-content/plugins/wp-grid-builder-elementor/assets/js/preview.js?ver=1.1.0:10:11909] Cannot read properties of undefined (reading \'forEach\') JS: 2022-02-25 17:20:25 [error X 32][https://development.natureslens.co.uk/wp-content/plugins/dynamic-content-for-elementor/assets/js/dynamic-posts-skin-carousel.min.js?ver=2.3.5:1:422] dceDynamicPostsSkinPrefix is not defined JS: 2022-02-28 14:15:10 [error X 6][https://development.natureslens.co.uk/wp-content/plugins/dynamic-content-for-elementor/assets/js/dynamic-posts-skin-carousel.min.js?ver=2.3.5:1:447] Can\'t find variable: dceDynamicPostsSkinPrefix JS: 2022-02-28 16:12:03 [error X 1][https://development.natureslens.co.uk/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.5.6:2:315310] undefined is not an object (evaluating \'this.container.isEditable\') JS: 2022-03-01 14:01:13 [error X 2][https://development.natureslens.co.uk/wp-content/plugins/elementor/assets/lib/backbone/backbone.marionette.min.js?ver=2.4.5.e1:24:19952] View (cid: \"view75\") has already been destroyed and cannot be used. JS: 2022-03-03 21:08:23 [error X 1][https://development.natureslens.co.uk/wp-content/plugins/elementor/assets/lib/backbone/backbone.marionette.min.js?ver=2.4.5.e1:24:19952] View (cid: \"view101\") has already been destroyed and cannot be used. JS: 2022-03-03 21:20:53 [error X 29][https://development.natureslens.co.uk/wp-content/plugins/elementor/assets/js/frontend-modules.min.js?ver=3.5.6:2:5384] Cannot read properties of undefined (reading \'toJSON\') PHP: showing 7 of 7PHP: 2022-02-23 07:42:19 [notice X 14][/home/naturesl/development.natureslens.co.uk/wp-content/plugins/elementor-pro/license/updater.php::84] Undefined index: new_version [array ( 'trace' => ' #0: Elementor\Core\Logger\Manager -> shutdown() ', )] PHP: 2022-02-23 11:47:09 [notice X 388][/home/naturesl/development.natureslens.co.uk/wp-content/plugins/elementor/includes/controls/base-multiple.php::87] Trying to access array offset on value of type null [array ( 'trace' => ' #0: Elementor\Core\Logger\Manager -> shutdown() ', )] PHP: 2022-02-23 15:00:41 [notice X 1][/home/naturesl/development.natureslens.co.uk/wp-content/plugins/elementor/includes/controls/groups/image-size.php::110] Undefined index: id [array ( 'trace' => ' #0: Elementor\Core\Logger\Manager -> shutdown() ', )] PHP: 2022-02-25 17:34:38 [error X 11][/home/naturesl/development.natureslens.co.uk/wp-content/plugins/elementor-pro/core/utils.php::72] Uncaught Error: Call to a member function get_main_id() on null in /home/naturesl/development.natureslens.co.uk/wp-content/plugins/elementor-pro/core/utils.php:72 Stack trace: #0 /home/naturesl/development.natureslens.co.uk/wp-content/plugins/elementor-pro/modules/forms/widgets/form.php(2089): ElementorPro\Core\Utils::get_current_post_id() #1 /home/naturesl/development.natureslens.co.uk/wp-content/plugins/elementor/includes/base/controls-stack.php(2192): ElementorPro\Modules\Forms\Widgets\Form->render() #2 /home/naturesl/development.natureslens.co.uk/wp-content/plugins/elementor/includes/base/widget-base.php(584): Elementor\Controls_Stack->render_by_mode() #3 /home/naturesl/development.natureslens.co.uk/wp-content/plugins/elementor/includes/base/widget-base.php(725): Elementor\Widget_Base->render_content() #4 /home/naturesl/development.natureslens.co.uk/wp-content/plugins/elementor/includes/base/element-base.php(447): Elementor\Widget_Base->print_content() #5 /home/naturesl/development.natureslens.co.uk/wp-co [array ( 'trace' => ' #0: Elementor\Core\Logger\Manager -> shutdown() ', )] PHP: 2022-02-28 14:47:34 [warning X 1][/home/naturesl/development.natureslens.co.uk/wp-content/plugins/elementor/includes/controls/base-multiple.php::87] Illegal string offset 'url' [array ( 'trace' => ' #0: Elementor\Core\Logger\Manager -> shutdown() ', )] PHP: 2022-03-04 09:45:05 [notice X 38][/home/naturesl/development.natureslens.co.uk/wp-content/plugins/elementor/modules/dev-tools/deprecation.php::301] The $control_id argument is deprecated since version 3.5.0! [array ( 'trace' => ' #0: Elementor\Core\Logger\Manager -> shutdown() ', )] PHP: 2022-03-04 09:46:21 [notice X 10][/home/naturesl/development.natureslens.co.uk/wp-content/plugins/elementor/modules/dev-tools/deprecation.php::301] The $control_id argument is deprecated since version 3.5.0! [array ( 'trace' => ' #0: Elementor\Core\Logger\Manager -> rest_error_handler() #1: /home/naturesl/development.natureslens.co.uk/wp-content/plugins/elementor/modules/dev-tools/deprecation.php(301): class type trigger_error() #2: /home/naturesl/development.natureslens.co.uk/wp-content/plugins/elementor/includes/managers/controls.php(523): Elementor\Modules\DevTools\Deprecation -> deprecated_argument() #3: /home/naturesl/development.natureslens.co.uk/wp-content/plugins/elementor/includes/managers/controls.php(501): Elementor\Controls_Manager -> register() #4: /home/naturesl/development.natureslens.co.uk/wp-content/plugins/dynamic-content-for-elementor/class/controls.php(60): Elementor\Controls_Manager -> register_control() ', )] Log: showing 17 of 172022-02-24 12:29:04 [info] Elementor data updater process has been completed. [array ( 'plugin' => 'Dynamic.ooo - Dynamic Content for Elementor', 'from' => '2.3.4', 'to' => '2.3.5', )] 2022-02-28 14:21:19 [info] elementor-pro::elementor_pro_updater Started 2022-02-28 14:21:19 [info] Elementor Pro/Upgrades - _on_each_version Start 2022-02-28 14:21:19 [info] Elementor Pro/Upgrades - _on_each_version Finished 2022-02-28 14:21:19 [info] Elementor data updater process has been completed. [array ( 'plugin' => 'Elementor Pro', 'from' => '3.6.2', 'to' => '3.6.3', )] 2022-02-28 14:21:19 [info] Elementor data updater process has been queued. [array ( 'plugin' => 'Elementor Pro', 'from' => '3.6.2', 'to' => '3.6.3', )] 2022-02-28 14:21:19 [info] elementor::elementor_updater Started 2022-02-28 14:21:19 [info] Elementor/Upgrades - _on_each_version Start 2022-02-28 14:21:19 [info] Elementor/Upgrades - _on_each_version Finished 2022-02-28 14:21:19 [info] Elementor data updater process has been completed. [array ( 'plugin' => 'Elementor', 'from' => '3.5.5', 'to' => '3.5.6', )] 2022-02-28 14:21:19 [info] Elementor data updater process has been queued. [array ( 'plugin' => 'Elementor', 'from' => '3.5.5', 'to' => '3.5.6', )] 2022-03-03 21:04:26 [info] Elementor data updater process has been completed. [array ( 'plugin' => 'Dynamic.ooo - Dynamic Content for Elementor', 'from' => '2.3.5', 'to' => '2.4.0', )] 2022-03-04 08:15:27 [info] Elementor data updater process has been queued. [array ( 'plugin' => 'Elementor', 'from' => '3.5.6', 'to' => '3.6.0-beta1', )] 2022-03-04 08:15:28 [info] elementor::elementor_updater Started 2022-03-04 08:15:28 [info] Elementor/Upgrades - _on_each_version Start 2022-03-04 08:15:28 [info] Elementor/Upgrades - _on_each_version Finished 2022-03-04 08:15:28 [info] Elementor data updater process has been completed. [array ( 'plugin' => 'Elementor', 'from' => '3.5.6', 'to' => '3.6.0-beta1', )] == Elementor - Compatibility Tag == Add Alt and Title to Elementor Image: Compatibility not specified Dynamic.ooo - Dynamic Content for Elementor: Compatibility not specified e-addons for Elementor: Compatibility not specified Elementor Pro: Compatibility not specified OoohBoi Steroids for Elementor: Compatibility not specified WP Grid Builder - Elementor: Compatibility not specified == Elementor Pro - Compatibility Tag ==

Rolling back to 3.5.6 made edits possible again

79ho3ein commented 2 years ago

other things...

1- If we set the widget width to custom, we can no longer select other modes such as inline. Because the selection option is hidden. So we have to delete the widget, so we can change the widget width to other options like inline again.

https://user-images.githubusercontent.com/77163248/156746684-6498d583-b913-4db3-abef-d0676bfd43df.mp4

2- Add the slides widget and then change the container to row. The slider is completely broken.

https://user-images.githubusercontent.com/77163248/156748106-73282437-30bd-40a9-aae6-8421713d1bd1.mp4

3- When we select these options to display the container, they are slightly replaced by dance. https://prnt.sc/f6VX0Ck7L0MZ As if the css is loading with a long delay.

4- If we have only one container, the default container mode will not be displayed on the tablet & Mobile. But if we add a two-column container, it displays correctly.

https://user-images.githubusercontent.com/77163248/156750324-f7d34de8-825a-4b82-9ea7-dc7589a4c92b.mp4

5- I do not know what the reason is, but by moving the mouse over the containers, and even some widgets, the width of the screen decreases and increases. (Actually the browser scroll bar is hidden and appears) Chrome browser - Windows

https://user-images.githubusercontent.com/77163248/156751066-4080fa38-c7c0-4f81-a3bd-d83c49658557.mp4

This is really nerve-wracking😁

fabigrafo commented 2 years ago

The container feature is great. I'm glad you didn't decide to make something half-baked and you're giving us the full power of flexbox. This is what I need as a professional designer and this is where Gutenberg is not going to go, because it needs to stay simple. Gutenberg for layman users, Elementor for power users and professionals.

Two suggestions:

1. User interface

Functionality-wise, the container seems to do the job. But UI/UX is a mess. Using flexbox in Webflow is way more intuitive. Same functions, much better UI. Elementor's UI is getting old and is not working for these more advanced options.

In Webflow, everything is perfectly unified, much more compact and sensibly divided.

In Elementor, there is so much scrolling, jumping between tabs, looking for things, opening sub-tabs, then opening typography popups and so on. The styling options are inconsistent. Sometimes there is a responsive control, hover control and sometimes not. You never know what you're gonna get.

Why is margin and padding in the Advanced tab? What's advanced about that?

Now, when you're introducing more complex styling features, the old UI is really ruining the experience.

I know you're working on a new UI, I've seen the prototype screenshot. But that just seems like more modern graphics for the old interface, but not much difference in terms of UX.

The user interface is the core of the experience and it deserves big improvements.

Have a look at Webflow's UI. I'm using both and Webflow is on a completely different level in terms of styling power and ease of use.

webflow

1. Flexbox needs auto margins

In frontend development, when we use flexbox, the capability to use "margin: auto" is fundamental. These things go hand in hand so I think it should be mentioned.

I already started a feature request: #17886

In line with this, I can only point out that at least in the "Layout" tab, the settings were much clearer a few dev versions ago, as this picture shows:

Bildschirmfoto 2022-03-04 um 12 42 48

I mean only the arrangement or the division. The progress in terms of content as it is now is good, there are already enough suggestions from other users above.

nreljed commented 2 years ago

there is a particular reason for the absence of auto wrap? I remember seeing several posts asking for this option I missed an episode ?

79ho3ein commented 2 years ago

The container feature is great. I'm glad you didn't decide to make something half-baked and you're giving us the full power of flexbox. This is what I need as a professional designer and this is where Gutenberg is not going to go, because it needs to stay simple. Gutenberg for layman users, Elementor for power users and professionals. Two suggestions:

1. User interface

Functionality-wise, the container seems to do the job. But UI/UX is a mess. Using flexbox in Webflow is way more intuitive. Same functions, much better UI. Elementor's UI is getting old and is not working for these more advanced options. In Webflow, everything is perfectly unified, much more compact and sensibly divided. In Elementor, there is so much scrolling, jumping between tabs, looking for things, opening sub-tabs, then opening typography popups and so on. The styling options are inconsistent. Sometimes there is a responsive control, hover control and sometimes not. You never know what you're gonna get. Why is margin and padding in the Advanced tab? What's advanced about that? Now, when you're introducing more complex styling features, the old UI is really ruining the experience. I know you're working on a new UI, I've seen the prototype screenshot. But that just seems like more modern graphics for the old interface, but not much difference in terms of UX. The user interface is the core of the experience and it deserves big improvements. Have a look at Webflow's UI. I'm using both and Webflow is on a completely different level in terms of styling power and ease of use. webflow

1. Flexbox needs auto margins

In frontend development, when we use flexbox, the capability to use "margin: auto" is fundamental. These things go hand in hand so I think it should be mentioned. I already started a feature request: #17886

In line with this, I can only point out that at least in the "Layout" tab, the settings were much clearer a few dev versions ago, as this picture shows:

Bildschirmfoto 2022-03-04 um 12 42 48

I mean only the arrangement or the division. The progress in terms of content as it is now is good, there are already enough suggestions from other users above.

I'm quite successful. Displaying container options in a tab was much better than it is now. Unfortunately, displaying container settings in two tabs is not interesting. And it is a kind of obstacle in the speed of design. Of course, this is my opinion.

Deadlift79 commented 2 years ago

1)

After updating to 3.6 beta I have an issue with svg logos widht. It appears in both site logo and image widget. Basically svg width is forced set to 48px by elementor and is not possible to change it in the editor apart then using custom CSS. I've tried with several logos.

Screen 1: 3.5 no svg issue Screen 2: 3.6 svg issue Screen 3: 3.6 with custom CSS

Immagine 2022-03-04 123749 Immagine 2022-03-04 123616 Immagine 2022-03-04 123206

2)

Container: cannot find motion effects under "style tab" but only in "advanced". In that way is no more possible to add motion effects to backgrounds, for example a parallax done with vertical scroll.

pauserratgutierrez commented 2 years ago

As said avobe, containers don't allow us use motion effects

Edit: Sorry I miss-looked it. They allow us!

SuatBa commented 2 years ago

love the container-element thusfar. but at current version i can't change triggers, display conditions and advaced rules for Pop-Ups. Always have to roll back the version to change Pop-Up-conditions, but in the previous version there's a bug that won't allow Pop-Ups as Links for e.g. Buttons

fabigrafo commented 2 years ago

After updating to 3.6 beta I have an issue with svg logos widht. It appears in both site logo and image widget. Basically svg width is forced set to 48px by elementor and is not possible to change it in the editor apart then using custom CSS. I've tried with several logos.

Screen 1: 3.5 no svg issue Screen 2: 3.6 svg issue Screen 3: 3.6 with custom CSS>

Container: cannot find motion effects under "style tab" but only in "advanced". In that way is no more possible to add motion effects to backgrounds, for example a parallax done with vertical scroll.

Motion effect was never under style, ever in advanced.

fabigrafo commented 2 years ago

As said avobe, containers don't allow us use motion effects

Under "advanced" like ever:

Bildschirmfoto 2022-03-04 um 15 04 52
79ho3ein commented 2 years ago

If enable the motion effect, we can not change the position of the widgets by dragging the mouse. In the video below, I compare with previous versions ...

https://user-images.githubusercontent.com/77163248/156793140-2ea71823-28e9-4a3b-81e2-22549e3b75cc.mp4

jormeer commented 2 years ago

I didnt have this problem before the beta

Fix: Image size with a link shrunk in Image widget (https://github.com/elementor/elementor/issues/15088, https://github.com/elementor/elementor/issues/12432)

But when installing the beta i do get the bug it should fix? A shrinked svg logo when having a link to it.

Deadlift79 commented 2 years ago

After updating to 3.6 beta I have an issue with svg logos widht. It appears in both site logo and image widget. Basically svg width is forced set to 48px by elementor and is not possible to change it in the editor apart then using custom CSS. I've tried with several logos. Screen 1: 3.5 no svg issue Screen 2: 3.6 svg issue Screen 3: 3.6 with custom CSS> Container: cannot find motion effects under "style tab" but only in "advanced". In that way is no more possible to add motion effects to backgrounds, for example a parallax done with vertical scroll.

Motion effect was never under style, ever in advanced.

Before container we have two motion effects setting panels:

With container that second one is disappeared.

settings

Deadlift79 commented 2 years ago

I didnt have this problem before the beta

Fix: Image size with a link shrunk in Image widget (#15088, #12432)

But when installing the beta i do get the bug it should fix? A shrinked svg logo when having a link to it.

Yes, thanks, exactly that issue.

webdevs-pro commented 2 years ago

Elementor stop working on frontend on my local environment (Laragon, Windows 10, Firefox) starting from version 3.6.0 dev32 Browser message is: The connection was reset. The connection to the server was reset while the page was loading. ERR_CONNECTION_RESET

This issue appears only on pages edited with Elementor

UPDATE: solved https://stackoverflow.com/questions/1138269/apache-error-notice-parent-child-process-exited-with-status-3221225477-res

webdevs-pro commented 2 years ago

Advanced tab width select control disappears if custom option selected (looks like control condition issue) 1646511812

iqbalmauludy commented 2 years ago

Finally! What I'm waiting for.... Rearrange global colors and fonts will be super useful for me.

Thank you so much Elementor😍

shilo-ey commented 2 years ago

Hey all, thank you for your comments.

We reviewed and going to fix most of the issues that were raised here.

We will provide specific comments per issue soon.

Thanks again!

Michaelgimii commented 2 years ago

Great update, thanks elementor🔥

The first and most important bug I encountered : https://prnt.sc/FvTMseemxqa- Nested containers stick together perfectly. Shouldn't they be like this? https://prnt.sc/QUXGNa_95-UZ Even when you add a widget, there is no space around it. I used to follow the dev version and this was not a problem!

79ho3ein commented 2 years ago

There is an important thing about containers and sections (Before 3.6) ... When we add a section or container, its handles are outside the container or section : https://prnt.sc/D_aOfZtyN02Q Of course, sometimes it is outside the section and the container, sometimes inside. But one question. Why should container or section handles be placed outside? It is wrong to place the handle outside the section or container for two reasons.

1- It will be difficult to display the handles of the first container or section. (At least in most cases)

https://user-images.githubusercontent.com/77163248/156678987-c78a813d-fa98-4cae-9bf1-bd2d320046cf.mp4

2- If the upper section or container has a higher z index value, the lower section handle or container will be located below it and will not be available.

So I think these two problems will only be solved in one way. Container handles should only be placed inside : https://prnt.sc/QzJ6kkle7fw0 Under no circumstances should they be displayed outside the container. There is no reason for it to be shown outside. Please share your opinion. Am I wrong? Is there a reason to display the handles outside the container? In any case, this is not a big change, I hope it will be fixed in 3.6 so that we can get rid of it forever.

DavidGMiles commented 2 years ago

Same issue if you have negative margins - I second this call

misslaidlaw commented 2 years ago

Currently unable to add the Container widget to "Favourites"

seanvandermolen commented 2 years ago

Perfect timing

djrwp commented 2 years ago

Hi Elementor Team, Like everyone says the flex container feature is a great addition. But please review #17983 issue I submitted since dev version but still an issue in this beta as when the container content width is set to boxed and you add padding on responsive option the padding is ignored, while in full width mode it works. If this is a problem with how boxed and flex css works then please disable left and right padding as options for the container when boxed is selected to remove any confusion.

confirmed this is an issue. Padding is only honoured on desktop, all other breakpoints padding is ignored

Screenshot 2022-03-07 at 15 36 08 Screenshot 2022-03-07 at 15 35 49

.

shilo-ey commented 2 years ago

Thank you all for this great inputs! we are working hard on fixing all of the issues you raised.

We just release another beta version with more fixes. feel free to update to v3.6.0-beta2 and get the following updates:

Please keep this related to the Current beta Only! any other Issue Report or Feature Request feel free to open a new issue.

Thanks again to everyone.

mirco750 commented 2 years ago

Hello, the width of the containers does not work on breakpoints.

https://user-images.githubusercontent.com/101135944/157097027-a64a9fcd-e95b-4f03-9690-27edf8ef6d70.mp4

Some reason for not all active margins in the containers this is very limiting.

https://user-images.githubusercontent.com/101135944/157097310-4ce2403f-1dab-4ec6-ab7d-9531c7fd0f45.mp4

elasticeye commented 2 years ago

When converting to container (from section/columns), the margin will be copied, but I can't changed left/right margins. See video

PanagiotisRou commented 2 years ago

There should be a way to add a gap only between the items. For example, I want to have a Gap between the 3 columns with the width of 33,3333% without breaking in 2 columns.

gap_image gridgap2

KiQdev commented 2 years ago

Media carousel set to slideshow completely breaks in mobile view, (only)

teoeugene commented 2 years ago

First of all, you did an amazing work with the container! 🚀

I want to suggest something. We have the ability to set the direction that the elements inside a container will follow. This is great, but obligates anyone to add multiple containers to create stacked rows and columns. Here's an example: image

To avoid this multiple container need, I suggest to have a new option on the main conteiner that triggers a break when a number of elements is reached. In my example I would use "Break when elements reach: 2", so when the container automaticly detects 2 elements (Monday, 13:00 - 16:00) a break will happen and the next 2 elements will be displayed in the next line, and so on.

@pauserratgutierrez Flexbox doesn't work that way. To achieve what you want, that sort of nesting is exactly what you'll need to do. Alternatively, you will have to set width for the Day and Time child containersto fill up 100% of the parent flexbox container. (eg. 50%/50%) and the same height for both. That way you'll only have 2 child containers per row (although calling it row in this scenario is technically inaccurate).

The other other alternative is using grid, which isn't available for Elementor yet unfortunately, but you can use custom CSS to make it a container way easier that the old section/column widget especially now that the container simplified DOM structure makes it way easier to override flex and use "display: grid" instead.

black-eye commented 2 years ago

There should be a way to add a gap only between the items. For example, I want to have a Gap between the 3 columns with the width of 33,3333% without breaking in 2 columns.

@PanagiotisRou is definitely right. There should be a better way to change the gaps between (and I mean ONLY between) the "columns". The problem is discussed in several other issues e.g. this one: https://github.com/elementor/elementor/issues/17985

KiQdev commented 2 years ago

There should be a way to add a gap only between the items. For example, I want to have a Gap between the 3 columns with the width of 33,3333% without breaking in 2 columns.

@PanagiotisRou is definitely right. There should be a better way to change the gaps between (and I mean ONLY between) the "columns". The problem is discussed in several other issues e.g. this one: #17985

For me that works if Wrap is unchecked, only if checked it breaks to 2 columns.

black-eye commented 2 years ago

There should be a way to add a gap only between the items. For example, I want to have a Gap between the 3 columns with the width of 33,3333% without breaking in 2 columns.

@PanagiotisRou is definitely right. There should be a better way to change the gaps between (and I mean ONLY between) the "columns". The problem is discussed in several other issues e.g. this one: #17985

For me that works if Wrap is unchecked, only if checked it breaks to 2 columns.

Of course it works this way - if the columns don't wrap, they have to stay in one line. But what if you want them in several rows? That's the problem we are discussing here: you want 3 columns, but because the gap adds extra space, only 2 columns will fit.

black-eye commented 2 years ago

Please consider adding an option to keep the section related widgets available in the widget list (left panel). Mark them as obsolete, move them to an extra group, make it optional, but please keep them there.

I welcome your decision to keep the old sections untouched, without trying to convert them automatically after the update (it would end up as a disaster). It's also good, we can still edit them. But if we can edit them, why not have them in the list as well?

It's clear that many old sites won't be updated to the new system instantly, and it's probable that lots of them will be using both options simultaneously. I can imagine a situation, that I (or my client) decides to use the Containers only for the new pages and the old ones keep (for the time being) in Sections. But you still need to maintain the old pages which includes adding new sections. Sure, you can copy or duplicate them, but again, if you can do all this, it's better to have them in the list too.

Thanks

KiQdev commented 2 years ago

Copy a container and paste it creates an "old section" with the container inside. copy-paste container .

perks98 commented 2 years ago

Just my 2-pence but please refine this more so the flexbox experiment releases as a beta rather than alpha. Might as well stay in the Dev version, since alphas are advised not to be used on customer websites, and further updates if done on a production site could break in future while in alpha form. This is a good feature but you still have 'Inline Font Icons' in alpha too that is still as yet to be complete.

shilo-ey commented 2 years ago

Just my 2-pence but please refine this more so the flexbox experiment releases as a beta rather than alpha. Might as well stay in the Dev version, since alphas are advised not to be used on customer websites, and further updates if done on a production site could break in future while in alpha form. This is a good feature but you still have 'Inline Font Icons' in alpha too that is still as yet to be complete.

Thanks, These experiments are for assuring the stability of all websites. Alpha means that this feature is developed and we are allowing users who want to opt-in and try it out to experiment with it. This is a mean for assuring the safety of all of our users websites

We have just released Elementor v3.6.0-beta3 which includes the following updates:

There are still some bugs that you reported here that are being fixed and should be released soon in another beta version.

Please keep this related to the Current beta Only! any other Issue Report or Feature Request feel free to open a new issue.

Thanks again to everyone.

perks98 commented 2 years ago

Thanks, These experiments are for assuring the stability of all websites. Alpha means that this feature is developed and we are allowing users who want to opt-in and try it out to experiment with it. This is a mean for assuring the safety of all of our users websites

I know where you are coming from as it is better to publicise the feature so more people use it to stress test the feature and to bug fix in the main version rather than the smaller participants using the Dev version.

Anyways again still a great feature and love the work done to get it this far. 👍