✨ 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 Divi BodyCommerce: WooCommerce-Divi pages as tables

Divi BodyCommerce adds WooCommerce-specific modules to Divi's shortcode tree (product grids, mini cart, single-product layouts). SleekView surfaces every Divi page using those modules joined with the WooCommerce products they reference for one audit grid.

♾️ Lifetime License available

SleekView table view for Divi BodyCommerce

Divi + WooCommerce pages in one inventory

Divi BodyCommerce modules render inside Divi's shortcode tree, which lives in wp_posts.post_content alongside the _et_pb_use_builder flag. BodyCommerce shortcodes use prefixes like [dipl_woo_products], [dipl_woo_mini_cart], and [dipl_woo_product_breadcrumb]. The default WordPress admin treats those as ordinary posts, so finding every Divi page running a custom Woo grid means manual scrolling.

SleekView reads every Divi-built post plus the et_pb_layout library, joins them into one table, and exposes BodyCommerce module usage as filterable chips. Filter to pages containing a specific dipl_woo_* shortcode tag. Sort by last edited to find stale Woo layouts. Pin a saved view for the storewide audit so the next refresh takes minutes.

Inline edits to status, slug, and author write through standard WordPress update calls so any Divi or WooCommerce hooks fire normally. The shortcode tree containing BodyCommerce modules stays untouched (that's the Divi visual builder's job) but surrounding metadata becomes editable per row. CSV export of the audit slice gives the team a clean inventory of every Woo-Divi page on the site.

Workflow

From scattered shop pages to one Woo-Divi inventory

1

Detect Divi-built Woo pages

SleekView scans posts with _et_pb_use_builder set, surfaces ones containing dipl_woo_* shortcodes, and joins with wp_posts (post_type=product) for context.
2

Add module and product columns

Pull BodyCommerce module usage and referenced product titles as columns. Each Woo-Divi module gets a filter chip so audits scope easily.
3

Save audit views

Pin views for stale Woo-Divi pages, drafts using deprecated modules, and orphan product templates with no published parent.
4

Inline-edit metadata

Update status, slug, and author in the row for housekeeping tasks. The Divi shortcode tree itself stays inside the visual builder.

Sample columns

A typical Divi BodyCommerce pages view

Divi pages using BodyCommerce Woo modules across the site.
Source: wp_posts (post_type=page,product,et_pb_layout) + wp_postmeta (_et_pb_use_builder)
Title Status BodyCommerce modules Last edited Author URL
Shop landing Published Woo products grid Apr 24 Mira S. /shop
Sale page Published Mini cart, Breadcrumb Apr 20 Lena R. /sale
Custom collection Draft Woo products grid Apr 18 Den J. /collection
Old promo Trashed Mini cart Mar 28 Mira S. /promo

Comparison

Default Divi BodyCommerce admin vs SleekView

Default Divi BodyCommerce admin

  • No way to list pages using dipl_woo_* modules specifically
  • Pages, products, and the et_pb_layout library live on different screens
  • Default lists don't surface last edited or author columns
  • No filter for Divi-built Woo pages versus default Woo pages
  • Finding stale Woo-Divi pages requires manual scrolling

SleekView

  • All Divi pages plus product templates in one queryable table
  • Saved views for pages using a specific dipl_woo_* module
  • Inline edit status, slug, and author without opening Divi
  • Filter by BodyCommerce module presence, author, or last edited
  • CSV export of any audit slice for the team or the client

Features

What SleekView gives you for Divi BodyCommerce

Woo pages with module context

Every Divi page using BodyCommerce modules in one filterable grid. Module chips scope the table to exactly the Woo-Divi slice an audit needs.

Module-aware filters

Find every page using a Woo products grid, every mini-cart placement, or every breadcrumb module. Each audit becomes a saved view, not a SQL query.

Inline metadata edits

Update status, slug, and author in the row without opening the Divi builder. The BodyCommerce shortcode tree under post_content remains the visual builder's job.

Audience

Who uses SleekView for Divi BodyCommerce

Store owners

Track every Divi-customized shop page, sale landing, and collection layout in one grid. Module filters help spot pages that still use a deprecated Woo grid module.

Agencies

Audit client Woo-Divi sites for stale pages and orphan layouts in one pass. Per-client saved views make audit reports a recurring deliverable.

Marketing teams

Coordinate which sale landings and shop pages are live versus drafted ahead of campaigns. Status and module filters replace the launch spreadsheet entirely.

The bigger picture

Why Woo-Divi sites accumulate page-audit debt

BodyCommerce is the standard WooCommerce extension for Divi sites and shops running it typically run it for years across multiple seasonal redesigns. Each redesign leaves pages behind: the old sale landing with a custom Woo grid, the abandoned collection draft, the single-product layout from a campaign that never shipped. The default WordPress admin lists those as ordinary posts with no indication of which BodyCommerce modules they use or whether the products they reference still exist.

Stale Woo-Divi pages pile up quietly. Layout-library entries with no live parent go unnoticed. Drafts owned by former staff sit in the database indefinitely.

None of this is BodyCommerce's fault, it's the operational debt that high-volume Woo-Divi sites accumulate. A queryable inventory turns the audit from a multi-day project into a half-hour grid pass. Filter to pages still using a deprecated Woo grid module and migrate them.

Find every Divi-customized sale landing from past campaigns and review them for relevance. Agencies running Woo-Divi sites for clients use this audit as a routine handover; in-house teams use it as quarterly housekeeping.

Questions

Common questions about SleekView for Divi BodyCommerce

BodyCommerce modules render inside Divi's shortcode tree, which lives in wp_posts.post_content. The plugin reads WooCommerce product data from wp_posts (post_type=product) and wp_postmeta exactly like Woo does. SleekView reads all of it.

 

No. SleekView surfaces metadata around layouts. BodyCommerce module settings are edited inside the Divi visual builder where the design controls live. The grid handles status, slug, and author metadata.

 

Yes. A contains-text filter on post_content surfaces pages using a specific dipl_woo_* shortcode tag. Saved views per module help when you need to find every page using a deprecated Woo grid module.

 

Yes. Product data still lives in wp_posts (post_type=product) regardless of HPOS, since HPOS only changes order storage to the wc_orders table. BodyCommerce-augmented Divi pages and the products they reference all show in one grid.

 

Yes. Every saved view exports to CSV with visible columns. Agencies often export the stale-pages view as a client handover deliverable with module usage and last-edited dates visible.

 

Yes. SleekView is read-mostly. Inline edits use the standard WordPress update path so any Divi, BodyCommerce, or WooCommerce hooks fire normally. The grid never touches post_content shortcode trees.

 

Yes. BodyCommerce single-product layouts live in the et_pb_layout CPT with metadata flagging them as product templates. They show alongside regular pages with the layout type as a filter chip.

 

Queries paginate with server-side cursors and join on the indexed _et_pb_use_builder postmeta key. Sites with thousands of products and 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