Driveline for WPBakery

Copy the file you want from this plugin’s vc_templates folder into a vc_templates folder in your theme, keeping the same name, and edit it there. That is WPBakery’s own override convention and it applies one file at a time; anything you have not copied keeps using the version here. Result cards, the filter panel and the booking steps are Driveline Core’s own templates rather than this plugin’s, so those are overridden the way Driveline Core documents, in a driveline folder in your theme. Overriding one changes it everywhere it appears, which is the point.

The elements keep rendering. They are ordinary shortcodes registered by this plugin rather than by the builder, so a page does not fall back to showing its own square brackets. What goes away is the editor: nothing is offered in the element list until WPBakery is back.

No. WPBakery has a vc_set_as_theme() mode that hides its licence and activation screens, meant for products that ship the builder inside them. You bought WPBakery yourself, so that screen is yours and this plugin leaves it alone. A product that really does bundle the builder can turn the mode on by returning true from the driveline_wpbakery_as_theme filter. WPBakery’s updates keep running either way.

Only after you accept the tile host on the Driveline Core map settings screen. Until then the element draws a notice naming the host and loads no mapping library.

In the visitor’s browser. Nothing is written to the database and no account is needed. The list travels to the comparison table as a query argument, so a comparison can be shared as a link.