How Elementor works with WP?

Hi,

I totally agree, this plugin is a keeper ?? !!

Like any other pagebuilder, once you disable or delete the plugin the pages will look distorted. You can easely test this, by simply disabling Elementor for a short time and then take a look at your ( with Elementor or another pagebuilder ) created pages.

All your text will be there, but with just the left over code from Elementor.

Annie

• This reply was modified 7 years, 3 months ago by LogoLogics.

With beaver it works also without plugin.
I hope elementor reach this goal

Hi Mario,

Really, that would indeed be amazing, so far with other pagebuilders I get distorted pages.

So maybe I started with a question and we ended up with a request

I haven’t experienced visible “code” when disabling Elementor and viewing the default content. It appears that it leaves text/images and embeds for the most part, essentially un-styled content.

With some clever css, one could target the unique “wp-content” version with some styling that would not interfere with an “active” Elementor loaded page, but would act as the “clean” fall-back version if should ever the plugin become disabled. The trade off is extra time to do this and a little extra bloat in your css.

The other glaring problem here is that you don’t get any choice in picking and choosing what “wp content” is saved in the standard post editor vs what gets cut out when the plugin is disabled. Each widget is handled differently and some of which may not render anything at all in absence of the plugin. I have not investigated this personally but at any time one can see what exactly would be shown by simply choosing the use the default wp editor when editing a post/page via back end.

I agree, it would be cool if a page builder was developed to be more of a portable tool that one would use to create site content but leave no dependency except that of which is needed for the specific content created. How would it do this though?

It would have to be smart in it’s approach, maybe bundling the created content along with proper css/js and php libraries nested and nicely organized within one’s child theme making it also completely portable outside of a db grab.

That would be the ultimate developers tool while still being friendly to the end consumer providing the easy-to-learn/use visual front end designer.

@pingram3541 Great idea!! This is the concept that is missing on WordPress and the page builders.

@pingram3541 @logologics i’ve seen in action the beaver page builder and with it is possible to create a customized theme ( signed by the person that create it – shite labeled ) and it can be installed on client site without he never know that has been used a page builder and without that in admin dashboard appear any plug in installed how happen with elementor.
i use elementor and i like it so i’m not promoting beaver but this a big added value that i’d like will have also elementor.

I have a few sites where I used Elementor to build out the sites but no longer require Elementor to be installed. Initially my approach was to avoid having duplicate grids and libraries as most themes already provide this and then you’re actually layering a page builder’s library stack right on top of another (in most cases). Here is the code base I use to get around this with my custom themes:

https://github.com/pojome/elementor/issues/1137

For these particular sites it was an easy but timely process as I simply copied out each designed page (that was built in Elementor) into it’s own php page template in my child theme and had to save out and re-enqueue the unique css stylesheet Elementor provides by post id. (essentially making these sites mostly static)

As @mario-barretta suggests, Beaver apparently makes this an easier process but honestly, outside of using the code above to allow my themes to use the same css grid as Elementor, I now simply use a strict caching system so I can leave Elementor installed and active but if it ever gets de-actviated or even uninstalled my sites all still render everything perfectly. The caveat is a little extra cache-busting when making changes but solves the ugly front end issue should the plugin ever become disabled and I no longer have the tedious process of copying out to static files.

@pingram3541 in understand what do you mean but all the work that’needed to can use an elementor’s design is an oppiste situation to that chosen from users that use a page builder.
If they were able to easily do all that work is probable that develop autonomous a site.
I prefer elementor at beaver but the problems about to can show a site withou revealing to client that we have used a page builder and without having problema about the disappearing of plug in exists and i hope that Elementor become every day better.
Other problem, non pertinent with question of @giastwp is that on every new update there is ever something that do not work and that block our work or need actions so you can inderstand that the time is important and if we gain in building but lost in fixing something is not ok.