✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Bricksforge: forms, animations and global classes as tables

Bricksforge adds extra elements, dynamic data, animations, and global-class management on top of Bricks. SleekView reads every Bricks-built post and surfaces Bricksforge element usage so audits across forms, popups, and animations stop being manual.

♾️ Lifetime License available

SleekView table view for Bricksforge

Bricksforge usage in one queryable grid

Bricksforge elements render inside Bricks' layout array, which lives in _bricks_page_content_2 in wp_postmeta. Bricksforge global settings (form endpoints, animation defaults, license info) sit in wp_options under the plugin's own keys. The default Bricks admin gives no visibility into which pages use Bricksforge elements specifically, so audits across a site running Bricksforge for years means scrolling or running JSON searches.

SleekView reads every Bricks-built post plus the bricks_template CPT, joins them into one table, and exposes Bricksforge element usage as filterable chips. Filter to pages containing a specific Bricksforge form, popup, animation, or dynamic-data element. Sort by last edited to find stale layouts. Pin a saved view for each audit type so the next pass takes minutes rather than hours.

Inline edits to status, slug, and author route through standard WordPress update calls so any Bricks or Bricksforge hooks fire normally. The layout array under _bricks_page_content_2 stays untouched (the Bricks editor remains the only place those edits happen) but surrounding metadata becomes editable per row. CSV export of an audit slice gives the team a clean inventory of every Bricksforge-touched page.

Workflow

From scattered usage to one Bricksforge inventory

1

Detect Bricks-built posts

SleekView scans for posts with the _bricks_page_content_2 postmeta key, then parses the layout array for Bricksforge element identifiers.
2

Add element columns

Pull Bricksforge element usage out of the layout array as a filterable column. Each Bricksforge element type becomes a chip you can filter on.
3

Save audit views

Pin views for Form Pro usage, animation usage, or particle background usage. Drafts and stale pages get their own saved views per user.
4

Inline-edit metadata

Update status, slug, and author in the row for housekeeping. The layout array stays inside the Bricks editor.

Sample columns

A typical Bricksforge pages view

Bricks pages using Bricksforge elements across the site.
Source: wp_posts (post_type=page,post,bricks_template) + wp_postmeta (_bricks_page_content_2) + wp_options (Bricksforge settings)
Title Status Bricksforge elements Last edited Author URL
Contact page Published Form Pro, Animations Apr 24 Mira S. /contact
Newsletter signup Published Form Pro Apr 21 Lena R. /newsletter
Pricing draft Draft Animations, Particles Apr 17 Den J. /pricing
Old launch popup Trashed Form Pro Mar 30 Mira S. n/a

Comparison

Default Bricksforge admin vs SleekView

Default Bricksforge admin

  • No way to list which pages use specific Bricksforge elements
  • Pages and the bricks_template CPT live on different screens
  • Default lists don't show last edited or author by default
  • No filter for Bricksforge usage versus pure-Bricks pages
  • Finding orphan Bricksforge forms requires JSON spelunking

SleekView

  • All Bricks pages with Bricksforge usage shown per row
  • Saved views for Form Pro, animation, or popup usage specifically
  • Inline edit status, slug, and author without opening Bricks
  • Filter by element type, author, or last edited
  • CSV export of any audit slice

Features

What SleekView gives you for Bricksforge

Element-aware filters

Find every page using Bricksforge Form Pro, every page with the animation engine enabled, or every page running the particle background. Each audit becomes a saved view.

Inline edits

Update status, slug, and author from the row without opening Bricks. The layout array under _bricks_page_content_2 remains the Bricks editor's job.

Pages and templates together

Bricks pages plus the bricks_template CPT in one filterable grid with Bricksforge element columns visible. Audits stop bouncing between admin screens.

Audience

Who uses SleekView for Bricksforge

Agencies

Audit client Bricksforge usage and report on which pages still depend on which add-on features. Per-client saved views turn audit reports into recurring deliverables.

Site owners

Find every page still using a deprecated Bricksforge feature before deactivating it. Quarterly housekeeping prevents Bricksforge sprawl from compounding across years.

Editorial teams

Track which Bricksforge-powered landing pages, popups, and forms are live versus drafted. Status and element filters replace the launch checklist.

The bigger picture

Why Bricksforge sites need an element-usage surface

Bricksforge has become a standard Bricks add-on and the sites running it typically rely on multiple Bricksforge features at once: Form Pro for contact forms, animations for hero sections, popups for newsletter signups. Each feature accumulates pages over time: the contact form that hasn't been touched in two years, the popup form for a campaign that ended, the animation on a hero that someone disabled but never removed. The default Bricks admin gives no surface for any of this.

The bricks_template CPT mixes templates with no Bricksforge filter. Pages with Bricksforge elements look identical in the admin to pages without. A queryable inventory turns the audit from a multi-day investigation into a half-hour pass through the grid.

Filter to pages using a specific Bricksforge feature and review them when it's time to upgrade or deprecate. Find every page running the particle background and audit performance. Agencies running Bricksforge across client sites use this audit as a routine handover deliverable; in-house teams use it as quarterly housekeeping.

Questions

Common questions about SleekView for Bricksforge

Bricksforge elements render inside Bricks' layout array, which sits in _bricks_page_content_2 in wp_postmeta. Global settings (form endpoints, animation defaults) live in wp_options under Bricksforge's own keys. SleekView reads both.

 

No. SleekView surfaces metadata around layouts. Bricksforge element settings, form fields, animation timings, and design controls are still edited inside the Bricks visual editor. The grid handles status, slug, and author metadata around layouts.

 

Yes. A contains-text filter on _bricks_page_content_2 surfaces pages using specific Bricksforge element names like the Form Pro element or the particle background. Saved views per element type help with migration audits.

 

Form Pro submissions are stored separately by Bricksforge (in its own table or in wp_options depending on configuration) and can be exposed as a separate SleekView view. The page-audit grid focuses on which pages run forms, the submissions grid focuses on responses.

 

Yes. Every saved view exports to CSV with visible columns. A common workflow is exporting the Form Pro usage list with last-edited dates and authors so the team can decide page by page which forms to keep.

 

Yes. SleekView is read-mostly. Inline edits use the standard WordPress update path, so any Bricks or Bricksforge hooks fire normally. The grid never touches the layout array, which keeps the Bricks editor as the only source of truth for layout content.

 

Bricksforge extends Bricks' global classes system with extra management features. Class usage across pages can be surfaced as a separate audit view by reading the same _bricks_page_content_2 array and parsing class references.

 

Queries paginate with server-side cursors and join on the indexed _bricks_page_content_2 postmeta key. Sites with thousands of Bricks pages stay responsive because the grid never loads more rows than the viewport needs.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView