✨ 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 Bricks Extras: extra elements and pages as tables

Bricks Extras adds 50+ custom elements (mega menu, content switcher, accordion, marquee) that render inside Bricks' layout array. SleekView reads every Bricks page and exposes Extras element usage as a filterable column.

♾️ Lifetime License available

SleekView table view for Bricks Extras

Bricks Extras audits in one queryable table

Bricks Extras elements render inside Bricks' layout array, which lives in _bricks_page_content_2 in wp_postmeta. Each Extras element has its own identifier in the array (mega menu, advanced accordion, content switcher, animated text). The default Bricks admin shows pages and the bricks_template CPT as ordinary posts, with no filter to find pages using a specific Extras element.

SleekView reads every Bricks-built post plus the bricks_template CPT, joins them into one table, and exposes Bricks Extras element usage as filterable chips. Filter to pages containing a specific Extras 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 Extras hooks fire normally. The Bricks layout array stays untouched (the visual editor remains the source of truth for that) but surrounding metadata becomes editable per row. CSV export of an audit slice gives the team a clean inventory of every Extras-touched page on the site.

Workflow

From scattered Extras usage to one inventory

1

Detect Bricks-built posts

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

Add element columns

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

Save audit views

Pin views for mega menu usage, accordion usage, content switcher 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 Bricks Extras pages view

Bricks pages using Bricks Extras elements across the site.
Source: wp_posts (post_type=page,post,bricks_template) + wp_postmeta (_bricks_page_content_2)
Title Status Extras elements Last edited Author URL
Homepage 2026 Published Mega menu, Marquee Apr 23 Mira S. /
Features overview Published Content switcher Apr 19 Lena R. /features
FAQ page draft Draft Advanced accordion Apr 16 Den J. /faq
Old promo Trashed Marquee Mar 28 Mira S. /promo

Comparison

Default Bricks Extras admin vs SleekView

Default Bricks Extras admin

  • No way to list which pages use specific Extras elements
  • Pages and the bricks_template CPT live on different admin screens
  • Default lists don't show last edited or author columns
  • No filter for Extras-touched pages versus pure-Bricks pages
  • Finding pages using a deprecated Extras element requires JSON queries

SleekView

  • All Bricks pages with Extras element usage shown per row
  • Saved views for mega menu, accordion, or content switcher usage
  • Inline edit status, slug, and author per row
  • Filter by Extras element type, author, or last edited
  • CSV export of any audit slice for client handovers

Features

What SleekView gives you for Bricks Extras

Element-aware filters

Find every page using the Extras mega menu, every page running the content switcher, or every page with an animated marquee. Each audit becomes a saved view, not a JSON search.

Pages and templates together

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

Inline edits

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

Audience

Who uses SleekView for Bricks Extras

Agencies

Audit client Bricks Extras usage and report on which pages depend on which Extras elements. Per-client saved views turn audit reports into recurring deliverables.

Site owners

Find every page still using a specific Extras element before considering migration or deactivation. Quarterly housekeeping prevents Extras sprawl across years of pages.

Editorial teams

Track which Extras-powered campaign pages are live, drafted, or scheduled. Status and element filters replace the launch spreadsheet.

The bigger picture

Why Bricks Extras sites need an element audit

Bricks Extras is the largest commercial Bricks add-on by element count and the sites running it typically use a dozen or more of its elements across the site. Each element accumulates pages over time: the mega menu shipped two years ago that nobody refreshed, the content switcher on a feature page that's now out of date, the marquee on a campaign hero that ended months ago. The default Bricks admin gives no surface for any of this.

The bricks_template CPT mixes templates with no Extras filter. Pages with Extras 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 Extras element and review them for relevance. Find every Extras mega menu in use and confirm which is the live one. Agencies running Bricks Extras 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 Bricks Extras

Extras elements render inside Bricks' layout array, which sits in _bricks_page_content_2 in wp_postmeta. Each Extras element has a distinct identifier in the array so SleekView can parse element usage per page from a single read of the postmeta key.

 

No. SleekView surfaces metadata around layouts. Extras element settings (mega menu items, accordion content, content switcher tabs) are still edited inside the Bricks visual editor. The grid handles status, slug, and author metadata.

 

Yes. A contains-text filter on _bricks_page_content_2 surfaces pages using specific Extras element identifiers like the mega menu or the advanced accordion. Saved views per element help with migration audits.

 

Yes. The bricks_template CPT is read alongside pages and the same JSON parse runs on its layout array. So an Extras element used in a header template shows in the audit grid alongside one used directly on a page.

 

Yes. Every saved view exports to CSV with visible columns. A common workflow is exporting the mega-menu usage list with last-edited dates and authors so the team can audit nav coverage across the site.

 

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

 

Yes. All three add-ons render their elements inside the same _bricks_page_content_2 array. SleekView shows them as separate columns or filter chips so you can see, on the same row, which Bricks add-ons each page depends on.

 

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