WP Manifestindependent plugin directory
manifest / builders / bb-color-presets-first

BB Color Presets First WP Registry grade A. No security issues foundWP RegistryNo security issues foundOpen the reportA

Simple single use plugin which uses js to override Beaver Builder's colour picker behaviour making your colour presets visible first by default instead of just the picker, speeding up building out a site.

★ 3stars
47release downloads
v1.1.4latest · 2mo ago

Install

Download bb-color-presets-first-v1.1.4.zip From the v1.1.4 release on GitHub, Aug 21, 2026

Upload it under Plugins → Add New Plugin → Upload Plugin, then activate.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/weavedigitalstudio/bb-color-presets-first/releases/download/v1.1.4/bb-color-presets-first-v1.1.4.zip
Updates itself. It ships its own updater, so new versions appear under Dashboard → Updates.

⚠️ Heads up: Beaver Builder 2.11 adds this natively. From BB 2.11, the core builder includes a setting at Page Builder Settings → Advanced → Builder UI → "Color Picker: Default to Presets Tab" that does the tab-defaulting this plugin provides, built right into the React color picker. Once you're on 2.11 (stable), you can enable that toggle and stop relying on this plugin for the "presets first" behaviour. This plugin still does one extra thing core does not: it hides the "add custom color" controls to lock sites to your Global Colors. We'll keep that part maintained. See the planned direction below.

Why we released this: We got tired of constantly clicking the BB color presets tab when building sites at Weave Digital Studio and HumanKind Funeral Websites. We wanted to set our client's brand indentity colours once at the beginning (using Generate Press Global Colours or BB Global colours) and access these quickly in Beaver Builder. Plus, it helps prevent clients from accidentally adding non-brand colors to their sites. This tiny plugin saves us countless clicks every day!

It's a simple plugin which overrides Beaver Builder's colour picker behaviour, making your colour presets visible first by default instead of just the picker, streamlining your development workflow.

Compatibility

  • Beaver Builder 2.9+: Compatible with the new React-based color picker
  • Beaver Builder < 2.9: Uses the classic color picker override

The plugin automatically detects which version of Beaver Builder you're using and applies the appropriate method.


Installation from GitHub

When installing this plugin from GitHub:

  1. Go to the Releases page
  2. Download the latest release ZIP file
  3. Extract the ZIP file on your computer
  4. Rename the extracted folder to remove the version number
    (e.g., from bb-color-presets-first-1.1.0 to bb-color-presets-first)
  5. Create a new ZIP file from the renamed folder
  6. In your WordPress admin panel, go to Plugins → Add New → Upload Plugin
  7. Upload your new ZIP file and activate the plugin

Note: The folder renaming step is necessary for WordPress to properly handle plugin updates and functionality.


How It Works

Beaver Builder 2.9+

With the new React-based color picker, the plugin automatically clicks the presets tab whenever a color picker dialog opens.

Beaver Builder < 2.9

When you click any colour picker in Beaver Builder, the plugin automatically shows the presets panel instead of requiring you to click the show presets button first.

Color Restriction

The plugin also hides UI elements that allow adding custom colors. This helps maintain brand consistency by requiring users to use only the predefined color palettes from your Global Colors.

There are no settings. It just works.

Allowing Custom Colors

If you want to allow users to add custom colors, you can either:

  1. Comment out the bb_color_presets_restrict_color_palette function in the plugin file
  2. Remove the action hooks at the bottom of that function

Requirements

  • WordPress
  • Beaver Builder (any version)

Planned Direction (BB 2.11+)

Beaver Builder 2.11 ships a native "Color Picker: Default to Presets Tab" setting. Our plan:

  • Retire the tab-defaulting JS. The MutationObserver / click-the-tab approach is superseded by core. It can be replaced with a one-line filter that simply forces the core option on (pre_option__fl_builder_default_presets_tab).
  • Keep the palette restriction. Hiding the "add custom color" controls to enforce Global Colors is not part of core, so this stays.
  • Re-verify the restriction CSS against 2.11's rebuilt React picker before trusting the selectors.

If you're on BB 2.11+, enable the core toggle. You only still need this plugin if you want the custom-color lockdown.

Change Log

1.1.3

  • Fixed updater running on all plugin updates instead of only this one (could corrupt other plugins)
  • Added missing metadata to update response (plugin key, requirements, URL)

1.1.2

  • Fixed incorrect url. If you had v1.1.1 you'll need to re-install for the auto updates to work.

1.1.1

  • Improved BB 2.9+ color picker integration with inline script
  • Removed unused JS files
  • Optimized code structure

1.1.0

  • Added compatibility with Beaver Builder 2.9+ and its React-based color picker
  • Improved version detection to load the appropriate script
  • Updated documentation

1.0.1

  • Initial release

Support

Found a bug? Open an issue

Releases

7 releases. Each count is every asset in that release; expand a row for the breakdown.

Tag
Published
Assets
Downloads
v1.1.4 latest
Aug 21, 2026 2mo ago
bb-color-presets-first-v1.1.4.zip
15
Mar 1, 2026 7mo ago
bb-color-presets-first-v1.1.3.zip
22
Aug 20, 2025 1 year ago
bb-color-presets-first-v1.1.2.zip
5
Apr 3, 2025 1 year ago
bb-color-presets-first-v1.1.1.zip
4
Mar 22, 2025 1 year ago
bb-color-presets-first-v1.1.0.zip
1
Jan 16, 2025 1 year ago
tag only
—
Dec 18, 2024 1 year ago
tag only
—
A grade

Security

BB Color Presets First 1.1.4 · audited by WP Registry

No security issues found.

Audited release
1.1.4
Findings
none
Worst severity
—
Content hash
2a761e3aba7e381f98a7aed3…

WP Registry hashes the installable build and reports on that exact bytes-for-bytes copy. Embargoed findings are withheld until they are disclosed, so a clean verdict means nothing public is outstanding. WP Manifest does not audit code itself.