Hmm. Ok cool, but Landing Pages as a main feature? I do not know …

We already have a lot of patience with the Custom Brakepoints, and I understand that it takes longer, but why not process one of the other long-awaited open inquiries? (https://github.com/elementor/elementor/issues?q=is%3Aissue+is%3Aopen+sort%3Acomments-desc) PLEASE ELEMENTOR, listen to your community!

Having landing pages as a section is nice, but a main feature? The other things are very promising, however.

Before I rant for much more and in more detail, I'll have a look at the new beta tonight.

Hmm. Ok cool, but Landing Pages as a main feature?

I do not know …

We already have a lot of patience with the Custom Brakepoints, and I understand that it takes longer, but why not process one of the other long-awaited open inquiries? (elementor/elementor/issues?q=is%3Aissue+is%3Aopen+sort%3Acomments-desc) PLEASE ELEMENTOR, listen to your community!

Having landing pages as a section is nice, but a key feature? The other things are very promising, however.

Before I rant for a long time and in more detail, I'll have a look at the new beta tonight.

Hey @fabianenzensperger

Thanks for your feedback.

The beta issue is supposed to tell about the new features in this version.
Actually, the link you attached is something that we are constantly following, and I can assure you that we will handle a lot of this issue in the upcoming releases.

One mistake we had in v3.0 is that we bundled a lot of code and infrastructure changes in one single (complex) release which caused conflicts and a very long debugging process. we wish to prevent this situation in the future, therefore our releases will be more compact and often, and will add features that are risky in a more gradual manner, by adding experiments and testing them before they are publicly available.

I suggest you to take a look at the experiment that handles #8572, which is an issue in the link you attached.

Thanks again and hope this release will meet your expectations.

I saw that v3.1 is scheduled for mid-February, which still leaves time to have a more than stable and performing version. Can you tell us how long before E. Pro will be available in beta?

Another remark: the Marketing pages also match in the Wordpress pages section. Aren't they supposed to be separated?

Hi!

i use this code inside a shortcode to create a swiper slide for a post query before the new Improved Asset Loading experiment and all is fine. Now with this new improvements swiper scripts now is no loading if no have any swiper widget, ok?

 var mySwiper<?php echo get_the_ID(); ?> = new Swiper ('.slide-archivo-<?php echo get_the_ID(); ?>', { 
      spaceBetween: 0,
	preloadImages: false,
        lazyLoading: false,
        observer: true,
    loop: true,
      pagination: {
        el: '.swiper-pagination-<?php echo get_the_ID(); ?>',
        clickable: true,
      },
      navigation: {
        nextEl: '.swiper-button-next-<?php echo get_the_ID(); ?>',
        prevEl: '.swiper-button-prev-<?php echo get_the_ID(); ?>',
      },
	  onSlideChangeEnd: function(swiper) {
            activeSlide = swiper.slides.eq( swiper.activeIndex );
            slideLazy = activeSlide.find( $( '.image-inview' ) );

            // disable Autoplay during Image preload
            if (slideLazy.hasClass('lazyload')) {
                swiper.stopAutoplay();
            }
        }
    });

Now i put this before the script https://developers.elementor.com/experiment-optimized-asset-loading/

const asyncSwiper = elementorFrontend.utils.swiper;
 
new asyncSwiper( swiperElement, swiperConfig ).then( ( newSwiperInstance ) => {
  console.log( 'New Swiper instance is ready: ', newSwiperInstance );
 
  mySwiper<?php echo get_the_ID(); ?> = newSwiperInstance;
} );

but my code doesn't works, swiper scripts isn't load. How is wrong?

this is the error:

jquery.min.js:2 Uncaught TypeError: Cannot read property 'swiper' of undefined
    at HTMLDocument.<anonymous> (portfolio:976)
    at e (jquery.min.js:2)
    at t (jquery.min.js:2)

Thans for this new improvement! if i get works this... will be awesome

There's an issue appearing from Popup.

Undefined index: wp-content/plugins/elementor-pro/modules/popup/tag.php:87
Undefined index: popup wp-content/plugins/elementor-pro/modules/popup/tag.php:100

All nice - yet your code is still way too bloated. 5 DIVs and 1 H1 Tag for a heading? Have a look at Oxygen ( I know you don't wanna hear that, but you will have to address that one day - the earlier the better )

But cudos for the conditional stuff.

I think the Landing Page feature is totally unnecessary. I can't see what's the difference from the current page templates...
The new DOM feature seems really useful.

So please don't implement Landing Page library...

As most of the users has been hungry for performance and custom breakpoint improvement, I truly hope the Elementor team could really stop adding new features until major issue has been fixed such as;

Growing file size of frontend js and css is getting scarier

1. Overbloated CSS files (the more feature you add, the more unused style added which increase file size, and more work to cater to custom breakpoints feature)
2. .elementor-106 .elementor-element.elementor-element-194e2f5.elementor-wc-products ul.products li.product .button is overkill and generated huge amount of unnecessary plus unused CSS. And most of all, those who wanted customize that particular element need to duplicate the same length of CSS to override this will take huge amount of effort to change this since you make this absolute including "div/ul".
3. As @FrostStudios mentioned, 5 divs (DIVception) is overkill. Any potential of mode such as"Highly Optimized Mode (Strictly for new installation only".
4. Limiting the maximum creation of columns to 10 is tough for those who wanted to modify columns via FLEXBOX (Flexbox Wrap) to add more than 10 columns.
5. Landing page workflow is nice, make it 3.2 is still better.
6. Modular CSS/JS loading is great.
7. Customize blog post loop would be amazing too
8. Praying hard for Elementor Team to surprise us instead of just custom breakpoint, they are going to give us CSS Grid as well :D

CSS naming optimization

As part of our effort to simplify and minimize the markup created by Elementor, we have decided to truncate the prefix we use for any Elementor CSS classes, from .elementor- to just .e-.
source: https://developers.elementor.com/updated-convention-creating-new-widgets-for-improved-performance/

By the way, may I know if there's any developer, designer who would like to override some styling which unfortunately fixated absolute selector in frontend.min.css as item 2 above?

I do aware that adding new features would be important, we hope the Elementor team would really focus to solve performance issue and make the website created with Elementor is superbly high-performance, accessibility friendly, customizable.

And yet.. still no sign of a decent form builder.

GravityForms ftw

Yeah, but why would you install another plugin if you COULD do this in Elementor?

I'm seeing multiple 404 errors in the browser Console.
Below is a screenshot of the SourceMap 404 errors.

Typical software developers! Focusing on a new feature rather than prioritising all the issues with existing features.
Why, why, why?

I think this is great, love the experimental dock to safely roll out and test new features. Great stuff.

I agree though with others more customizable post loops and custom breaking points would be game-changers for site builders and are really what the community has been screaming for. Looking forward to having those options built-in!

Or even make an Elemetnor add on for custom post loops and creating custom post types like pods or jet engine. Would be $$$ in your pocket.

Keep up the great work!

I saw an Elementor Pro Beta Release email & got excited, I thought it was conditional logic for forms.

@jonathansoltero an email, can you show it?

@jonathansoltero an email, can you show it?

E-Mail from Elementor 30.12.2020 "Introducing Elementor v3.1 Beta"

"Dear Elementor beta testers,In just a few weeks, we will be launching Elementor v3.1, and today you get to try out its Beta version.

Here’s what you’ll find inside Elementor 3.1 Beta, based on your feedback:

• Landing Pages - New streamlined creation workflow and templates
• Experiments - Experience and control new features before they are officially released
• Performance - Conditional load of required assets
• Accessibility Improvements - Try the new accessible tabs widget

We can’t wait for you to test out these new features and let us know what you think.
 
Learn More Button
 
Important Note!
Found a bug? Please leave us a comment in the beta thread on GitHub.

Please keep the beta thread related to the current beta only. For other issues or feature requests - please open a new issue on Github.
 
Thank you for your support and help 🙏
The Elementor Team"

As most of the users has been hungry for performance and custom breakpoint improvement, I truly hope the Elementor team could really stop adding new features until major issue has been fixed such as;

Growing file size of frontend js and css is getting scarier

1. Overbloated CSS files (the more feature you add, the more unused style added which increase file size, and more work to cater to custom breakpoints feature)
2. .elementor-106 .elementor-element.elementor-element-194e2f5.elementor-wc-products ul.products li.product .button is overkill and generated huge amount of unnecessary plus unused CSS. And most of all, those who wanted customize that particular element need to duplicate the same length of CSS to override this will take huge amount of effort to change this since you make this absolute including "div/ul".
3. As @FrostStudios mentioned, 5 divs (DIVception) is overkill. Any potential of mode such as"Highly Optimized Mode (Strictly for new installation only".
4. Limiting the maximum creation of columns to 10 is tough for those who wanted to modify columns via FLEXBOX (Flexbox Wrap) to add more than 10 columns.
5. Landing page workflow is nice, make it 3.2 is still better.
6. Modular CSS/JS loading is great.
7. Customize blog post loop would be amazing too
8. Praying hard for Elementor Team to surprise us instead of just custom breakpoint, they are going to give us CSS Grid as well :D

CSS naming optimization

As part of our effort to simplify and minimize the markup created by Elementor, we have decided to truncate the prefix we use for any Elementor CSS classes, from .elementor- to just .e-.
source: https://developers.elementor.com/updated-convention-creating-new-widgets-for-improved-performance/

By the way, may I know if there's any developer, designer who would like to override some styling which unfortunately fixated absolute selector in frontend.min.css as item 2 above?

I do aware that adding new features would be important, we hope the Elementor team would really focus to solve performance issue and make the website created with Elementor is superbly high-performance, accessibility friendly, customizable.

This is the absolute truth. When I read “Developer Edition,” I got incredibly excited. However, landing pages should not be a developer’s feature. More granular control of loading assets, DOM improvements, and breakpoints are needed.

Oxygen works like this:

1. you add a section or div
2. you add a div or column widget (2 or more divs) -OR- a widget (e.g., heading, text, etc.)
3. you can then nest other divs or widgets

*each widget and div then has flexbox, typology, spacing/size, and so much more.

These should be the DOM elements presented. Complete granular control.

Also, a huge pet-peeve of mine is the ability to customize your CSS variables. It is such a pain for me to use your given --e- variables because most of the time, it is some random alphanumeric string.

If a user wants to use the swiper, tab, or accordion widgets, it loads in a div with a repeater widget that allows for easy customization/control. This is ideal.

I’m glad that Elementor is shedding light on the needed assets and DOM improvements, but please don’t start introducing a “Developer Edition” with Landing Page options. This is only taking what you currently have, changing it a little, and giving it a new name.

Hi all,

First of all, thank you for your feedback.

@rodolphebertozzo

I saw that v3.1 is scheduled for mid-February, which still leaves time to have a more than stable and performing version. Can you tell us how long before E. Pro will be available in beta?

Another remark: the Marketing pages also match in the Wordpress pages section. Aren't they supposed to be separated?

There was a mistake with the release date and it was fixed, thanks.

The Pro version will be introduced soon as a separate beta version.

The Landing Pages currently are Pages, we are checking if keeping them that way is how we want to release this feature or changing it a bit. each option has its pros and cons.

There's an issue appearing from Popup.

@sermalefico : First, you need to make sure that elementorFrontend exists.
This object is being called from the frontend.js file, which is loaded from the footer.
Since you are trying to use a shortcode, probably you inserted it in the middle of the page (where the frontend.js file was not loaded yet). So, you get the error of swiper is undefined.
In addition, in case you are not using a widget handler, you need to listen to the following hook, which initializes elementorFrontend.utils.swiper

elementorFrontend.on( 'components:init', () => {
   // Do something that is based on the elementorFrontend object.
} );

@sermalefico updated.

@riadcitaku : Can you please share more light and steps to reproduce the errors?

@Jonathlee :
As for the file sizes, the file version should be 3.1.0-beta1 and not v3.0.15 we see from your screenshot. Only then, you will see a decrease in the file sizes.
Please make sure you are using the right version and you cleared your cache (server and browser side).

• CSS files - we are currently investigating how to approach the change without harming existing websites or various addons installed
• DOM - we are activating the Optimized DOM output by default to only new sites to prevent potential break or conflicts in existing sites.
  We will proceed these constant improvements in the next releases.

@mcrowell : Thanks! we're investigating this issue.

@portseif

The Developer Edition is a different release channel that allow us to provide frequent releases with our development progress to extend the period that 3rd party developers have to adjust to changes.
The features that are introduced in the Developer Edition versions will not necessarily will be developer oriented.

As for bloat issues and performance upgrades - as mentioned before, we are working on these aspects and will continue to provide you with these kind of improvements from release to release.

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.

@shilo-ey I don't understand how doing it works ... :(

Select2 ajax search is not working on display selected values.
How to reproduce it:

• add widget Posts
• from Query Section search and select a term filter
• change section and return on Query Section

NO errors on console and no errors on Select2 ajax call (as display on screen).

Hi @mcrowell
Thanks for your report.

We had a bug on our end due to the Webpack upgrade, and we are fixing it now.

Select2 ajax search is not working on display selected values.
How to reproduce it:

• add widget Posts
• from Query Section search and select a term filter
• change section and return on Query Section

NO errors on console and no errors on Select2 ajax call (as display on screen).

@nerds-farm Thanks!

It seem to work fine on our end.
Can you please make sure you're using only Elementor and Elementor Pro to isolate potential conflicts?

Thanks

@shilo-ey, why did you move the HTML semantics optimization feature to the Experiences tab, since many sites have it enabled and it can be disabled anyway? Do you plan to make further improvements to avoid case on older sites using custom CSS to avoid case?

@shilo-ey I don't understand how doing it works ... :(

@sermalefico we updated the snippet:

elementorFrontend.on( 'components:init', () => {
   // Do something that is based on the elementorFrontend object.
} );

Check and let me know if it works for you

Thanks

@shilo-ey, why did you move the HTML semantics optimization feature to the Experiences tab, since many sites have it enabled and it can be disabled anyway? Do you plan to make further improvements to avoid case on older sites using custom CSS to avoid case?

@rodolphebertozzo we migrated this option to the Experiments tabs, so it will act the same, but will allow Elementor to control whether to activate it to existing or new sites by default.

Thanks

@fabianenzensperger please try changing the permalinks to Plain and let me know if it solves the issue for you.

Thanks

@shilo-ey That worked, thanks!

@fabianenzensperger And if you revert the permalinks back the issue reproduces?

@fabianenzensperger And if you revert the permalinks back the issue reproduces?

Thanks for asking, now it doesn't matter which permalink structure I use. It works with everyone now. I don't know why it didn't work before.

I thought this was releasing today, when is it releasing @shilo-ey ?

I thought this was releasing today, when is it releasing @shilo-ey ?

Hmm. Why did you think that? Who ever said that?

It says release date January 19th at the bottom of the beta release post...

Oh ok yeah. But only: Probably! 👀

Hi all!

We just released a new beta version, please update your version to v3.1.0 Beta 4.

Due to several bugs found with your help, we decided to postpone the release date to next week.
Please check the new version and make sure everything works flawlessly.

This beta release includes:

• Tweak: Updated eicons library to v5.10.0
• Fix: UI glitch in the Library modal footer
• Fix: 404 page displayed when trying to access Landing Pages
• Fix: Carousel functionality didn't work if Optimized DOM Mode was disabled
• Fix: Column height is not correct when Optimized DOM experiment is inactive in IE11
• Fix: Wrong translation function caused errors in the Revisions panel
• Fix: Widgets empty state is not visible in WordPress 5.6

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.

@shilo-ey Is the social icons bug fixed? Don't see it in the changelog

@shilo-ey Is the social icons bug fixed? Don't see it in the changelog

Please keep this thread related to the Beta only

@shilo-ey It's a bug that's not fixed in the beta that has now been almost 3 months unfixed... Not sure how that isn't related.

@shilo-ey It's a bug that's not fixed in the beta that has now been almost 3 months unfixed... Not sure how that isn't related.

Yes in elementor blogs pages have the same bug. https://elementor.com/blog/redirect-url-wordpress/

check share section on the bottom post

@shilo-ey It's a bug that's not fixed in the beta that has now been almost 3 months unfixed... Not sure how that isn't related.

Yes in elementor blogs pages have the same bug. elementor.com/blog/redirect-url-wordpress

check share section on the bottom post

@sermalefico

Do you have a comparison before/after?

Or even a JSON template export for us to examine?

Is it browser related or happens on all devices?

Add a advise to

https://wordpress.org/support/topic/incompatibility-with-future-elementor-update-custom-codes/

@shilo-ey It's a bug that's not fixed in the beta that has now been almost 3 months unfixed... Not sure how that isn't related.

Yes in elementor blogs pages have the same bug. elementor.com/blog/redirect-url-wordpress
check share section on the bottom post

@sermalefico

Do you have a comparison before/after?

Or even a JSON template export for us to examine?

Is it browser related or happens on all devices?

This occurs when using a CSS minifier, such as autoptimize or Fastvelocity minify. For some reason CSS variables have some space that in this specific widget is broken on the frontend. Yes, all devices.

@shilo-ey Coming tomorrow? :)

Elementor 3.1 is now public it seems

@shilo-ey It's a bug that's not fixed in the beta that has now been almost 3 months unfixed... Not sure how that isn't related.

Yes in elementor blogs pages have the same bug. elementor.com/blog/redirect-url-wordpress
check share section on the bottom post

@sermalefico
Do you have a comparison before/after?
Or even a JSON template export for us to examine?
Is it browser related or happens on all devices?

This occurs when using a CSS minifier, such as autoptimize or Fastvelocity minify. For some reason CSS variables have some space that in this specific widget is broken on the frontend. Yes, all devices.

@sermalefico
Thanks! will check again

Add a advise to

https://wordpress.org/support/topic/incompatibility-with-future-elementor-update-custom-codes/

Cool, thanks for letting us know, we will check if the conflict is due to an implementation issue on our side.

@fabianenzensperger Yes, today the version is rolling out.

Thanks for your feedback.

Will update here once it's officially released.

Thank you all for your precious comments and reports!

The version is now publicly available via WordPress repository or via your plugins dashboard.

If you encounter any new issue regarding this version please create a new issue report.

Release blog post will be updated soon.

Thanks again!