Disable UX Builder Altogether - Flatsome Theme & UX Builder Plugin | Flatsome Features

Disable UX Builder Altogether - Flatsome Theme & UX Builder Plugin

planned

James Carmody

I really like your theme, it is definitely the best for any WooCommerce store. 
However it falls short in 1 major area. As per the wordpress theme guide a page builder shouldn't be integrated into the theme. It should be a seperate plugin that works along side of the theme. 
Look at all the major themes and page builders. Beaver Builder is the most popular and they have a beaver theme and and beaver builder plugin. This way I am free to use their builder on any theme and vice versa I am free to use their theme with any builder. Other page builders follow the same pattern such as Divi etc. 
The fact that flatsome UX builder is deeply integrated into the theme is very worrying. There is no option to enable or disable the UX builder and from testing with other page builders such as Divi and Beaver Builder there are compatibility issues with UX Builder. 
Now long term it would be even more ideal if UX Builder was a separate plugin. If you think that UX builder is good product then you would want it installed on other themes other than flatsome. However the main reason for separating them would be to allow customers to install their own preferred page builder which they are comfortable with. 
What happens if someone decides to switch themes in the future? They would have to recreate all their pages with another builder instead of continuing to use UX builder with their new theme.

Fernando

yes please, construct page builder plugin

Marina Brühl-Martens

if you don't want to have the ux builder you just have to set the shop page as the start page under read
and if you only want to add the product slider to your shop page, you have to edit the code from the blocks on the start page under insert page
you can delete all pages and blocks then it will not be loaded
and just insert the product and category slider, for example

നീലത്താമര creations

I don't recommend the splitting, Because more integrated = more speed and lite. But From the developer view flatsome developer can push new feature to users simply by pushing update in uxbuilder plugin . But my biggest concern is Speed, Load, Security. Please don't compromise these 3 things.

Nguyen Lap

i don't like it. If you split it up like other topics, I think that's a mistake. You may not be able to compete with them. Your advantage is simple speed. If it is split, the number of uxbuilder users will decrease in that it is not really rich compared to other competitors.

Cris John

Wew its been 2 years already no progress :(

Martin Skallerup

Sooooo.... 2 years now.

Michael S

Please cancel the UX Builder Plugin. It will be a horrible idea. The UX builder should be used on UX themes products only.

Lucian Armasu

I also believe the way the UX Builder is currently set-up it introduces too much HTML. It's a hunch, but I see some SEO audits telling me I have too low content to HTML ratios.

Bill Broadbent

This would help us a lot. Is there an ETA?

Francesca Medaglia

Hi, any news about this feature implementation, yuou have an ETA ?

Thanks in advance for the support.

silvano sottocasa

Francesca Medaglia: scusami vedo che sei italiana ... io sono un neofito... sai come posso implementare il carrello con altri costi? io dovrei inserire il costo del laser su taglieri che ovviamente ha un costo e sommarlo al totale del carrello. Grazie se puoi rispondermi

→