My issues with 2.1.0 (Anywhere Elementor conflict)

Hi,

I would never use two different site builders in one site?
If you ask me, that’s an accident waiting to happen!:-)

Understood, but it’s only on the front page as client started with a VC-developed theme but then liked Elementor and wanted to stick with original design – and AE did work perfectly with VC until the update.

I see, but apart from higher risk on conflicts, there is also speed.
One pagebuilder already puts some weight into pageload, let alone two.

The frontpage should be easy to reconstruct with Elementor, so you can lose the risk of conflicts and pagespeed factors.

It is ofcourse completely up to you, but as I said, it is an accident waiting to happen.
The more plugins you mix, the higher your changes of getting serious issues one day.

Annie

• This reply was modified 6 years, 4 months ago by LogoLogics.

Actualiza a la ultima version de elementor extras a mi me funciono actualizando ese plugins, ya que cuando actualice elementor a la 2.1 me dio error 500, actualice elementor extras y se soluciono

Update to the latest version of elementor extras, I worked updating those plugins, because when I updated elementor to 2.1 I got 500 error, update elementor extras and it was solved