• Resolved chaug

    (@chaug)


    I just installed KingComposer and activated it for test purposes. I was not happy to see that KingComposer has – without asking me – deactivated both Elementor and Beaver Builder. Fortunately it was honest enough to inform me about this (giving possible conflicts as a reason).

    I would like to suggest that no page builder plugin should automatically deactivate another for the simple reason that for most page builders, this means that it immediately breaks the webpages concerned. Since this is rarely what the user wants, I think it would be more apropriate to warn the user about incompatibilities and to suggest which plugins should be deactivated.

    Having said this, I would like to ask what exactly the problems are that the deactivation is supposed to avoid? Where does KingComposer conflict with Elementor or Beaver Builder?

    Evidently, you should not try to use KingComposer for editing pages that were made with another page builder. But that goes without saying. So where else might there be conflicts?

Viewing 1 replies (of 1 total)
  • Hi chaug,

    Because some plugins have bad code, so it effect to the element of KC.
    We will remove that code.

    Hope that convenient for your plan.

    Best regards,

    Anthony

Viewing 1 replies (of 1 total)
  • The topic ‘Why deactivate other pagebuilders?’ is closed to new replies.