How to Enable/Disable Builders for Widgets in WDesignKit?
On this page
What It Does
Widget Builders lets you turn each page-builder integration, Elementor, Gutenberg (Nexter), Gutenberg Core, and Bricks, on or off independently, so WDesignKit only shows and loads the widgets for the builder or builders you actually use.
Why It Matters
Most sites use one page builder, not four. Leaving every builder’s widgets visible clutters the Widget Listing, Browse, and Workspace screens with options you will never use, and loads their related files on the server for no reason.
What You Get
A single Widget Builders popup with one toggle per builder, so you can match WDesignKit’s widget list to the builder or builders installed on your site.
Benefits
- A cleaner Widget Listing, Browse, Shared With Me, and Workspace screen once unused builders are turned off.
- Fewer files loaded on the server, since a disabled builder’s related widget files stop loading.
Capabilities
- Four builder toggles, confirmed live on this session’s audit: Elementor Widget Builder, Nexter Gutenberg Widget Builder, Gutenberg Core Widget Builder (native WordPress blocks), and Bricks Widget Builder.
- Each toggle is independent, so you can, for example, keep Elementor and Bricks on while turning Gutenberg and Gutenberg Core off.
- Applies across the Widget Listing page, Widget Browse page, Shared With Me page, and Workspace, hiding the disabled builder’s widgets everywhere at once.
How It Works
Each toggle in the Widget Builders popup writes to WDesignKit’s stored builder settings. On the next page load, WDesignKit checks those settings before it registers a builder’s widget files or shows that builder’s widgets in the panel, so a disabled builder’s code is skipped rather than just hidden with CSS.
How to Use It
In WDesignKit, you can create and download widgets for both Elementor and Gutenberg page builders. However, if you are focusing on one specific page builder, you can easily disable the option for the other builder. This ensures that your workspace and browsing experience are optimized for finding and utilizing widgets tailored to your preferred page builder.
By disabling the page builder option, you simplify the widget builder interface and remove any unnecessary distractions related to the disabled builder.
This applies to various sections of the WDesignKit plugin, including the Widget Listing page, Widget Browse page, Shared With Me page, and Workspace. By hiding the page builder-related options, you can easily navigate and focus on the relevant widgets for your chosen page builder.
Requirement – This feature is a part of The WDesignKit, make sure it’s installed & activated to enjoy all its powers.
1. To do this, from the WDesignKit plugin page, go to Settings, then click on the Customize button in the Widget Builder section.
2. It will open the Widget Builders pop-up, where you can easily enable or disable Elementor Widget Builder, Nexter Widget Builder, and Bricks Widget Builder options for the WDesignKit widgets.
The disabled page builder-related widget or block options will be hidden from the WDesignKit plugin page.
This way, you can reduce the load on the server by loading fewer files.
Note: since this doc’s 2023 walkthrough video was recorded, WDesignKit added a fourth toggle, Gutenberg Core Widget Builder, alongside Elementor, Nexter Gutenberg, and Bricks. This was confirmed live via the plugin’s current settings this session; the video above still shows only the original three.
Use Cases
- An Elementor-only site turning off Gutenberg, Gutenberg Core, and Bricks widgets to declutter the panel.
- A Bricks site disabling the other three builders since none of their widgets apply.
- A performance-sensitive site turning off builders it does not use to reduce the number of files WDesignKit loads.
Limitations
- Turning off a builder hides its widgets; it does not uninstall or affect the page builder plugin itself.
- This doc’s existing walkthrough video predates the Gutenberg Core Widget Builder toggle and was not re-recorded this session; a new screen recording showing all four toggles is still needed and is flagged in the docs tracker.
- The Widget Builder feature as a whole must also be enabled in Settings > Features Manager; turning that master switch off hides all builder toggles regardless of their individual state.
Troubleshooting
- A builder’s widgets still show after disabling it. Reload the page builder editor; the toggle takes effect on the next page load rather than instantly inside an already-open editor.
- Widget Builders popup will not open. Confirm the Widget Builder master switch is on in Settings > Features Manager first; the per-builder popup only opens when that master feature is enabled.
- WDesignKit is breaking the page builder editor after enabling a builder. This mirrors a real support pattern seen on other WDesignKit builder-conflict tickets: try disabling builders you do not need one at a time and reloading the editor to isolate which toggle is involved, then report the specific combination to WDesignKit support.