Help

A quick guide to hooks, how this site works, and how to use them in your own code.

What is this site?

BB Hooks is a searchable reference for every action and filter in Beaver Builder, BB Theme, and Beaver Themer. The data is generated directly from the plugin source code, so it's always accurate and up to date.

Actions and filters

WordPress uses a hook system to let developers customise or extend plugin behaviour without modifying core files. There are two types of hook:

Actions

An action fires at a specific point during execution. You attach a callback with add_action() and WordPress calls it when that point is reached. Actions are for doing something — running code, outputting markup, clearing a cache, etc. They don't return a value.

// Run code after a Beaver Builder layout is saved
add_action( 'fl_builder_after_save_layout', function( $post_id ) {
    my_plugin_clear_cache( $post_id );
} );

Filters

A filter passes a value to your callback and expects a (possibly modified) value back. You attach a callback with add_filter(). Filters are for changing something — modifying a setting, adding items to an array, altering output, etc.

// Limit the builder revision history to 5 entries
add_filter( 'fl_builder_revisions_number', function( $number ) {
    return 5;
} );

WordPress developer docs: Actions · Filters · Hooks overview

Defined hooks vs. listened hooks

Each product page has two tabs:

Defined hooks: Hooks that Beaver Builder fires — every do_action() and apply_filters() call inside the plugin. These are the hooks you use in your own code to customise BB behaviour.
Listened hooks: Hooks from WordPress core (or other plugins) that Beaver Builder listens to — places where BB itself calls add_action() or add_filter(). This is useful for understanding how BB integrates with the rest of WordPress, but these are not hooks you would normally use to extend BB yourself.

Listeners

When you expand a defined hook you may see a Listeners section. These are places inside Beaver Builder's own code that are already hooked into that same hook. Knowing what BB does by default at a hook is useful context when you're adding your own callback — for example, to run before or after the built-in behaviour using the $priority argument.

// Run *before* BB's own callback (default priority is 10)
add_action( 'init', 'my_early_setup', 5 );

// Run *after* BB's own callback
add_action( 'init', 'my_late_setup', 20 );

Where to put your code

Add your hook callbacks to a child theme's functions.php or to a small site-specific plugin. Never edit Beaver Builder's files directly — your changes would be lost on the next update.

// In your child theme's functions.php, or a custom plugin:

add_filter( 'fl_builder_render_assets_inline', '__return_true' );