✨ 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 Carbon Fields Pro: code-defined fields with an editable admin table

Carbon Fields Pro registers fields in PHP and stores values under _carbon_-prefixed keys in wp_postmeta, wp_termmeta, wp_usermeta, and wp_options. SleekView pivots those keys into proper columns so editors can audit and edit without opening every record.

♾️ Lifetime License available

SleekView table view for Carbon Fields Pro

PHP-registered fields, finally with a cross-record view

Carbon Fields Pro keeps the same code-first philosophy as the free plugin: fields are registered with Container::make() in PHP rather than configured through an admin UI. Pro adds richer field types (associations, complex fields, gravity-based pickers) and longer-term support. Values still live in standard WordPress meta tables under keys like _carbon_hero_cta or _carbon_featured. The post edit screen renders these one record at a time, and that is where the experience ends.

SleekView pivots Carbon Fields Pro keys into proper columns with sort, filter, search, and inline edits across every matching record. Posts, terms, users, and theme options are supported because the underlying meta tables are. Simple types (text, select, checkbox) edit inline through carbon_set_post_meta(), carbon_set_term_meta(), carbon_set_user_meta(), and carbon_set_theme_option() so any container-level save hooks still fire. Complex types show their summary in the column and link to the post edit screen for full editing.

Filters cover the cases that matter for content audits: missing values for a key, stale or empty hero copy, posts not updated since a given date, regions not set yet. SleekView treats Carbon Fields Pro and ACF the same way (as plain meta sources), so a site running both can build a single view mixing keys from each plugin. There is no migration step and no extra storage; the meta tables stay authoritative.

Workflow

From _carbon_ meta to working tables

1

Pick the keys

Tell SleekView which Carbon Fields keys to surface. Underscore-prefixed keys in wp_postmeta, wp_termmeta, wp_usermeta, or wp_options all become candidate columns.
2

Build the column set

Drag keys into the order editors actually read. Mix Carbon columns with native columns like author, date, status, and last modified.
3

Audit with filters

Filter posts by missing values, select value, last-updated, or boolean state. Catch empty hero copy, stale promo flags, or unset regions before they ship.
4

Edit through carbon_set_*

Click a cell to update a text, select, or checkbox field. Writes route through Carbon Fields' setters so container save hooks fire.

Sample columns

Carbon Fields Pro values across landing pages

One row per post with _carbon_-prefixed values surfaced as columns alongside native wp_posts data.
Source: wp_postmeta + wp_termmeta + wp_usermeta + wp_options (_carbon_ prefixes)
Title Hero CTA Featured Region Updated Status
Studio landing Book a call Yes EU Apr 22 Published
Pricing page Start free Yes Global Apr 18 Published
Old campaign Sign up Stale US Jan 14 Draft
Legacy promo Empty Aug 03 Draft

Comparison

Default Carbon Fields Pro admin vs SleekView

Default Carbon Fields Pro admin

  • Field values are buried in each post's edit screen
  • No cross-post view of which fields are set to what
  • Bulk-editing one key across posts requires custom code
  • Termmeta, usermeta, and options fields have no list UI
  • Auditing missing or empty fields means clicking through every record

SleekView

  • Pivot _carbon_-prefixed values into proper columns
  • Cover postmeta, termmeta, usermeta, and options in one tool
  • Inline-edit through carbon_set_* so container hooks fire
  • Filter posts by field value, missing values, or last-updated
  • Save per-role views for landing pages, products, or team members

Features

What SleekView gives you for Carbon Fields Pro

Meta to columns

Pick the _carbon_ keys you care about and they become first-class columns with sort, filter, and search across all matching records.

Edits via carbon_set_*

Inline writes go through Carbon Fields' own setter functions so container save hooks fire and existing validation continues to apply.

Four scopes, one tool

Posts, terms, users, and theme options all use Carbon Fields. SleekView reads each from the right meta or options table without extra setup.

Audience

Who uses SleekView for Carbon Fields Pro

Editors

Spot empty hero copy and outdated flags before they ship. A view of landing pages with empty CTAs is one saved filter away.

Developers

Audit which posts have which fields populated while migrating field schemas. Useful when a container is renamed or split.

Marketing ops

Bulk-toggle featured or region flags across landing pages. Inline edits write through Carbon Fields so custom logic still applies.

The bigger picture

Why Carbon Fields Pro needs a cross-record audit layer

Carbon Fields Pro is built for developers who want their custom field schema in code: registered through PHP, version-controlled with the rest of the codebase, and deployed alongside the theme. That is a strength when the schema is part of the engineering contract, but it leaves a content-team gap. The post edit screen renders the fields one record at a time, and that is where the experience ends.

There is no built-in cross-post view of who set which field to what. There is no way to see how many landing pages still have an empty hero CTA. Termmeta, usermeta, and options fields have no list UI at all, so auditing them means writing one-off WP_Query calls or opening each record.

SleekView fills that audit and bulk-edit gap without replacing how Carbon Fields Pro works. Keys stay where they are, hooks keep firing on simple edits, and complex types still belong on the post edit screen. What changes is that editors and developers finally have a way to see all the values at once, filter to the records that need attention, and update them in bulk.

The schema stays in code; the audit stays in WP Admin.

Questions

Common questions about SleekView for Carbon Fields Pro

Yes. Carbon Fields Pro registers fields in PHP rather than through a UI, but the values still live in standard meta tables. SleekView reads whichever keys you tell it to surface, so the in-code schema stays authoritative and the admin table mirrors what is already there.

 

Simple types (text, select, checkbox) edit inline through Carbon Fields' setter functions. Complex types like associations and complex fields show their summary in the column and link to the post edit screen for full editing, since their UI is non-trivial.

 

All supported. Build a terms, users, or options view and surface _carbon_-prefixed keys exactly as you would for posts. The taxonomy view shows term meta as columns, the users view shows usermeta-backed Carbon keys, and the options view shows theme-option values.

 

Yes. SleekView writes through carbon_set_post_meta() and equivalents, so container-level carbon_fields_post_meta_container_saved-style hooks fire on simple edits. The payload matches Carbon Fields' own save path for the affected key.

 

Yes. A built-in filter shows records with empty or missing values for a given key, useful for migration audits. Combine it with last-updated filters to find posts that have not been touched since a schema change but still need their new fields filled in.

 

Yes. SleekView treats both as plain meta sources, so you can build views mixing Carbon Fields Pro and ACF keys in the same table. Useful during migrations between the two, or on long-running sites where some content models use one and some use the other.

 

Carbon Fields stores values under _carbon_-prefixed keys. SleekView lets you reference either the registered field name or the underlying meta key, so editors do not have to remember the prefix when adding a column.

 

Yes. Per-role view permissions decide which Carbon Fields keys are exposed to a given role. An editor view shows only public-facing keys while a developer view shows the full set. The role check happens before the query so unauthorized columns never load.

 

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