2.1 Creating pages with WP Bakery Page Builder

IMPORTANT NOTE AFTER WORDPRESS GUTENBERG EDITOR RELEASE:

In order to keep WP Bakery Page Composer the default page builder of your website, we strongly recommend disabling Gutenberg.

  • Open your WordPress Admin Dashboard
  • Navigate to Visual Composer – Settings;
  • Locate the Gutenberg settings and select disable (Off);

  • Save changes.

When creating a new page, click on Pages > All pages, and then Add new (on the arrow icon) > Classic editor otherwise Gutenberg editor will replace WPBakery Page builder.

When editing new click Classic editor link near page name in list, otherwise Gutenberg editor will replace WPBakery Page builder.

Go to Page->Add new

Screen Shot 2017-01-18 at 22.38.14

Choose Page Visual Composer as page template in the right column

Screen Shot 2017-01-18 at 22.39.33

Enter a title

Screen Shot 2017-01-18 at 22.40.19

Save or publish

Screen Shot 2017-01-18 at 22.40.57

Click Backend Editor (frontend editor is not super stable at the moment, we discourage using it)

Screen Shot 2017-01-18 at 22.41.37

Start adding elements

Screen Shot 2017-01-18 at 22.42.30

Custom functions for layout:

Screen Shot 2017-01-18 at 22.58.32

In the Row settings, clicking the Qantumthemes Design options, you can set a row as negative (texts will use the background colors, useful for sections with background photos) and you can add a container, as this template is 100% width.

In Theme Shortcodes you have a huge number of custom elements added by this theme. Their equivalent shortcode and parameters are discussed in the Theme Shortcodes section of the manual.

Screen Shot 2017-01-18 at 23.04.35

Official manual for Visual Composer:

https://wpbakery.atlassian.net/wiki/display/VC/Visual+Composer+Pagebuilder+for+WordPress

Please note we DO NOT provide Visual Composer support with the Bundle License.

Important:

Some elements of the Visual Composer are disabled, as they are incompatible with the theme. We offer several elements to display sliders, carousels, captions and more that are compatible with the theme and fits with the design of the website.

Why? Because Visual Composer is NOT Ajax-Friendly, so those disabled elements can’t work with QT Ajax Pageload plugin.
If you don’t want to use ajax and prefere all the Visual Composer functions instead, you have to delete all the “vc_remove_element” actions from the theme’s functions.php.

Doing this invalidates the theme support service, as it is a code customization which modifies the way this product was meant to work.

This will enable all the Visual Composer functions, but will be incompatible with the QT Ajax Pageload plugin, which is the plugin needed to keep the music going across the pages.